Skip to content

API for AWS OpsWorks

ABAP Interface /AWS1/IF_OWX

The "TLA" is a Three Letter Abbreviation that appears in ABAP class names, data dictionary objects and other ABAP objects throughout the AWS SDK for SAP ABAP. The TLA for AWS OpsWorks is OWX. This TLA helps squeeze ABAP objects into the 30-character length limit of the ABAP data dictionary.


To install the AWS SDK for SAP ABAP, import the Core transport, along with the transport for the OpsWorks module and other API modules you are interested in. A few modules are included in the Core transport itself. For more information, see the Developer Guide guide.

About The Service

AWS OpsWorks

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

AWS OpsWorks Stacks 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 Stacks 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 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.





  • (API only; not available in the AWS console)











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.

Using the SDK

In your code, create a client using the SDK module for AWS OpsWorks, which is created with factory method /AWS1/CL_OWX_FACTORY=>create(). In this example we will assume you have configured an SDK profile in transaction /AWS1/IMG called ZFINANCE.

DATA(go_session)   = /aws1/cl_rt_session_aws=>create( 'ZFINANCE' ).
DATA(go_owx)       = /aws1/cl_owx_factory=>create( go_session ).

Your variable go_owx is an instance of /AWS1/IF_OWX, and all of the operations in the AWS OpsWorks service are accessed by calling methods in /AWS1/IF_OWX.

API Operations

For an overview of ABAP method calls corresponding to API operations in AWS OpsWorks, see the Operation List.

Factory Method

/AWS1/CL_OWX_FACTORY=>create( )

Creates an object of type /AWS1/IF_OWX.


Optional arguments:







/AWS1/IF_OWX represents the ABAP client for the OpsWorks service, representing each operation as a method call. For more information see the API Page page.

Configuring Programmatically

DATA(lo_config) = DATA(go_owx)->get_config( ).

lo_config is a variable of type /AWS1/CL_OWX_CONFIG. See the documentation for /AWS1/CL_OWX_CONFIG for details on the settings that can be configured.


Waiters for Implementation can be accessed via get_waiter() method followed by the waiter method to be called.

Details about the waiter methods available for service Implementation can be found in interface /AWS1/IF_OWX_WAITER.


Paginators for AWS OpsWorks can be created via get_paginator() which returns a paginator object of type /AWS1/IF_OWX_PAGINATOR. The operation method that is being paginated is called using the paginator object, which accepts any necessary parameters to provide to the underlying API operation. This returns an iterator object which can be used to iterate over paginated results using has_next() and get_next() methods.

Details about the paginator methods available for service AWS OpsWorks can be found in interface /AWS1/IF_OWX_PAGINATOR.