API for AWS Resource Access Manager¶

ABAP Package	`/AWS1/API_RAM_IMPL`
ABAP SDK "TLA"	`RAM`
ABAP Interface	`/AWS1/IF_RAM`

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 Resource Access Manager is RAM. 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 RAM 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¶

This is the Resource Access Manager API Reference. This documentation provides descriptions and syntax for each of the actions and data types in RAM. RAM is a service that helps you securely share your Amazon Web Services resources to other Amazon Web Services accounts. If you use Organizations to manage your accounts, then you can share your resources with your entire organization or to organizational units (OUs). For supported resource types, you can also share resources with individual Identity and Access Management (IAM) roles and users.

To learn more about RAM, see the following resources:

Using the SDK¶

In your code, create a client using the SDK module for AWS Resource Access Manager, which is created with factory method /AWS1/CL_RAM_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_ram)       = /aws1/cl_ram_factory=>create( go_session ).

Your variable go_ram is an instance of /AWS1/IF_RAM, and all of the operations in the AWS Resource Access Manager service are accessed by calling methods in /AWS1/IF_RAM.

API Operations¶

For an overview of ABAP method calls corresponding to API operations in AWS Resource Access Manager, see the Operation List.

Factory Method¶

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

Creates an object of type /AWS1/IF_RAM.

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_RAM` `/AWS1/IF_RAM`¶

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

Configuring Programmatically¶

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

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

Paginators¶

Paginators for AWS Resource Access Manager can be created via get_paginator() which returns a paginator object of type /AWS1/IF_RAM_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 Resource Access Manager can be found in interface /AWS1/IF_RAM_PAGINATOR.