We build many multi-account Amazon Web Services (AWS) environments at Slalom, as is recommended as part of the AWS Well-Architected Framework. But even without that guidance, I think it’s an ideal structure for most AWS environments. I talked about several reasons for this and offered an overview of the strategy in a previous article: Crafting Secure AWS Environments: Using an AWS Multi-Account Environment.
Now, in this second article, I’ll focus on application account strategies in the context of an AWS Landing Zone.
Let’s start with a couple important Definitions:
We build many multi-account Amazon Web Services (AWS) environments at Slalom, as is recommended as part of the AWS Well-Architected Framework. But even without that guidance, we think it’s an ideal structure for most AWS environments. Part of that is due to the launch of AWS Organizations which made multi-account management far easier.
However, regardless of the size of your AWS footprint, a multi-account setup makes sense from a security, operational, and separation-of-duties perspective for a number of reasons.
By Augusto Rosa
My background is grounded in DevOps and Site Reliability Engineering, and being somewhat new to the Snowflake Data Cloud world and DataOps, I have been pleasantly surprised by how much automation we can drive with a data platform like Snowflake.
Let’s first define what DataOps is: there are generally two definitions.
The first definition is the easy one, the technical one, DataOps is a way to manage your entire data infrastructure through code. This data automation includes schemas, data, testing and all the orchestration around them in an easily manageable, fully auditable package including governance. …
AWS launched DevOps Guru during re:invent 2020, so I got to try it. It has been running in one of my accounts for about a week. Not a very active account, but it has found a few things. Here my first impressions.
Enabling AWS DevOps Guru is relatively easy, and it is not quite well integrated yet into Amazon CodeGuru as an option. They’re merely a top line on the dashboard for CodeGuru that tells you to click here to get to DevOps Guru.
I have worked in technology for more than 20 years, and one thing I learned a while ago is that if you stop learning, your career is likely over. I often tell people that work to:
worry less about their job security but worry about keeping their skills.
A learner’s mentality is someone curious, a listener, shares knowledge, and asks and wonders about the why of things.
I have gotten in trouble throughout my career more than once for asking why this and why that.
An accomplished senior technical engineer focused building and maintained highly functioning teams. Involved in DevOps as a speaker, writer, organizer and coach