AWS

Hey everyone! Today I wanted to cover a very important topic that caused me some confusion when I first started studying. I only got clarity on it when I had to implement it in a real project. When designing networks on AWS, one of the most important decisions is defining how different environments will communicate securely, scalably, and cost-effectively. AWS offers several options for private connectivity between resources, but three services tend to generate frequent confusion: ...

When a company starts its journey on AWS without the support of a consultancy or with an inexperienced team, everything usually begins in a single account. The first services are deployed quickly, teams have administrative access, and the main concern is getting workloads into production. It was no different for us. When we identified the opportunity to start our cloud journey, even with some external support, we didn’t see the need for a multi-account environment. ...

Lessons Learned Deploying AWS Direct Connect + Transit Gateway Hybrid environments have moved from being the exception to becoming part of the strategy for many companies. Integrating on-premises datacenters with the cloud requires much more than simply provisioning resources in the cloud — it demands a deep understanding of networking, routing, and connectivity. Working recently on a scenario using AWS Direct Connect integrated with AWS Transit Gateway made it even clearer how networking knowledge makes a real difference in the stability and correct operation of an architecture. ...