API for AWS Compute Optimizer¶

ABAP Package	`/AWS1/API_COP_IMPL`
ABAP SDK "TLA"	`COP`
ABAP Interface	`/AWS1/IF_COP`

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 Compute Optimizer is COP. 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 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¶

Compute Optimizer is a service that analyzes the configuration and utilization metrics of your Amazon Web Services compute resources, such as Amazon EC2 instances, Amazon EC2 Auto Scaling groups, Lambda functions, Amazon EBS volumes, and Amazon ECS services on Fargate. It reports whether your resources are optimal, and generates optimization recommendations to reduce the cost and improve the performance of your workloads. Compute Optimizer also provides recent utilization metric data, in addition to projected utilization metric data for the recommendations, which you can use to evaluate which recommendation provides the best price-performance trade-off. The analysis of your usage patterns can help you decide when to move or resize your running resources, and still meet your performance and capacity requirements. For more information about Compute Optimizer, including the required permissions to use the service, see the Compute Optimizer User Guide.

Using the SDK¶

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

Your variable go_cop is an instance of /AWS1/IF_COP, and all of the operations in the AWS Compute Optimizer service are accessed by calling methods in /AWS1/IF_COP.

API Operations¶

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

Factory Method¶

`/AWS1/CL_COP_FACTORY=>create( )`¶

Creates an object of type /AWS1/IF_COP.

IMPORTING¶

Optional arguments:¶

`IV_PROTOCOL` `TYPE /AWS1/RT_PROTOCOL` `/AWS1/RT_PROTOCOL`¶

`IO_SESSION` `TYPE REF TO /AWS1/CL_RT_SESSION_BASE` `/AWS1/CL_RT_SESSION_BASE`¶

`IV_REGION` `TYPE /AWS1/RT_REGION_ID` `/AWS1/RT_REGION_ID`¶

`IV_CUSTOM_ENDPOINT` `TYPE /AWS1/RT_ENDPOINT` `/AWS1/RT_ENDPOINT`¶

RETURNING¶

`OO_CLIENT` `TYPE REF TO /AWS1/IF_COP` `/AWS1/IF_COP`¶

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

Configuring Programmatically¶

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

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

Paginators¶

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