HEX
Server: Apache
System: Linux vps-cdc32557.vps.ovh.ca 5.15.0-156-generic #166-Ubuntu SMP Sat Aug 9 00:02:46 UTC 2025 x86_64
User: hanode (1017)
PHP: 7.4.33
Disabled: pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare,
Upload Files
File: //lib/python3/dist-packages/awscli/examples/route53resolver/list-resolver-rule-associations.rst
**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 <https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver.html#resolver-overview-forward-vpc-to-network>`__ in the *Amazon Route 53 Developer Guide*.