Skip to content

Decommission AWS account from Guardrails console. Closes #272 #325

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
wants to merge 5 commits into
base: main
Choose a base branch
from
Draft

Decommission AWS account from Guardrails console. Closes #272 #325

wants to merge 5 commits into from

Conversation

RahulSrivastav14
Copy link
Contributor

Updated the guide Decommission AWS account from Guardrails console as per the issue #272

@RahulSrivastav14 RahulSrivastav14 self-assigned this Mar 26, 2025
@github-actions GitHub Actions
Copy link

Preview Available 🚀

Commit Author: Siddhartha Das
Commit Message: Add changelog entry for Pipes archive mod support. Closes #799 (#800)

Preview Link: turbot-com-git-docs-guardrailsadd-guide-decommiss-06ba30-turbot.vercel.app

@RahulSrivastav14 RahulSrivastav14 linked an issue Mar 26, 2025 that may be closed by this pull request
Update guide - Decommission AWS account from Guardrails console #272
Open
3 tasks
@github-actions GitHub Actions
Copy link

Preview Available 🚀

Commit Author: Siddhartha Das
Commit Message: Add changelog entry for Pipes archive mod support. Closes #799 (#800)

Preview Link: turbot-com-git-docs-guardrailsadd-guide-decommiss-06ba30-turbot.vercel.app

@rajlearner17
Copy link
Contributor

rajlearner17 commented Mar 31, 2025 •
edited
Loading

@RahulSrivastav14

We can break this in to 2 to 3 guides?

Decommission Account (Main folder)

  • Without Resource Deletion - [Disconnect the AWS account from Guardrails] This is Guardrails-side only change. No changes are made in the AWS account. (~2000 resources)

  • With Resource Deletion Using UI - [Decommission Guardrails-managed resources] - Altering the relevant policy settings will make changes in the AWS account. Administrators should determine if they would like to keep Guardrails-managed resources in the account, such as S3 buckets, or CloudTrail. Event Handlers should always be removed.

  • With Resource Deletion Using Script (just this /guardrails/docs/guides/aws/decommission#step-1-clone-guardrails-samples-github-repo)

@rajlearner17 rajlearner17 marked this pull request as draft March 31, 2025 14:23
@github-actions GitHub Actions
Copy link

github-actions bot commented Jun 6, 2025

This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the stale label Jun 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@rajlearner17 rajlearner17 Awaiting requested review from rajlearner17

Assignees

@RahulSrivastav14 RahulSrivastav14

Labels
stale
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Update guide - Decommission AWS account from Guardrails console
3 participants
@RahulSrivastav14 @rajlearner17 @vkumbha