A CloudNation delegacy of four talented cloud engineers has made their way to Las Vegas to be a part of AWS re:Invent 2022. In these blogs they will share their most interesting learnings, experiences and views on everything happening. Exciting right?
This blog is written by Danny Steenman, live from Vegas!
Started the day with the keynote of AWS CEO Adam Selipsky, the focus of this year's keynote was around sustainability and improving the integrations surrounding the management of the data that keeps growing rapidly for their customers every year.
My first session of the day was a break out session about: Build production-ready prototypes rapidly using serverless patterns
In most cases when developing production ready applications, you need to make a tradeoff between velocity or completeness when prototyping. Focusing on both will cause delays in your development lifecycle.
Two ways to speed it up is the cloud native approach (serverless) and iterative approach. Combining it with AWS CDK constructs can improve agility and deploy components fast for prototyping while doing it in a secure and well-architected way.
My second session was a chalk-talk about: Organize application components into repositories & pipelines with AWS CDK
Here we discussed about the trade-offs between using single or multiple pipelines in repositories and how that improves speed or reliability.
A couple of announcements that piqued my interest:
Amazon CloudWatch launches cross-account observability across multiple AWS accounts
I really like how Amazon focused on making multi-account setups more reliable and useful for the developers and engineers that need to maintain them. Having the ability now to get a consolidated view on logs and metrics between accounts really helps to sell the idea of splitting workloads between accounts.
Click here to read more about this.
Amazon VPC Reachability Analyzer now supports network reachability analysis across accounts in an AWS Organization
Another feature that expands upon multi-account usage is that you can now analyse network reachability between AWS resources across different accounts. This is really useful when you have a shared services account that let other accounts consume its applications that are hosted in a VPC. If for example you might not be able to connect to a container or instances in another account within the organization, then the reachability analyzer might be able to quickly find where in the network chain it goes wrong.
Click here to read more about this.
I'll catch you up again on my findings tomorrow. Greetings from Vegas!