API for AWS S3 Control¶
ABAP Package | /AWS1/API_S3C |
---|---|
ABAP SDK "TLA" | S3C |
ABAP Interface | /AWS1/IF_S3C |
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 S3 Control is S3C
.
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 S3 Control 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 Web Services S3 Control provides access to Amazon S3 control plane actions.
Using the SDK¶
In your code, create a client using the SDK module for AWS S3 Control, which is created with
factory method /AWS1/CL_S3C_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_s3c) = /aws1/cl_s3c_factory=>create( go_session ).
Your variable go_s3c
is an instance of /AWS1/IF_S3C
,
and all of the operations
in the AWS S3 Control service are accessed by calling methods in /AWS1/IF_S3C
.
API Operations¶
For an overview of ABAP method calls corresponding to API operations in AWS S3 Control, see the Operation List.
Factory Method¶
/AWS1/CL_S3C_FACTORY=>CREATE( )
¶
Creates an object of type /AWS1/IF_S3C
.
IMPORTING¶
Required arguments:¶
IO_SESSION
TYPE REF TO
/AWS1/CL_RT_SESSION_BASE
¶
Optional arguments:¶
IV_PROTOCOL
TYPE
/AWS1/RT_PROTOCOL
¶
IV_REGION
TYPE
/AWS1/RT_REGION_ID
¶
IV_CUSTOM_ENDPOINT
TYPE
/AWS1/RT_ENDPOINT
¶
RETURNING¶
OO_CLIENT
TYPE REF TO
/AWS1/IF_S3C
¶
/AWS1/IF_S3C
represents the ABAP client for the S3 Control service, representing each operation as a method call. For more information see the API Page page.