Skip to content

API for AWS Secrets Manager

ABAP Interface /AWS1/IF_SMR

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 Secrets Manager is SMR. This TLA helps squeeze ABAP objects into the 30-character length limit of the ABAP data dictionary.


To install the AWS SDK for SAP ABAP, import the Core transport, along with the transport for the Secrets Manager 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 Secrets Manager

Amazon Web Services Secrets Manager provides a service to enable you to store, manage, and retrieve, secrets.

This guide provides descriptions of the Secrets Manager API. For more information about using this service, see the Amazon Web Services Secrets Manager User Guide.

API Version

This version of the Secrets Manager API Reference documents the Secrets Manager API version 2017-10-17.

For a list of endpoints, see Amazon Web Services Secrets Manager endpoints.

Support and Feedback for Amazon Web Services Secrets Manager

We welcome your feedback. Send your comments to, or post your feedback and questions in the Amazon Web Services Secrets Manager Discussion Forum. For more information about the Amazon Web Services Discussion Forums, see Forums Help.

Logging API Requests

Amazon Web Services Secrets Manager supports Amazon Web Services CloudTrail, a service that records Amazon Web Services API calls for your Amazon Web Services account and delivers log files to an Amazon S3 bucket. By using information that's collected by Amazon Web Services CloudTrail, you can determine the requests successfully made to Secrets Manager, who made the request, when it was made, and so on. For more about Amazon Web Services Secrets Manager and support for Amazon Web Services CloudTrail, see Logging Amazon Web Services Secrets Manager Events with Amazon Web Services CloudTrail in the Amazon Web Services Secrets Manager User Guide. To learn more about CloudTrail, including enabling it and find your log files, see the Amazon Web Services CloudTrail User Guide.

Using the SDK

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

Your variable go_smr is an instance of /AWS1/IF_SMR, and all of the operations in the AWS Secrets Manager service are accessed by calling methods in /AWS1/IF_SMR.

API Operations

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

Factory Method

/AWS1/CL_SMR_FACTORY=>create( )

Creates an object of type /AWS1/IF_SMR.


Optional arguments:







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

Configuring Programmatically

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

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


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