This community is for professionals and enthusiasts of our products and services.
Share and discuss the best content and new marketing ideas, build your professional profile and become a better marketer together.


2 Answers
Jesse Wiener United States
6/18/20, 4:57 PM

Hi Stan,

Thanks for the question. I'm sorry to hear about your frustrations! We do recommend a multi-account structure. Separating development, staging and production environments prevent exactly the kind of errors that you're describing. AWS does not charge by the account, only by the resources used, so a configuration like this is ideal. In fact, it is encouraged. AWS Organizations, an AWS managed service, makes this possible. Users can build an account structure of any size and complexity using tree relationships, where permissions and policies are inherited by accounts that are under the same parent account branch. Centralized billing and log aggregation can be configured in separate accounts as well. For most clients, though, we recommend joining Cloud303's organization as part of your engagement with us. By joining our organization, we are able to pass the cost savings of scale onto you, the client.

Good luck!

Cloud303 Solutions Architect

Dan Logan United States
10/13/20, 8:30 PM

I can confirm that multiple AWS accounts is the way to go. Cloud 303 is managing our production and staging environments and I thought it would suck to have them split out.... it doesn't. I love having separated environments. As long as you're using a professional to make sure you have everything secure, then it all works, trust me. It takes a bit to get your CLI aliases setup so that you can access both environments easily, but, it's 110% worth it, trust me.

Ask a Question
Keep Informed
2 follower(s)
About This Community
This community is for users of the AWS cloud platform. We answer questions about how to use both AWS in general and the tools we provide to our customers. Read Guidelines