AWS Builder Center
AWS CB Spotlight 5 Timers Club-Sergio Cambelo

AWS CB Spotlight 5 Timers Club-Sergio Cambelo

Congratulations to Sergio Cambelo on joining the 5 timers club!

Series: AWS Community Builders Spotlight-5 Timers Club (38 articles)

  1. …
  2. 18
    AWS CB Spotlight 5 Timers Club-Sergio Cambelo This article
Developer Community Manager (Supporting AWS Heroes and Community Builders) at AWS

Congratulations Sergio Cambelo !

Last but certainly not least we welcome Sergio Cambelo into the CB Spotlight 5-Timers Club! Sergio solves multi-account networking problems at enterprise scale by combining VPC Lattice, Cloud WAN, and Route 53 Global Resolver into declarative patterns that eliminate manual routing complexity. On their fictional plaque it reads:
Sergio's articles solve real problems that appear in every multi-account environment. His VPC Lattice piece shows service-to-service connectivity at Layer 7. He walks through the traditional approach: a load balancer per service, PrivateLink endpoints per consumer VPC, Route 53 records per environment. It works but doesn't scale. VPC Lattice centralizes all of this. One service mesh handles discovery, authentication, observability. His Global Resolver article tackles hybrid DNS. Organizations have branch offices and data centers that need to resolve private Route 53 zones. The traditional solution requires VPN tunnels, Resolver Endpoints in every region, conditional forwarders, manual failover logic. Global Resolver exposes anycast IPs on the public internet, authenticated by IP allowlist or access tokens. One policy controls all of it. No VPN required. He builds CloudFormation templates for both. He tests locally first. He shows the dig commands that prove it works.
Sergio thinks in terms of architectural complexity and operational burden. His Cloud WAN egress article explains the send-to service insertion action. Instead of managing routes manually across multiple Transit Gateways, Cloud WAN automatically injects a default route pointing to centralized egress VPCs. Adding a new region requires only a policy change. He traces packet flow from workload instance to internet and back. He shows why the return path works without a send-to policy in reverse. His third-party connectivity article handles the hardest networking problem: IP space collisions. You cannot control what CIDR ranges third parties use. VPC Lattice with full NAT solves this by translating traffic at Layer 7. He builds the Terraform code to demo it. Every article includes cost warnings and comparison matrices. He knows what tradeoffs matter. He documents them.

Read Sergio's first five entries here:

  • VPC Lattice: Full NAT for Third-Party Connectivity Read more 
  • Route 53 Global Resolver: Hybrid DNS Without a VPN Read more 
  • I Lost Newsletter Subscribers Because My Internet Went Down. Here's What I Built. Read more 
  • Centralized Egress with AWS Cloud WAN Read more 
  • Amazon VPC Lattice: Service-to-Service Connectivity at Layer 7 Read more 

Series: AWS Community Builders Spotlight-5 Timers Club (38 articles)

  1. …
  2. 18
    AWS CB Spotlight 5 Timers Club-Sergio Cambelo This article
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article