/AWS1/CL_RDS=>CREATEDBPROXYENDPOINT()

About CreateDBProxyEndpoint

Creates a DBProxyEndpoint. Only applies to proxies that are associated with Aurora DB clusters. You can use DB proxy endpoints to specify read/write or read-only access to the DB cluster. You can also use DB proxy endpoints to access a DB proxy through a different VPC than the proxy's default VPC.

Method Signature

IMPORTING

Required arguments:

iv_dbproxyname TYPE /AWS1/RDSDBPROXYNAME /AWS1/RDSDBPROXYNAME

The name of the DB proxy associated with the DB proxy endpoint that you create.

iv_dbproxyendpointname TYPE /AWS1/RDSDBPROXYENDPOINTNAME /AWS1/RDSDBPROXYENDPOINTNAME

The name of the DB proxy endpoint to create.

it_vpcsubnetids TYPE /AWS1/CL_RDSSTRINGLIST_W=>TT_STRINGLIST TT_STRINGLIST

The VPC subnet IDs for the DB proxy endpoint that you create. You can specify a different set of subnet IDs than for the original DB proxy.

Optional arguments:

it_vpcsecuritygroupids TYPE /AWS1/CL_RDSSTRINGLIST_W=>TT_STRINGLIST TT_STRINGLIST

The VPC security group IDs for the DB proxy endpoint that you create. You can specify a different set of security group IDs than for the original DB proxy. The default is the default security group for the VPC.

iv_targetrole TYPE /AWS1/RDSDBPROXYENDPTTGTROLE /AWS1/RDSDBPROXYENDPTTGTROLE

The role of the DB proxy endpoint. The role determines whether the endpoint can be used for read/write or only read operations. The default is READ_WRITE. The only role that proxies for RDS for Microsoft SQL Server support is READ_WRITE.

it_tags TYPE /AWS1/CL_RDSTAG=>TT_TAGLIST TT_TAGLIST

Tags

RETURNING

oo_output TYPE REF TO /aws1/cl_rdscredbproxyendptrsp /AWS1/CL_RDSCREDBPROXYENDPTRSP

Domain	/AWS1/RT_ACCOUNT_ID
Primitive Type	NUMC

Examples

Syntax Example

This is an example of the syntax for calling the method. It includes every possible argument and initializes every possible value. The data provided is not necessarily semantically accurate (for example the value "string" may be provided for something that is intended to be an instance ID, or in some cases two arguments may be mutually exclusive). The syntax shows the ABAP syntax for creating the various data structures.

DATA(lo_result) = lo_client->/aws1/if_rds~createdbproxyendpoint(
  it_tags = VALUE /aws1/cl_rdstag=>tt_taglist(
    (
      new /aws1/cl_rdstag(
        iv_key = |string|
        iv_value = |string|
      )
    )
  )
  it_vpcsecuritygroupids = VALUE /aws1/cl_rdsstringlist_w=>tt_stringlist(
    ( new /aws1/cl_rdsstringlist_w( |string| ) )
  )
  it_vpcsubnetids = VALUE /aws1/cl_rdsstringlist_w=>tt_stringlist(
    ( new /aws1/cl_rdsstringlist_w( |string| ) )
  )
  iv_dbproxyendpointname = |string|
  iv_dbproxyname = |string|
  iv_targetrole = |string|
).

This is an example of reading all possible response values

lo_result = lo_result.
IF lo_result IS NOT INITIAL.
  lo_dbproxyendpoint = lo_result->get_dbproxyendpoint( ).
  IF lo_dbproxyendpoint IS NOT INITIAL.
    lv_string = lo_dbproxyendpoint->get_dbproxyendpointname( ).
    lv_string = lo_dbproxyendpoint->get_dbproxyendpointarn( ).
    lv_string = lo_dbproxyendpoint->get_dbproxyname( ).
    lv_dbproxyendpointstatus = lo_dbproxyendpoint->get_status( ).
    lv_string = lo_dbproxyendpoint->get_vpcid( ).
    LOOP AT lo_dbproxyendpoint->get_vpcsecuritygroupids( ) into lo_row.
      lo_row_1 = lo_row.
      IF lo_row_1 IS NOT INITIAL.
        lv_string = lo_row_1->get_value( ).
      ENDIF.
    ENDLOOP.
    LOOP AT lo_dbproxyendpoint->get_vpcsubnetids( ) into lo_row.
      lo_row_1 = lo_row.
      IF lo_row_1 IS NOT INITIAL.
        lv_string = lo_row_1->get_value( ).
      ENDIF.
    ENDLOOP.
    lv_string = lo_dbproxyendpoint->get_endpoint( ).
    lv_tstamp = lo_dbproxyendpoint->get_createddate( ).
    lv_dbproxyendpointtargetro = lo_dbproxyendpoint->get_targetrole( ).
    lv_boolean = lo_dbproxyendpoint->get_isdefault( ).
  ENDIF.
ENDIF.