API for AWS App Runner¶

ABAP Package	`/AWS1/API_APR_IMPL`
ABAP SDK "TLA"	`APR`
ABAP Interface	`/AWS1/IF_APR`

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 App Runner is APR. 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 AppRunner 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¶

App Runner

App Runner is an application service that provides a fast, simple, and cost-effective way to go directly from an existing container image or source code to a running service in the Amazon Web Services Cloud in seconds. You don't need to learn new technologies, decide which compute service to use, or understand how to provision and configure Amazon Web Services resources.

App Runner connects directly to your container registry or source code repository. It provides an automatic delivery pipeline with fully managed operations, high performance, scalability, and security.

For more information about App Runner, see the App Runner Developer Guide. For release information, see the App Runner Release Notes.

To install the Software Development Kits (SDKs), Integrated Development Environment (IDE) Toolkits, and command line tools that you can use to access the API, see Tools for Amazon Web Services.

Endpoints

For a list of Region-specific endpoints that App Runner supports, see App Runner endpoints and quotas in the Amazon Web Services General Reference.

Using the SDK¶

In your code, create a client using the SDK module for AWS App Runner, which is created with factory method /AWS1/CL_APR_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_apr)       = /aws1/cl_apr_factory=>create( go_session ).

Your variable go_apr is an instance of /AWS1/IF_APR, and all of the operations in the AWS App Runner service are accessed by calling methods in /AWS1/IF_APR.

API Operations¶

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

Factory Method¶

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

Creates an object of type /AWS1/IF_APR.

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_APR` `/AWS1/IF_APR`¶

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

Configuring Programmatically¶

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

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

Paginators¶

Paginators for AWS App Runner can be created via get_paginator() which returns a paginator object of type /AWS1/IF_APR_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 App Runner can be found in interface /AWS1/IF_APR_PAGINATOR.