This article is meant for CEOs, CTOs, and managers who want to understand the benefits of managing AWS infrastructure using Organizations, by answering a common question clients have: Why spend the time setting up AWS Organizations?
I have worked with countless clients on recurring issues that leave them feeling trapped and struggling how to:
I am confident that this article will help you understand how important is to use AWS at the outset so that you start off organized and thus avoid the extra time and costs involved in having to later reorganize.
It’s much easier to:
I always recommend this setup to my clients:
The Demo and Production environments are locked down to the point that no one but the main admin has access to them.
All accounts have 100 percent automatic deployment and do not have access to the servers over SSH or other means – no exceptions.
Having said all this, here’s an example of what will happen if you start the wrong way, based on interacting with clients over the years.
Depending on project size, creating a CloudFormation from scratch takes an average of one month, and then it takes two more weeks to create all the AWS accounts to deploy the stack using the created CloudFormation files. This is the stage where all the final testing and final tuning happens.
Lastly, you’ll start running your code in the new environment with a new work flow. A lot of the project’s bugs will surface at this stage, because up to this point no one could log into the servers to perform ad hoc changes (also known as massaging the code). Now all the work a developer told himself he’d copy later in the repository shows up at this stage. How long will it take to fix everything? It depends on the project. From my experience, it takes a team of developers three months to normalize everything and adapt to the more organized environment.
This is an example for once you get your project off the ground. You could extend your Organization this way later on:
I hope this explanation helps you organize your thoughts around AWS Organizations so that you can know exactly what to ask for when talking to contractors or your team.
If you found this article useful, consider sharing it with someone you think could benefit from it.
Please describe your situation and your cloud computing needs.