list-resolver-rule-associations¶

Description¶

Lists the associations that were created between resolver rules and VPCs using the current AWS account.

Synopsis¶

  list-resolver-rule-associations
[--max-results <value>]
[--next-token <value>]
[--filters <value>]
[--cli-input-json | --cli-input-yaml]
[--generate-cli-skeleton <value>]
[--cli-auto-prompt <value>]

Options¶

--max-results (integer)

The maximum number of rule associations that you want to return in the response to a ListResolverRuleAssociations request. If you don’t specify a value for MaxResults , Resolver returns up to 100 rule associations.

--next-token (string)

For the first ListResolverRuleAssociation request, omit this value.

If you have more than MaxResults rule associations, you can submit another ListResolverRuleAssociation request to get the next group of rule associations. In the next request, specify the value of NextToken from the previous response.

--filters (list)

An optional specification to return a subset of resolver rules, such as resolver rules that are associated with the same VPC ID.

Note

If you submit a second or subsequent ListResolverRuleAssociations request and specify the NextToken parameter, you must use the same values for Filters , if any, as in the previous request.

(structure)

For List operations, an optional specification to return a subset of objects, such as resolver endpoints or resolver rules.

Name -> (string)

When you’re using a List operation and you want the operation to return a subset of objects, such as resolver endpoints or resolver rules, the name of the parameter that you want to use to filter objects. For example, to list only inbound resolver endpoints, specify Direction for the value of Name .

Values -> (list)

When you’re using a List operation and you want the operation to return a subset of objects, such as resolver endpoints or resolver rules, the value of the parameter that you want to use to filter objects. For example, to list only inbound resolver endpoints, specify INBOUND for the value of Values .

(string)

Shorthand Syntax:

Name=string,Values=string,string ...

JSON Syntax:

[
  {
    "Name": "string",
    "Values": ["string", ...]
  }
  ...
]

--cli-input-json | --cli-input-yaml (string) Reads arguments from the JSON string provided. The JSON string follows the format provided by --generate-cli-skeleton. If other arguments are provided on the command line, those values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally. This may not be specified along with --cli-input-yaml.

--generate-cli-skeleton (string) Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value input, prints a sample input JSON that can be used as an argument for --cli-input-json. Similarly, if provided yaml-input it will print a sample input YAML that can be used with --cli-input-yaml. If provided with the value output, it validates the command inputs and returns a sample output JSON for that command.

--cli-auto-prompt (boolean) Automatically prompt for CLI input parameters.

See ‘aws help’ for descriptions of global parameters.

Examples¶

To list associations between Resolver rules and VPCs

The following list-resolver-rule-associations example lists the associations between resolver rules and VPCs in the current AWS account.

aws route53resolver list-resolver-rule-associations

Output:

{
    "MaxResults": 30,
    "ResolverRuleAssociations": [
        {
            "Id": "rslvr-autodefined-assoc-vpc-304bexam-internet-resolver",
            "ResolverRuleId": "rslvr-autodefined-rr-internet-resolver",
            "Name": "System Rule Association",
            "VPCId": "vpc-304bexam",
            "Status": "COMPLETE",
            "StatusMessage": ""
        },
        {
            "Id": "rslvr-rrassoc-d61cbb2c8bexample",
            "ResolverRuleId": "rslvr-rr-42b60677c0example",
            "Name": "my-resolver-rule-association",
            "VPCId": "vpc-304bexam",
            "Status": "COMPLETE",
            "StatusMessage": ""
        }
    ]
}

For more information, see How Route 53 Resolver Forwards DNS Queries from Your VPCs to Your Network in the Amazon Route 53 Developer Guide.

Output¶

NextToken -> (string)

If more than MaxResults rule associations match the specified criteria, you can submit another ListResolverRuleAssociation request to get the next group of results. In the next request, specify the value of NextToken from the previous response.

MaxResults -> (integer)

The value that you specified for MaxResults in the request.

ResolverRuleAssociations -> (list)

The associations that were created between resolver rules and VPCs using the current AWS account, and that match the specified filters, if any.

(structure)

In the response to an AssociateResolverRule , DisassociateResolverRule , or ListResolverRuleAssociations request, information about an association between a resolver rule and a VPC.

Id -> (string)

The ID of the association between a resolver rule and a VPC. Resolver assigns this value when you submit an AssociateResolverRule request.

ResolverRuleId -> (string)

The ID of the resolver rule that you associated with the VPC that is specified by VPCId .

Name -> (string)

The name of an association between a resolver rule and a VPC.

VPCId -> (string)

The ID of the VPC that you associated the resolver rule with.

Status -> (string)

A code that specifies the current status of the association between a resolver rule and a VPC.

StatusMessage -> (string)

A detailed description of the status of the association between a resolver rule and a VPC.

Table of Contents

Feedback

User Guide