API for Amazon Route 53 Resolver

ABAP Package	/AWS1/API_R5R_IMPL
ABAP SDK "TLA"	R5R
ABAP Interface	/AWS1/IF_R5R

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 Resolver is R5R. 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 Route53Resolver 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

When you create a VPC using Amazon VPC, you automatically get DNS resolution within the VPC from Route 53 Resolver. By default, Resolver answers DNS queries for VPC domain names such as domain names for EC2 instances or Elastic Load Balancing load balancers. Resolver performs recursive lookups against public name servers for all other domain names.

You can also configure DNS resolution between your VPC and your network over a Direct Connect or VPN connection:

Forward DNS queries from resolvers on your network to Route 53 Resolver

DNS resolvers on your network can forward DNS queries to Resolver in a specified VPC. This allows your DNS resolvers to easily resolve domain names for Amazon Web Services resources such as EC2 instances or records in a Route 53 private hosted zone. For more information, see How DNS Resolvers on Your Network Forward DNS Queries to Route 53 Resolver in the Amazon Route 53 Developer Guide.

Conditionally forward queries from a VPC to resolvers on your network

You can configure Resolver to forward queries that it receives from EC2 instances in your VPCs to DNS resolvers on your network. To forward selected queries, you create Resolver rules that specify the domain names for the DNS queries that you want to forward (such as example.com), and the IP addresses of the DNS resolvers on your network that you want to forward the queries to. If a query matches multiple rules (example.com, acme.example.com), Resolver chooses the rule with the most specific match (acme.example.com) and forwards the query to the IP addresses that you specified in that rule. For more information, see How Route 53 Resolver Forwards DNS Queries from Your VPCs to Your Network in the Amazon Route 53 Developer Guide.

Like Amazon VPC, Resolver is Regional. In each Region where you have VPCs, you can choose whether to forward queries from your VPCs to your network (outbound queries), from your network to your VPCs (inbound queries), or both.

Using the SDK

In your code, create a client using the SDK module for Amazon Route 53 Resolver, which is created with factory method /AWS1/CL_R5R_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_r5r)       = /aws1/cl_r5r_factory=>create( go_session ).

Your variable go_r5r is an instance of /AWS1/IF_R5R, and all of the operations in the Amazon Route 53 Resolver service are accessed by calling methods in /AWS1/IF_R5R.

API Operations

For an overview of ABAP method calls corresponding to API operations in Amazon Route 53 Resolver, see the Operation List.

Factory Method

/AWS1/CL_R5R_FACTORY=>create( )

Creates an object of type /AWS1/IF_R5R.

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_R5R /AWS1/IF_R5R

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

Configuring Programmatically

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

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

Paginators

Paginators for Amazon Route 53 Resolver can be created via `get_paginator()` which returns a paginator object of type [`/AWS1/IF_R5R_PAGINATOR`](./_AWS1_IF_R5R_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 Route 53 Resolver can be found in interface [`/AWS1/IF_R5R_PAGINATOR`](./_AWS1_IF_R5R_PAGINATOR.md).