API for Amazon Macie¶
| ABAP Package | /AWS1/API_MAC_IMPL |
|---|---|
| ABAP SDK "TLA" | MAC |
| ABAP Interface | /AWS1/IF_MAC |
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 Macie is MAC.
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 Macie 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 Macie Classic has been discontinued and is no longer available.
A new Amazon Macie is now available with significant design improvements and additional features, at a lower price and in most Amazon Web Services Regions. We encourage you to take advantage of the new and improved features, and benefit from the reduced cost. To learn about features and pricing for the new Macie, see Amazon Macie. To learn how to use the new Macie, see the Amazon Macie User Guide.
Using the SDK¶
In your code, create a client using the SDK module for Amazon Macie, which is created with
factory method /AWS1/CL_MAC_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_mac) = /aws1/cl_mac_factory=>create( go_session ).
Your variable go_mac is an instance of /AWS1/IF_MAC,
and all of the operations
in the Amazon Macie service are accessed by calling methods in /AWS1/IF_MAC.
API Operations¶
For an overview of ABAP method calls corresponding to API operations in Amazon Macie, see the Operation List.
Factory Method¶
/AWS1/CL_MAC_FACTORY=>create( )¶
Creates an object of type /AWS1/IF_MAC.
IMPORTING¶
Optional arguments:¶
iv_protocol TYPE /aws1/rt_protocol /AWS1/RT_PROTOCOL¶
Domain /AWS1/RT_ACCOUNT_ID Primitive Type NUMC
io_session TYPE REF TO /aws1/cl_rt_session_base /AWS1/CL_RT_SESSION_BASE¶
Domain /AWS1/RT_ACCOUNT_ID Primitive Type NUMC
iv_region TYPE /aws1/rt_region_id /AWS1/RT_REGION_ID¶
Domain /AWS1/RT_ACCOUNT_ID Primitive Type NUMC
iv_custom_endpoint TYPE /aws1/rt_endpoint /AWS1/RT_ENDPOINT¶
Domain /AWS1/RT_ACCOUNT_ID Primitive Type NUMC
RETURNING¶
oo_client TYPE REF TO /aws1/if_mac /AWS1/IF_MAC¶
/AWS1/IF_MACrepresents the ABAP client for the Macie service, representing each operation as a method call. For more information see the API Page page.
Configuring Programmatically¶
DATA(lo_config) = DATA(go_mac)->get_config( ).
lo_config is a variable of type /AWS1/CL_MAC_CONFIG. See the documentation for /AWS1/CL_MAC_CONFIG for
details on the settings that can be configured.
Paginators¶
Paginators for Amazon Macie can be created via `get_paginator()` which returns a paginator object of type [`/AWS1/IF_MAC_PAGINATOR`](./_AWS1_IF_MAC_PAGINATOR.md). 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 Amazon Macie can be found in interface [`/AWS1/IF_MAC_PAGINATOR`](./_AWS1_IF_MAC_PAGINATOR.md).