/AWS1/CL_EC2=>CREATEVPCENDPOINTCONNNOTIF()
¶
About CreateVpcEndpointConnectionNotification¶
Creates a connection notification for a specified VPC endpoint or VPC endpoint service. A connection notification notifies you of specific endpoint events. You must create an SNS topic to receive notifications. For more information, see Creating an Amazon SNS topic in the Amazon SNS Developer Guide.
You can create a connection notification for interface endpoints only.
Method Signature¶
IMPORTING¶
Required arguments:¶
iv_connectionnotificationarn
TYPE /AWS1/EC2STRING
/AWS1/EC2STRING
¶
The ARN of the SNS topic for the notifications.
it_connectionevents
TYPE /AWS1/CL_EC2VALUESTRINGLIST_W=>TT_VALUESTRINGLIST
TT_VALUESTRINGLIST
¶
The endpoint events for which to receive notifications. Valid values are
Accept
,Connect
,Delete
, andReject
.
Optional arguments:¶
iv_dryrun
TYPE /AWS1/EC2BOOLEAN
/AWS1/EC2BOOLEAN
¶
Checks whether you have the required permissions for the action, without actually making the request, and provides an error response. If you have the required permissions, the error response is
DryRunOperation
. Otherwise, it isUnauthorizedOperation
.
iv_serviceid
TYPE /AWS1/EC2VPCENDPOINTSERVICEID
/AWS1/EC2VPCENDPOINTSERVICEID
¶
The ID of the endpoint service.
iv_vpcendpointid
TYPE /AWS1/EC2VPCENDPOINTID
/AWS1/EC2VPCENDPOINTID
¶
The ID of the endpoint.
iv_clienttoken
TYPE /AWS1/EC2STRING
/AWS1/EC2STRING
¶
Unique, case-sensitive identifier that you provide to ensure the idempotency of the request. For more information, see How to ensure idempotency.
RETURNING¶
oo_output
TYPE REF TO /aws1/cl_ec2crevpcendptcxnnt01
/AWS1/CL_EC2CREVPCENDPTCXNNT01
¶
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_ec2~createvpcendpointconnnotif(
it_connectionevents = VALUE /aws1/cl_ec2valuestringlist_w=>tt_valuestringlist(
( new /aws1/cl_ec2valuestringlist_w( |string| ) )
)
iv_clienttoken = |string|
iv_connectionnotificationarn = |string|
iv_dryrun = ABAP_TRUE
iv_serviceid = |string|
iv_vpcendpointid = |string|
).
This is an example of reading all possible response values
lo_result = lo_result.
IF lo_result IS NOT INITIAL.
lo_connectionnotification = lo_result->get_connectionnotification( ).
IF lo_connectionnotification IS NOT INITIAL.
lv_string = lo_connectionnotification->get_connectionnotificationid( ).
lv_string = lo_connectionnotification->get_serviceid( ).
lv_string = lo_connectionnotification->get_vpcendpointid( ).
lv_connectionnotificationt = lo_connectionnotification->get_connectionnotiftype( ).
lv_string = lo_connectionnotification->get_connectionnotifarn( ).
LOOP AT lo_connectionnotification->get_connectionevents( ) 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_connectionnotifications = lo_connectionnotification->get_connectionnotifstate( ).
lv_string = lo_connectionnotification->get_serviceregion( ).
ENDIF.
lv_string = lo_result->get_clienttoken( ).
ENDIF.