API for Amazon Route 53¶
ABAP Package | /AWS1/API_R53_IMPL |
---|---|
ABAP SDK "TLA" | R53 |
ABAP Interface | /AWS1/IF_R53 |
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 Route 53 is R53
.
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 Route 53 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 Route 53 is a highly available and scalable Domain Name System (DNS) web service.
You can use Route 53 to:
-
Register domain names.
For more information, see How domain registration works.
-
Route internet traffic to the resources for your domain
For more information, see How internet traffic is routed to your website or web application.
-
Check the health of your resources.
For more information, see How Route 53 checks the health of your resources.
Using the SDK¶
In your code, create a client using the SDK module for Amazon Route 53, which is created with
factory method /AWS1/CL_R53_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_r53) = /aws1/cl_r53_factory=>create( go_session ).
Your variable go_r53
is an instance of /AWS1/IF_R53
,
and all of the operations
in the Amazon Route 53 service are accessed by calling methods in /AWS1/IF_R53
.
API Operations¶
For an overview of ABAP method calls corresponding to API operations in Amazon Route 53, see the Operation List.
Factory Method¶
/AWS1/CL_R53_FACTORY=>create( )
¶
Creates an object of type /AWS1/IF_R53
.
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_R53
/AWS1/IF_R53
¶
/AWS1/IF_R53
represents the ABAP client for the Route 53 service, representing each operation as a method call. For more information see the API Page page.
Configuring Programmatically¶
DATA(lo_config) = DATA(go_r53)->get_config( ).
lo_config
is a variable of type /AWS1/CL_R53_CONFIG
. See the documentation for /AWS1/CL_R53_CONFIG
for
details on the settings that can be configured.
Waiters¶
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_R53_WAITER
.
Paginators¶
Paginators for Amazon Route 53 can be created via get_paginator()
which returns a paginator object of type /AWS1/IF_R53_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 Amazon Route 53 can be found in interface /AWS1/IF_R53_PAGINATOR
.