API for Compute Optimizer Automation

ABAP Package	/AWS1/API_COA
ABAP SDK "TLA"	COA
ABAP Interface	/AWS1/IF_COA

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 Compute Optimizer Automation is COA. 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 Compute Optimizer Automation 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

Automation is a feature within Amazon Web Services Compute Optimizer that enables you to apply optimization recommendations to your Amazon Web Services resources, reducing costs and improving performance. You can apply recommended actions directly or create automation rules that implement recommendations on a recurring schedule when they match your specified criteria. With automation rules, set criteria such as Amazon Web Services Region and Resource Tags to target specific geographies and workloads. Configure rules to run daily, weekly, or monthly, and Compute Optimizer continuously evaluates new recommendations against your criteria. Track automation events over time, examine detailed step history, estimate savings achieved, and reverse actions directly from Compute Optimizer when needed.

Using the SDK

In your code, create a client using the SDK module for Compute Optimizer Automation, which is created with factory method /AWS1/CL_COA_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_coa)       = /aws1/cl_coa_factory=>create( go_session ).

Your variable go_coa is an instance of /AWS1/IF_COA, and all of the operations in the Compute Optimizer Automation service are accessed by calling methods in /AWS1/IF_COA.

API Operations

For an overview of ABAP method calls corresponding to API operations in Compute Optimizer Automation, see the Operation List.

Factory Method

/AWS1/CL_COA_FACTORY=>create( )

Creates an object of type /AWS1/IF_COA.

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_coa /AWS1/IF_COA

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

Configuring Programmatically

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

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

Paginators

Paginators for Compute Optimizer Automation can be created via get_paginator() which returns a paginator object of type /AWS1/IF_COA_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 Compute Optimizer Automation can be found in interface /AWS1/IF_COA_PAGINATOR.