ASSOCIATERESOLVERRULE()`¶

About AssociateResolverRule¶

Associates a Resolver rule with a VPC. When you associate a rule with a VPC, Resolver forwards all DNS queries for the domain name that is specified in the rule and that originate in the VPC. The queries are forwarded to the IP addresses for the DNS resolvers that are specified in the rule. For more information about rules, see CreateResolverRule.

Method Signature¶

METHODS /AWS1/IF_R5R~ASSOCIATERESOLVERRULE
  IMPORTING
    !IV_RESOLVERRULEID TYPE /AWS1/R5RRESOURCEID OPTIONAL
    !IV_NAME TYPE /AWS1/R5RNAME OPTIONAL
    !IV_VPCID TYPE /AWS1/R5RRESOURCEID OPTIONAL
  RETURNING
    VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_r5rassocresolverrlrsp
  RAISING
    /AWS1/CX_R5RINTERNALSVCERROREX
    /AWS1/CX_R5RINVALIDPARAMETEREX
    /AWS1/CX_R5RINVALIDREQUESTEX
    /AWS1/CX_R5RLIMITEXCEEDEDEX
    /AWS1/CX_R5RRESOURCEEXISTSEX
    /AWS1/CX_R5RRESOURCENOTFOUNDEX
    /AWS1/CX_R5RRESOURCEUNAVAILEX
    /AWS1/CX_R5RTHROTTLINGEX
    /AWS1/CX_R5RCLIENTEXC
    /AWS1/CX_R5RSERVEREXC
    /AWS1/CX_RT_TECHNICAL_GENERIC
    /AWS1/CX_RT_SERVICE_GENERIC.

IMPORTING¶

Required arguments:¶

`iv_resolverruleid` `TYPE /AWS1/R5RRESOURCEID` `/AWS1/R5RRESOURCEID`¶

The ID of the Resolver rule that you want to associate with the VPC. To list the existing Resolver rules, use ListResolverRules.

`iv_vpcid` `TYPE /AWS1/R5RRESOURCEID` `/AWS1/R5RRESOURCEID`¶

The ID of the VPC that you want to associate the Resolver rule with.

Optional arguments:¶

`iv_name` `TYPE /AWS1/R5RNAME` `/AWS1/R5RNAME`¶

A name for the association that you're creating between a Resolver rule and a VPC.

The name can be up to 64 characters long and can contain letters (a-z, A-Z), numbers (0-9), hyphens (-), underscores (_), and spaces. The name cannot consist of only numbers.

RETURNING¶

`oo_output` `TYPE REF TO /aws1/cl_r5rassocresolverrlrsp` `/AWS1/CL_R5RASSOCRESOLVERRLRSP`¶

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->associateresolverrule(
  iv_name = |string|
  iv_resolverruleid = |string|
  iv_vpcid = |string|
).

This is an example of reading all possible response values

lo_result = lo_result.
IF lo_result IS NOT INITIAL.
  lo_resolverruleassociation = lo_result->get_resolverruleassociation( ).
  IF lo_resolverruleassociation IS NOT INITIAL.
    lv_resourceid = lo_resolverruleassociation->get_id( ).
    lv_resourceid = lo_resolverruleassociation->get_resolverruleid( ).
    lv_name = lo_resolverruleassociation->get_name( ).
    lv_resourceid = lo_resolverruleassociation->get_vpcid( ).
    lv_resolverruleassociation_1 = lo_resolverruleassociation->get_status( ).
    lv_statusmessage = lo_resolverruleassociation->get_statusmessage( ).
  ENDIF.
ENDIF.

/AWS1/IF_R5R=>ASSOCIATERESOLVERRULE()¶