API for Auto Scaling¶
ABAP Package | /AWS1/API_ASC_IMPL |
---|---|
ABAP SDK "TLA" | ASC |
ABAP Interface | /AWS1/IF_ASC |
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 Auto Scaling is ASC
.
This TLA helps squeeze ABAP objects into the 30-character length limit of the ABAP data dictionary.
Installation¶
To install the AWS SDK for SAP ABAP, import the Core transport, along with the transport for the Auto Scaling 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¶
Amazon EC2 Auto Scaling is designed to automatically launch and terminate EC2 instances based on user-defined scaling policies, scheduled actions, and health checks.
For more information, see the Amazon EC2 Auto Scaling User Guide and the Amazon EC2 Auto Scaling API Reference.
Using the SDK¶
In your code, create a client using the SDK module for Auto Scaling, which is created with
factory method /AWS1/CL_ASC_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_asc) = /aws1/cl_asc_factory=>create( go_session ).
Your variable go_asc
is an instance of /AWS1/IF_ASC
,
and all of the operations
in the Auto Scaling service are accessed by calling methods in /AWS1/IF_ASC
.
API Operations¶
For an overview of ABAP method calls corresponding to API operations in Auto Scaling, see the Operation List.
Factory Method¶
/AWS1/CL_ASC_FACTORY=>create( )
¶
Creates an object of type /AWS1/IF_ASC
.
IMPORTING¶
Optional arguments:¶
IV_PROTOCOL
TYPE /AWS1/RT_PROTOCOL
/AWS1/RT_PROTOCOL
¶
Domain /AWS1/RT_ACCOUNT_ID Primitive Type NUMC
IO_SESSION
TYPE REF TO /AWS1/CL_RT_SESSION_BASE
/AWS1/CL_RT_SESSION_BASE
¶
Domain /AWS1/RT_ACCOUNT_ID Primitive Type NUMC
IV_REGION
TYPE /AWS1/RT_REGION_ID
/AWS1/RT_REGION_ID
¶
Domain /AWS1/RT_ACCOUNT_ID Primitive Type NUMC
IV_CUSTOM_ENDPOINT
TYPE /AWS1/RT_ENDPOINT
/AWS1/RT_ENDPOINT
¶
Domain /AWS1/RT_ACCOUNT_ID Primitive Type NUMC
RETURNING¶
OO_CLIENT
TYPE REF TO /AWS1/IF_ASC
/AWS1/IF_ASC
¶
/AWS1/IF_ASC
represents the ABAP client for the Auto Scaling service, representing each operation as a method call. For more information see the API Page page.
Configuring Programmatically¶
DATA(lo_config) = DATA(go_asc)->get_config( ).
lo_config
is a variable of type /AWS1/CL_ASC_CONFIG
. See the documentation for /AWS1/CL_ASC_CONFIG
for
details on the settings that can be configured.
Waiters¶
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_ASC_WAITER`](./_AWS1_IF_ASC_WAITER.md).
Paginators¶
Paginators for Auto Scaling can be created via `get_paginator()` which returns a paginator object of type [`/AWS1/IF_ASC_PAGINATOR`](./_AWS1_IF_ASC_PAGINATOR.md). 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 Auto Scaling can be found in interface [`/AWS1/IF_ASC_PAGINATOR`](./_AWS1_IF_ASC_PAGINATOR.md).