---
title: "Retire an AWS environment’s production loop | Proofline Help"
description: "Stop scheduled work and delivery before withdrawing AWS access. Check which other environments still depend on the account-wide role and any shared forwarding stack."
url: https://proofline.sh/help/aws-teardown-production-loop/
---

[Help center](/help/)

# Retire an AWS environment’s production loop

Stop scheduled work and delivery before withdrawing AWS access. Check which other environments still depend on the account-wide role and any shared forwarding stack.

## Stop the schedules and remove the cloud resources

Use this order to stop scheduled work, remove delivery destinations, disconnect AWS and remove its infrastructure grants. Check other environments before changing an organization-wide connection or channel.

1.  Disable schedules. On **Latent risks**, open each schedule, clear **Run this schedule**, then select **Save schedule**. In **Setup → Weekly report**, clear **Send a weekly report**. A weekly note not yet sent is withdrawn. In **Setup → Deploy verification**, select **Stop watching** under each account and region in **Watched alarms**.
2.  Remove destinations. In **Settings → Connections → Slack**, select **Stop posting** under **Existing-problems channel**, then confirm **Stop posting**. For a full organization disconnect, open **Settings → Connections → Slack**, select **Disconnect Slack**, then confirm **Disconnect**. These channels serve the organization; keep a shared destination when another environment still uses it.
3.  Disconnect the AWS account. In each linked environment's **Setup → AWS accounts**, open the account and select **Unlink from this environment**. Then follow [Remove a connection](/help/remove-connection/): open the AWS connection's **Settings** and select **Remove connection**. Resolve any listed dependencies before confirming. Check the console's final state and retry cleanup if requested.
4.  Remove the AWS resources. Delete the CloudFormation stack, or remove the Proofline Terraform module or generated resources from their owning root and apply the reviewed plan. Remove forwarding in every region where you installed it. Confirm the read role, forwarding rule, destination and delivery role are gone in AWS.

Disconnecting in Proofline does not delete your stack or change your Terraform state. Disable schedules first even when you intend to delete them. Deleting a scan schedule keeps recorded scans and existing problems.

## Related guides

-   [Turn on the production loop for AWS](/help/aws-production-loop/)
-   [Connect Amazon Web Services](/help/connect-aws/)
