top of page

It's warming up here in Düsseldorf ☀️

Updated: Oct 2

Every week I learn something new. This week, it was all about setting up AWS Organizations to manage multiple sub-prod and prod environments. In many ways, the post itself describes in detail the first step that needs to be taken to build a product.

In the (g)olden days, this was termed as infrastructure procurement. Look how far have we come - something that took half a year to be delivered, multiple rounds of negotiations with multiple vendors, coordination efforts, risky transport - is now simply available within a few clicks and minutes. ChatGPT says Age of Aquarius is all about technological innovation, and this is just the beginning. Not so golden afterall?

Thanks for reading Let's Do Tech! Subscribe for free to receive weekly updates on my solo journey.

Anyway, although the post describes and provides pointers about using AWS Organizations to manage multiple sub-prod and prod instances, I have come a few steps ahead. That’s the beauty of your subscription to Let’s Do Tech. You get these updates earlier than the masses. 😉

What happened, really?

  1. I created member AWS accounts for sub-prod and prod environments.

  2. Implemented stack and pipeline for infrastructure development.

  3. Implemented stack and pipeline for application development.

  4. Developed nuances for sub-prod only, prod-only, and common deployments.

  5. Created developer account access policies to avoid accidental prod disasters.

  6. Created service accounts for pipeline and approvals.

I will be covering rest of the points in upcoming posts later this week. But I am glad you are following my journey. Do let me know your thoughts - any, and I will be glad to incorporate the feedback.

Also, I have added a page for guest-posts I have been writing till now. Do check them out.

Until next week.

0 views0 comments
bottom of page