Skip to content

API for AWS Signer

ABAP Interface /AWS1/IF_SGN

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 Signer is SGN. 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 signer 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

AWS Signer is a fully managed code-signing service to help you ensure the trust and integrity of your code.

Signer supports the following applications:

With code signing for AWS Lambda, you can sign AWS Lambda deployment packages. Integrated support is provided for Amazon S3, Amazon CloudWatch, and AWS CloudTrail. In order to sign code, you create a signing profile and then use Signer to sign Lambda zip files in S3.

With code signing for IoT, you can sign code for any IoT device that is supported by AWS. IoT code signing is available for Amazon FreeRTOS and AWS IoT Device Management, and is integrated with AWS Certificate Manager (ACM). In order to sign code, you import a third-party code-signing certificate using ACM, and use that to sign updates in Amazon FreeRTOS and AWS IoT Device Management.

With Signer and the Notation CLI from the Notary‚Ä® Project, you can sign container images stored in a container registry such as Amazon Elastic Container Registry (ECR). The signatures are stored in the registry alongside the images, where they are available for verifying image authenticity and integrity.

For more information about Signer, see the AWS Signer Developer Guide.

Using the SDK

In your code, create a client using the SDK module for AWS Signer, which is created with factory method /AWS1/CL_SGN_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_sgn)       = /aws1/cl_sgn_factory=>create( go_session ).

Your variable go_sgn is an instance of /AWS1/IF_SGN, and all of the operations in the AWS Signer service are accessed by calling methods in /AWS1/IF_SGN.

API Operations

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

Factory Method

/AWS1/CL_SGN_FACTORY=>create( )

Creates an object of type /AWS1/IF_SGN.


Optional arguments:







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

Configuring Programmatically

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

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


Waiters for Implementation can be accessed via get_waiter() method followed by the waiter method to be called.

Details about the waiter methods available for service Implementation can be found in interface /AWS1/IF_SGN_WAITER.


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