API for AWS WAF Regional¶

ABAP Package	`/AWS1/API_WAR_IMPL`
ABAP SDK "TLA"	`WAR`
ABAP Interface	`/AWS1/IF_WAR`

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 WAF Regional is WAR. 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 WAF Regional 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¶

This is AWS WAF Classic Regional documentation. For more information, see AWS WAF Classic in the developer guide.

For the latest version of AWS WAF, use the AWS WAFV2 API and see the AWS WAF Developer Guide. With the latest version, AWS WAF has a single set of endpoints for regional and global use.

This is the AWS WAF Regional Classic API Reference for using AWS WAF Classic with the AWS resources, Elastic Load Balancing (ELB) Application Load Balancers and API Gateway APIs. The AWS WAF Classic actions and data types listed in the reference are available for protecting Elastic Load Balancing (ELB) Application Load Balancers and API Gateway APIs. You can use these actions and data types by means of the endpoints listed in AWS Regions and Endpoints. This guide is for developers who need detailed information about the AWS WAF Classic API actions, data types, and errors. For detailed information about AWS WAF Classic features and an overview of how to use the AWS WAF Classic API, see the AWS WAF Classic in the developer guide.

Using the SDK¶

In your code, create a client using the SDK module for AWS WAF Regional, which is created with factory method /AWS1/CL_WAR_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_war)       = /aws1/cl_war_factory=>create( go_session ).

Your variable go_war is an instance of /AWS1/IF_WAR, and all of the operations in the AWS WAF Regional service are accessed by calling methods in /AWS1/IF_WAR.

API Operations¶

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

Factory Method¶

`/AWS1/CL_WAR_FACTORY=>create( )`¶

Creates an object of type /AWS1/IF_WAR.

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_WAR` `/AWS1/IF_WAR`¶

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

Configuring Programmatically¶

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

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