Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

AWS OpsWorks endpoints and quotas - AWS General Reference

AWS OpsWorks endpoints and quotas

This section lists the the service endpoints and service quotas for the service. To connect programmatically to an AWS service, you use an endpoint. For more information, see AWS service endpoints.

In addition to the standard AWS endpoints, some AWS services offer the following endpoints in some or all of the AWS Regions that the service is supported in:

  • IPv4 endpoints — These endpoints support only IPv4 requests and have the following format: service-name.region.amazonaws.com

  • Dual-stack endpoints — These endpoints support both IPv4 requests and IPv6 requests and have the following format: service-name.region.api.aws

  • FIPS endpoints — These endpoints comply with the Federal Information Processing Standards (FIPS) and can support either IPv4 requests or dual-stack (IPv4 and IPv6) requests. FIPS endpoints have the following format: service-name-fips.region.ip-endpoint-type, where ip-endpoint-type is amazonaws.com (for IPv4 requests) or api.aws (for IPv4 or IPv6 requests).

Service quotas, also referred to as limits, are the maximum number of service resources or operations for your AWS account. For more information, see AWS service quotas.

Note

AWS recommends that you use Regional STS endpoints within your applications, and avoid using global (legacy) STS endpoints. Regional STS endpoints reduce latency, build in redundancy, and increase session token validity. For more information about configuring your applications to use a Regional STS endpoint, see AWS STS Regionalized endpoints in the AWS SDKs and Tools Reference Guide. For more information about global (legacy) AWS STS endpoints, including how to monitor for use of this type of endpoint, see How to use Regional AWS STS endpoints in the AWS Security blog.

Service endpoints

AWS OpsWorks CM

You can create and manage AWS OpsWorks for Chef Automate and AWS OpsWorks for Puppet Enterprise servers in the following Regions. Resources can be managed only in the Region in which they are created. Resources that are created in one Regional endpoint are not available, nor can they be cloned to, another Regional endpoint.

Region Name Region Endpoint Protocol
US East (N. Virginia) us-east-1 opsworks-cm.us-east-1.amazonaws.com HTTPS
Asia Pacific (Sydney) ap-southeast-2 opsworks-cm.ap-southeast-2.amazonaws.com HTTPS
Europe (Ireland) eu-west-1 opsworks-cm.eu-west-1.amazonaws.com HTTPS

AWS OpsWorks Stacks

You can create and manage AWS OpsWorks resources in all of the following Regions. The Canada (Central) Region Region is API-only; you cannot create stacks in Canada (Central) Region by using the AWS Management Console. Resources can be managed only in the Region in which they are created. Resources that are created in one Regional endpoint are not available—nor can they be cloned to—another Regional endpoint.

Region Name Region Endpoint Protocol
US East (Ohio) us-east-2 opsworks.us-east-2.amazonaws.com HTTPS
US East (N. Virginia) us-east-1 opsworks.us-east-1.amazonaws.com HTTPS
US West (N. California) us-west-1 opsworks.us-west-1.amazonaws.com HTTPS
US West (Oregon) us-west-2 opsworks.us-west-2.amazonaws.com HTTPS
Asia Pacific (Mumbai) ap-south-1 opsworks.ap-south-1.amazonaws.com HTTPS
Asia Pacific (Seoul) ap-northeast-2 opsworks.ap-northeast-2.amazonaws.com HTTPS
Asia Pacific (Singapore) ap-southeast-1 opsworks.ap-southeast-1.amazonaws.com HTTPS
Asia Pacific (Sydney) ap-southeast-2 opsworks.ap-southeast-2.amazonaws.com HTTPS
Asia Pacific (Tokyo) ap-northeast-1 opsworks.ap-northeast-1.amazonaws.com HTTPS
Canada (Central) ca-central-1 opsworks.ca-central-1.amazonaws.com HTTPS
Europe (Frankfurt) eu-central-1 opsworks.eu-central-1.amazonaws.com HTTPS
Europe (Ireland) eu-west-1 opsworks.eu-west-1.amazonaws.com HTTPS
Europe (London) eu-west-2 opsworks.eu-west-2.amazonaws.com HTTPS
Europe (Paris) eu-west-3 opsworks.eu-west-3.amazonaws.com HTTPS
South America (São Paulo) sa-east-1 opsworks.sa-east-1.amazonaws.com HTTPS

Service quotas

The following quotas are for AWS OpsWorks CM.

Name Default Adjustable Description
Automated (scheduled) backup generations per server Each supported Region: 10 Yes Automated (scheduled) backup generations per server. Each server (Chef Automate or Puppet Enterprise) can have a maximum of 30 generations of automated backups.
Chef Automate or Puppet Enterprise servers Each supported Region: 5 Yes Number of servers per account
Manual backups per server Each supported Region: 10 Yes Number of manual backups per server (Chef Automate or Puppet Enterprise)

The following quotas are for AWS OpsWorks stacks.

Name Default Adjustable Description
Apps per stack Each supported Region: 40 Yes The maximum number of apps that you can have in an OpsWorks stack. An AWS OpsWorks Stacks app represents code that you want to run on an application server. Apps are deployed by using Chef recipes.
Instances per stack Each supported Region: 40 Yes The maximum number of instances that you can have in an OpsWorks stack, including both instances created in OpsWorks and outside of OpsWorks. Instances within an OpsWorks stack serve a particular purpose, such as serving applications or hosting a database server.
Layers per stack Each supported Region: 40 Yes The maximum number of layers that you can create in an OpsWorks stack. A layer contains a set of EC2 instances within a stack that serve a particular purpose, such as serving applications or hosting a database server. Layers use Chef recipes to run tasks on instances such as installing packages, deploying apps, and running scripts.
Stacks Each supported Region: 40 Yes The maximum number of AWS OpsWorks stacks that you can create in this account. A stack is a group of OpsWorks instances that perform different roles--such as application servers, database servers, or load balancers--to run a web application.
PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.