Suggestions
Steffan Norberhuis
Launch Your AWS Success 🚀 | Founder Rocketleap
Who is Steffan Norberhuis, Founder at Rocketleap?
Steffan Norberhuis is the founder of Rocketleap, a company that helps organizations accelerate their journey on Amazon Web Services (AWS) cloud.135 He has over 7 years of experience as a freelance AWS and DevOps consultant, working with companies of all sizes to help them adopt AWS and a DevOps way of working to speed up their development process.1
Norberhuis founded Rocketleap with the belief that he could help companies in a better way by focusing on providing Infrastructure as Code (IaC). He has dedicated himself to gathering all AWS best practices into a single, easy-to-use platform that companies can use from day one.1
Norberhuis is a frequent speaker at AWS-related events, such as the AWS Community Day DACH and AWS Community Day NL.257 He has also been featured on LinkedIn, where he shares his insights on leadership and lessons learned.6
You can connect with Steffan Norberhuis on LinkedIn using his username steffannorberhuis.4
Highlights
Saving costs with better connectivity in AWS VPC. Is that possible? Yes!
Every AWS account begins with a default VPC, which is often set up once and then forgotten. However, unlocking the full potential of the VPC can yield numerous benefits.
You can enhance security with defense in depth within your network, optimize costs by leveraging shared VPC connectivity resources, connect easily using private DNS, and streamline developer access to databases. These best practices are helpful for small startups that want to minimize costs as well as big corporates that wish to enhance security.
Do you want to know more? At the AWS Community Day DACH, I will share my experiences in building advanced VPC architectures. We will explore current best practices in AWS, empowering you to optimize your VPC for maximum effectiveness. I am grateful for the opportunity to participate in the community day for Germany, Austria, and Switzerland.
Will I see you on the 17th of September in Munich?
If you want to know more but cannot make the community day, connect with me and DM me on LinkedIn! You can also connect to hear more about speeding up development in AWS.
"Is there a reason to enforce naming conventions in AWS?"
While you should not be a zealot, and some AWS Resources do not accept all naming conventions, it generally pays off to use the same naming convention.
The main benefit is that your AWS feels cleaner!
That doesn't sound so important, yet it is. The broken window theory applies to Software Engineering. If your infrastructure is not clean, it will attract more grime. Over time, you as an organization start to accept more bad solutions. You normalize the deviation from the standard. The bar gets lower and lower.
So, what should you do in AWS: 👉 Have a naming convention 👉Use autogenerated names for uniqueness 👉Adopt the naming convention from your Infrastructure as Code Technology
If you use auto-generated names as much as possible, you can reuse your IaC more easily. You will never get the common error "resource with that name already exists".
Developing a new part of Infrastructure as Code? Just deploy a development environment. Deploying a risky new deployment? Just deploy another version and migrate traffic by percentage.
Get the little things right, so that you will also get the big things right. Attention to detail matters!
