AWS History Lesson with David Yanacek at AWSreInvent

How AWS re:Invented the cloud By Phoebe Sajor From the floor at AWS re:Invent, Ryan is joined by AWS Senior Principal Engineer David Yanacek to chat about all things AWS, from the truth behind AWS’s Black Friday origin mythos to the development of essential cloud tools like SQS and DynamoDB. Plus, how David envisions autonomous agents will ease developers' operational burdens. https://lnkd.in/erWjFgUr

How AWS re:Invented the cloud By Phoebe Sajor From the floor at AWS re:Invent, Ryan is joined by AWS Senior Principal Engineer David Yanacek to chat about all things AWS, from the truth behind AWS’s Black Friday origin mythos to the development of essential cloud tools like SQS and DynamoDB. Plus, how David envisions autonomous agents will ease developers' operational burdens. https://lnkd.in/erWjFgUr

How AWS re:Invented the cloud By Phoebe Sajor From the floor at AWS re:Invent, Ryan is joined by AWS Senior Principal Engineer David Yanacek to chat about all things AWS, from the truth behind AWS’s Black Friday origin mythos to the development of essential cloud tools like SQS and DynamoDB. Plus, how David envisions autonomous agents will ease developers' operational burdens. https://lnkd.in/erWjFgUr

How AWS re:Invented the cloud By Phoebe Sajor From the floor at AWS re:Invent, Ryan is joined by AWS Senior Principal Engineer David Yanacek to chat about all things AWS, from the truth behind AWS’s Black Friday origin mythos to the development of essential cloud tools like SQS and DynamoDB. Plus, how David envisions autonomous agents will ease developers' operational burdens. https://lnkd.in/erWjFgUr

How AWS re:Invented the cloud By Phoebe Sajor From the floor at AWS re:Invent, Ryan is joined by AWS Senior Principal Engineer David Yanacek to chat about all things AWS, from the truth behind AWS’s Black Friday origin mythos to the development of essential cloud tools like SQS and DynamoDB. Plus, how David envisions autonomous agents will ease developers' operational burdens. https://lnkd.in/erWjFgUr

There’s a quiet logic running through AWS that most tutorials never talk about. Amazon EC2 teaches you that servers are temporary, they’re meant to be replaced, not protected. Auto Scaling takes that idea further by assuming failure will happen and handling it without waiting for humans. Amazon VPC then draws the boundaries, deciding what should be public, what must stay private, and how far mistakes are allowed to travel. Public subnets for entry. 1. Private subnets for real work. 2. Internet Gateways for controlled access. 3. NAT Gateways for safe exit. These aren’t separate features. They’re parts of the same design philosophy. I wrote today’s blog explaining why AWS is designed this way, before building anything. Tomorrow, I’ll create this entire setup from scratch and share what actually breaks. 📘 Read the full story here: 👉 https://lnkd.in/gjFp_527 #AWS #CloudArchitecture #AmazonEC2 #AutoScaling #VPC #LearningInPublic #AWSCommunity

AWS (Amazon web services) highlights that there are 6 benefits of cloud services specifically the AWS cloud as an example. In my opinion, these 6 benefits correlate to a one central need. The need for "Flexibility" 🪱. You can even directly map the 6 benefits to some kind of flexibility. Flexibility of: - 💰 Cost & resources (including time): This maps to "Trade fixed expense for variable expense", "Benefit from massive economies of scale" and "stop spending money to run and maintain data centers". - ⚖️ Scale: This maps to "Benefit from massive economies of scale" and "Stop guessing capacity" - 👩🔬 Optimisation & experimentation to meet business needs: Maps to "Increase speed and agility" - 🛫 Movement & location: Maps to "Go global in minutes" I'll be sharing more system thoughts, opinions & ideas this year. I'm very excited and will now make this my entire identity 😂 . Source: https://lnkd.in/eCiYDeMH

Amazon Web Services (AWS) Bedrock is the AI gateway of choice for most large enterprises. It allows some of our users to connect a great variety of LLMs to run directly from an AWS deployment (even in-VPC). Today we are happy to announce the Amazon Bedrock + Openwork integration, thanks to a contribution to our open source from our friends at Amazon Web Services (AWS) Yariv Levy ❤️ Check it out!

aws_eks_cluster.main: Creation complete after 9m51s Why does it take 10 minutes to create an EKS cluster? 10 minutes is a really long time in the land of computers. If I start a ec2 box systemd-analyze says that takes 50 seconds for example. What is amazon doing behind the scenes that is taking 10 whole minutes?

💸 The Night AWS Taught Me the Value of Alarms It started as a small experiment. I launched a few EC2 instances, enabled autoscaling, and tested a new feature. Everything worked perfectly, so I went home feeling proud 😌. What I didn’t do… was set AWS billing alarms. Over the next few days, traffic slowly increased. Logs piled up. A forgotten load test kept running. Auto Scaling did exactly what it was designed to do — scale. And scale. And scale. AWS never complained. It was silently doing its job. One morning, I opened my email and saw a subject line that stopped my heart: > “Your AWS Estimated Charges Have Exceeded Your Threshold” The bill had crossed a number I had never seen before 💀. I rushed to the console. Instances everywhere. NAT Gateway costs climbing. CloudWatch logs growing like weeds. Nothing was “wrong” — everything was just expensive. That day I learned a painful truth: 💡 AWS doesn’t warn you about bad architecture — it just charges you for it. After shutting things down, I did what I should’ve done on day one: set billing alarms added cost budgets reviewed unused resources scheduled cleanup jobs The next bill was boring. And boring is exactly what you want in cloud billing. 🧠 Lesson from the Experience: If you don’t watch your AWS costs, AWS will happily watch them grow. Cloud bills don’t spike because of bugs — they spike because of silence.