How to Cancel AWS Config - Subscribed.FYI
Log in to leave your review.
Join our community of software reviewers on Subscribed.fyi

Continue With Google
Continue With LinkedIn
Continue With X.com
Continue Review with Email
Continue with Email
Enter your email to continue.
Continue
Enter your password
Enter your password to finish setting up your account.
Continue
Reset your password
Enter activation code we sent to your email.
Submit
Set your new password
Enter a new password for your account.
Submit
✨ Ask AI Search
Categories
For Business
Log in
Share Insight

AWS Config

back button Go to AWS Config

How to Cancel AWS Config

To fully cancel AWS Config and reduce costs, follow these steps:

  1. Disable Recording: Go to the AWS Config console, navigate to the settings page, and disable the configuration recorder for each region where it is enabled. This will stop AWS Config from recording resource configurations and evaluating rules.

  2. Delete Config Rules: Delete all AWS Config rules to prevent further evaluations and costs. You can do this manually through the AWS Config console by selecting each rule and choosing "Delete rule" from the actions dropdown. Alternatively, use the AWS CLI command:
    bash
    for rule in $(aws configservice describe-config-rules –query ‘ConfigRules[*].ConfigRuleName’ –output text); do
    aws configservice delete-config-rule –config-rule-name "$rule"
    done

  3. Delete Configuration Recorder: Use the AWS CLI to delete the default configuration recorder:
    bash
    aws configservice delete-configuration-recorder –configuration-recorder-name default –region

  4. Delete Service Linked Role: AWS Config uses a service-linked role. You should delete this role if it was created specifically for AWS Config.

  5. Delete Config Bucket and Objects: If AWS Config is storing configuration snapshots in an S3 bucket, you may want to delete the bucket and its objects to avoid storage costs.

  6. Disable Trusted Access: If your organization integrates with AWS Config, disable trusted access to prevent further integration:
    bash
    aws organizations disable-aws-service-access –service-principal config.amazonaws.com

  7. Check Billing Console: Ensure that there are no ongoing charges related to AWS Config by reviewing your billing console.