Skip to content
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

FAQ: Fresh root account #421

Merged
merged 2 commits into from
Jan 12, 2020
Merged

FAQ: Fresh root account #421

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7e433f2
add fresh root account
drnickiw Mar 20, 2019
3f4ad33
update fresh root FAQ
drnickiw Mar 20, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions content/faq/should-start-with-fresh-root-account.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
---
title: "Do you recommend starting with a fresh root account?"
description: "We recommend starting fresh with a completely clean account provisioned 100% from the ground up using Infrastructure as Code."
tags:
- root account
- AWS
- Terraform
- Infrastructure as Code
---

## Question

Do you recommend starting with a fresh root account, or building out of our current root AWS account?


## Answer

We recommend starting fresh with a completely clean account provisioned 100% from the ground up using automation tools like Terraform and consistent naming conventions that are programmatically generated .

This is not a hard requirement to "start fresh with AWS accounts." It really depends on what things look like. If there's a lot of cruft, we like to start clean. It's ultimately based on your preference. By starting completely fresh, we can still peer VPCs to obtain DB access and setup whitelists for cross-account access to Lambdas, KMS keys, and DynamoDB tables.

We also eliminate naming collisions or impact to production systems.