| Interface | Description |
|---|---|
| AWSOpsWorks |
Interface for accessing AWS OpsWorks.
|
| AWSOpsWorksAsync |
Interface for accessing AWS OpsWorks asynchronously.
|
| Class | Description |
|---|---|
| AbstractAWSOpsWorks |
Abstract implementation of
AWSOpsWorks. |
| AbstractAWSOpsWorksAsync |
Abstract implementation of
AWSOpsWorksAsync. |
| AWSOpsWorksAsyncClient |
Client for accessing AWS OpsWorks asynchronously.
|
| AWSOpsWorksAsyncClientBuilder |
Fluent builder for
AWSOpsWorksAsync. |
| AWSOpsWorksClient |
Client for accessing AWS OpsWorks.
|
| AWSOpsWorksClientBuilder |
Fluent builder for
AWSOpsWorks. |
Welcome to the OpsWorks Stacks API Reference. This guide provides descriptions, syntax, and usage examples for OpsWorks Stacks actions and data types, including common parameters and error codes.
OpsWorks Stacks is an application management service that provides an integrated experience for managing the complete application lifecycle. For information about OpsWorks, see the OpsWorks information page.
SDKs and CLI
Use the OpsWorks Stacks API by using the Command Line Interface (CLI) or by using one of the Amazon Web Services SDKs to implement applications in your preferred language. For more information, see:
Endpoints
OpsWorks Stacks supports the following endpoints, all HTTPS. You must connect to one of the following endpoints. Stacks can only be accessed or managed within the endpoint in which they are created.
opsworks.us-east-1.amazonaws.com
opsworks.us-east-2.amazonaws.com
opsworks.us-west-1.amazonaws.com
opsworks.us-west-2.amazonaws.com
opsworks.ca-central-1.amazonaws.com (API only; not available in the Amazon Web Services Management Console)
opsworks.eu-west-1.amazonaws.com
opsworks.eu-west-2.amazonaws.com
opsworks.eu-west-3.amazonaws.com
opsworks.eu-central-1.amazonaws.com
opsworks.ap-northeast-1.amazonaws.com
opsworks.ap-northeast-2.amazonaws.com
opsworks.ap-south-1.amazonaws.com
opsworks.ap-southeast-1.amazonaws.com
opsworks.ap-southeast-2.amazonaws.com
opsworks.sa-east-1.amazonaws.com
Chef Versions
When you call CreateStack, CloneStack, or UpdateStack we recommend you use the
ConfigurationManager parameter to specify the Chef version. The recommended and default value for Linux
stacks is currently 12. Windows stacks use Chef 12.2. For more information, see Chef Versions.
You can specify Chef 12, 11.10, or 11.4 for your Linux stack. We recommend migrating your existing Linux stacks to Chef 12 as soon as possible.