Package com.amazonaws.services.opsworks

AWS OpsWorks

See: Description

Interface Summary

Interface	Description
AWSOpsWorks	Interface for accessing AWS OpsWorks.
AWSOpsWorksAsync	Interface for accessing AWS OpsWorks asynchronously.

Class Summary

Class	Description
AbstractAWSOpsWorks	Abstract implementation of AWSOpsWorks.
AbstractAWSOpsWorksAsync	Abstract implementation of AWSOpsWorksAsync.
AWSOpsWorksAsyncClient	Interface for accessing AWS OpsWorks asynchronously.
AWSOpsWorksAsyncClientBuilder	Fluent builder for AWSOpsWorksAsync.
AWSOpsWorksClient	Client for accessing AWS OpsWorks.
AWSOpsWorksClientBuilder	Fluent builder for AWSOpsWorks.

Package com.amazonaws.services.opsworks Description

AWS OpsWorks

Welcome to the AWS OpsWorks API Reference. This guide provides descriptions, syntax, and usage examples for AWS OpsWorks actions and data types, including common parameters and error codes.

AWS OpsWorks is an application management service that provides an integrated experience for overseeing the complete application lifecycle. For information about this product, go to the AWS OpsWorks details page.

SDKs and CLI

The most common way to use the AWS OpsWorks API is by using the AWS Command Line Interface (CLI) or by using one of the AWS SDKs to implement applications in your preferred language. For more information, see:

• AWS CLI

• AWS SDK for Java

• AWS SDK for .NET

• AWS SDK for PHP 2

• AWS SDK for Ruby

• AWS SDK for Node.js

• AWS SDK for Python(Boto)

Endpoints

AWS OpsWorks supports two endpoints, opsworks.us-east-1.amazonaws.com and opsworks.ap-south-1.amazonaws.com (both HTTPS). You must connect to one of those two endpoints. You can then use the API to direct AWS OpsWorks to create stacks in any AWS region. Stacks created in all regions except ap-south-1 are connected to the us-east-1 regional endpoint; stacks created in ap-south-1 are associated with the ap-south-1 regional endpoint, and can only be accessed or managed within that endpoint.

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.