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/disassociate-resolver-rule.rst
**To disassociate a Resolver rule from an Amazon VPC**

The following ``disassociate-resolver-rule`` example removes the association between the specified Resolver rule and the specified VPC. You can disassociate a rule from a VPC in the following circumstances:

- For DNS queries that originate in this VPC, you want Resolver to stop forwarding queries to your network for the domain name that is specified in the rule.
- You want to delete the forwarding rule. If a rule is currently associated with one or more VPCs, you must disassociate the rule from all VPCs before you can delete it. ::

    aws route53resolver disassociate-resolver-rule \
        --resolver-rule-id rslvr-rr-4955cb98ceexample \
        --vpc-id vpc-304bexam 

Output::

    {
        "ResolverRuleAssociation": {
            "Id": "rslvr-rrassoc-322f4e8b9cexample",
            "ResolverRuleId": "rslvr-rr-4955cb98ceexample",
            "Name": "my-resolver-rule-association",
            "VPCId": "vpc-304bexam",
            "Status": "DELETING",
            "StatusMessage": "[Trace id: 1-5dc5ffa2-a26c38004c1f94006example] Deleting Association"
        }
    }