API for AWS Lambda Core¶

ABAP Package	`/AWS1/API_LMC`
ABAP SDK "TLA"	`LMC`
ABAP Interface	`/AWS1/IF_LMC`

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 Lambda Core is LMC. 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 Lambda Core 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 Lambda Core is a set of APIs for managing shared infrastructure resources used by AWS Lambda. The Lambda Core API provides operations for creating and managing network connectors that enable Lambda MicroVMs to access resources in your Amazon Virtual Private Cloud (Amazon VPC).

Network connectors provision elastic network interfaces (ENIs) in your VPC subnets, providing a managed network path from Lambda compute environments to private resources such as Amazon RDS databases, Amazon ElastiCache clusters, and internal APIs. You create a network connector once and attach it to one or more Lambda MicroVMs at run time.

Using the SDK¶

In your code, create a client using the SDK module for AWS Lambda Core, which is created with factory method /AWS1/CL_LMC_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_lmc)       = /aws1/cl_lmc_factory=>create( go_session ).

Your variable go_lmc is an instance of /AWS1/IF_LMC, and all of the operations in the AWS Lambda Core service are accessed by calling methods in /AWS1/IF_LMC.

API Operations¶

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

Factory Method¶

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

Creates an object of type /AWS1/IF_LMC.

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_lmc` `/AWS1/IF_LMC`¶

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

Configuring Programmatically¶

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

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

Paginators¶

Paginators for AWS Lambda Core can be created via get_paginator() which returns a paginator object of type /AWS1/IF_LMC_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 Lambda Core can be found in interface /AWS1/IF_LMC_PAGINATOR.