API for Amazon S3 on Outposts¶
ABAP Package | /AWS1/API_S3O |
---|---|
ABAP SDK "TLA" | S3O |
ABAP Interface | /AWS1/IF_S3O |
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 Amazon S3 on Outposts is S3O
.
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 S3Outposts 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 S3 on Outposts provides access to S3 on Outposts operations.
Using the SDK¶
In your code, create a client using the SDK module for Amazon S3 on Outposts, which is created with
factory method /AWS1/CL_S3O_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_s3o) = /aws1/cl_s3o_factory=>create( go_session ).
Your variable go_s3o
is an instance of /AWS1/IF_S3O
,
and all of the operations
in the Amazon S3 on Outposts service are accessed by calling methods in /AWS1/IF_S3O
.
API Operations¶
For an overview of ABAP method calls corresponding to API operations in Amazon S3 on Outposts, see the Operation List.
Factory Method¶
/AWS1/CL_S3O_FACTORY=>CREATE( )
¶
Creates an object of type /AWS1/IF_S3O
.
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_S3O
¶
/AWS1/IF_S3O
represents the ABAP client for the S3Outposts service, representing each operation as a method call. For more information see the API Page page.