Roberto Andradas Izquierdo

@brankopetric00 Did you build an internal packages repo, a mirror, from the ones in the Internet so you do not have to download them in every build?

Our NAT Gateway cost more than our entire application infrastructure. $4,800/month for routing. The discovery: - AWS bill jumped from $12k to $17k - Investigated line by line - NAT Gateway: $4,800/month - Wait, what? What NAT Gateway does: - Allows private subnets to access internet - $0.045 per GB processed - $0.045 per hour running Our usage: - 3 NAT Gateways (high availability) - 89 TB data processed monthly - Mostly outbound API calls Where the traffic came from: - Microservices calling external APIs - Pulling Docker images from Docker Hub - Downloading packages during builds - CloudWatch logs - S3 uploads (could use Gateway Endpoint) Optimizations: 1. VPC Endpoints (free data transfer): - Added S3 Gateway Endpoint - Added DynamoDB Gateway Endpoint - Saved 34 TB/month 2. ECR instead of Docker Hub: - Moved all images to ECR - No NAT Gateway charges for pulls - Saved 22 TB/month 3. Consolidated API calls: - Batched requests - Added caching layer - Reduced external calls by 60% - Saved 18 TB/month 4. Reduced NAT Gateways: - Went from 3 to 1 - Acceptable risk for non-production - Saved $720/month in hourly charges New monthly cost: - 15 TB through NAT Gateway - $675 data processing - $240 hourly (1 gateway) - Total: $915/month Savings: $3,885 monthly ($46,620 annually) Lesson: Data transfer is expensive. VPC Endpoints are free. Audit your traffic before scaling NAT Gateways. Architecture decisions have billing implications.

Seeing "cloud is dead" after the AWS outage? The emperor has no clothes. Let's be honest: it's about the Shared Responsibility Model. Did you actually architect for resilience, or were you just assuming the risks? #AWS #CloudArchitecture #Resilience

Cloud Governance is the damn Air Traffic Controller. It's the only one leveraging a full-map view to see what's between the silos. Its job is to build the guidance that stops all that 'noise' from ending in a fiery crash. #CloudGovernance #CloudStrategy #CCoE #TechLeadership

La comunidad hace grande a la nube ☁️ Programas como #AWSCommunityBuilders y los #AWSUserGroups hacen posible eventos como el #AWSCommunityDay Zaragoza 💛 🎤 ¡Te animamos a enviar tu charla y compartir tu experiencia! 🙌 #AWSSpain #AWSCommunity #Cloud #ComunidadTech

Waiting to enjoy this in AWS Lambda Python runtime! 🥵 #aws #python

✨ Python 3.14 is here, it's a game-changer: bye bye, GIL (Global Interpreter Lock)! Native threads can now run in parallel across multiple cores. This means a massive performance boost for your CPU-intensive code. Get ready for speed! 🚀 #Python #Multithreading #Performance

@lucamezzalira The biggest wall I consistently face is the lack of priority alignment between teams. This, combined with insufficient communication, leads to discovering critical requirements and limitations far too late in the process. It is valid not just for micro-frontends.

When I started working with micro-frontends, I remember spending days trying to solve problems that shouldn’t have been that hard. Simple things, like sharing design systems across teams or aligning release strategies, ended up turning into long discussions and endless trial-and-error sessions. Over the years, I realised that every team hits a different wall. For some, it’s the tooling. For others, it’s the lack of clear guidance or training. And sometimes, it’s just the complexity of coordinating so many moving parts. If you have a magic wand right now with a single thing that could be fixed, what’s the most painful part of micro-frontends for you right now? Is there a missing piece of software, documentation, or practice that you wish existed to make your life easier? Drop it in the comments, I’d love to hear your perspective (and maybe it’ll inspire something new for the community 👀). #microfrontends #frontend #architecture #webdev

An architect's true value is understanding business context. Without it, Conway's Law reduces your elegant patterns to mere diagrams. #CloudArchitect #Engineering #ConwaysLaw #Tech

I find this pretty interesting, specially but not only, for companies that enforce a common monitoring framework for their workloads. #AWS #CloudWatch #Monitoring

Guardrails prevent disaster. Railways enable velocity. A good AWS Organization with solid SCPs gives you both. 🛤️ #AWS #CloudGovernance #SCPs #AWOrganizations

8/ Regularly audit and prune unused or redundant SCP statements. Keeps policies slim and your org running smoothly! 🧹 #AWS #CloudManagement

7/ Automate SCP management with IaC tools like CloudFormation or Terraform. Ensures consistency and saves you from manual errors! 🤖 #AWS #DevOps

🚨 Scaling AWS Organizations? High-level SCPs seem simple, but piling on exceptions bloats policies, hitting the 5120-char limit & breaking workloads! 😵 Don’t get trapped—read the thread for tips to scale smart! 🪤 #AWS #CloudSecurity #DevOps

Set up AWS Organizations with automated guardrails to keep your cloud secure & compliant. It’s like guardrails for code—keeps devs safe without slowing us down. More time to build, less to worry! 🛠️ #CloudGovernance #AWS