Seth Eliot ☕

AWS gave us a trophy

Can you bring Artificial Skeleton Bones on an airplane? Yes, you can tsa.gov/travel/securit…

@awsdevelopers @awsdevelopers are you ever going to come back and give the answer (which is SQS BTW)?

Do you know which AWS service came first in history?

@MicrosoftTeams Please fix this...

@cperciva @awsdevelopers Yes! Long gone, but I think this may be the closest thing to it's descendent developer.amazonservices.com

@awsdevelopers The Amazon E-Commerce Service! It made the amazon.com product catalogue available via an API, and also had some image-editing functionality for e.g. adding a "20% off!" label on top of a product image.

@awsdevelopers @aaronshunter I do. And currently 72% of people do not.

@Oblivious9021 Duck, duck, goose

Interviewer: A Load Balancer sits in front of multiple servers...but how does it choose the right one for each request?

@endingwithali just follow the directions here youtube.com/watch?v=40SnEd…

setting up my first home server what flavor of linux should i use

Two completely different tests - same score! How?

@RDarrylR It's Darryl and his daily Gateway API update 😁. Great stuff

You've likely heard about the end of support for #Ingress #NGINX. Migrating off a core infrastructure component like this across multiple clusters with zero downtime isn't easy. This article discusses a real Ingress-NGINX to #GatewayAPI migration on #EKS, covering the DNS toggle pattern that made the cutover safe and reversible. The details include pre-transferring TXT ownership records (a step often skipped) to gating HTTPRoutes behind Helm feature flags. The approach is methodical and built for teams that can't afford to learn by breaking production. The process in the example took about a week across 5+ clusters. Tal Shechanovitz talks about the full migration path. Many other teams are staring down the Ingress-NGINX end of life deadline and this real-world reference may help. Check it out! lckhd.eu/0QKuDZ

@apparentorder But if you try to do simple things like list VPCs (or even create one) they fail. It is effectively a Region-down event.

@setheliot Strictly AZ-local resources like an EC2 instances are not affected in mec1-az1. But services that depend on multiple AZ, like S3 or DynamoDB, are impacted (because 2/3 AZ damaged).

@nocoot That is a reasonable guess, but if so, it breaks the "promise" of AZ independence

@setheliot (speculating) Some services promise cross-az replication of data, they can't accept writes when 2/3 AZs are down?

@RDarrylR Supported by AWS Load Balancer Controller (LBC)... interesting... kubernetes-sigs.github.io/aws-load-balan…

The #Kubernetes Gateway API is gradually replacing the traditional Ingress API, and if you manage cluster networking, it is worth understanding why. The shift brings more flexible routing, broader protocol support, and a modular resource model that scales better. The article below discusses the key differences between #Ingress and #GatewayAPI, covers GatewayClass and HTTPRoute configuration, and includes a practical migration example. It also flags common pitfalls like misconfigured listeners and overlapping routes. The Collabnix Team put together a nice article here. If you want to understand what the Gateway API is then check it out! lckhd.eu/QXFGKr

@kmcnam1 no spaces, all lowercase, thanks

@livingdevops ECS – “I want containers but Kubernetes gives me anxiety.” is pretty funny, but bonus points for not using the wrong AWS icons (epic workaround: not using any AWS icons)

Top 25 AWS services explained EC2 – Your server. But in the cloud. You pay even when it’s doing nothing. (Sound familiar?) Lambda – EC2’s lazy cousin. Only wakes up when there’s work. No work, no bill. ECS – “I want containers but Kubernetes gives me anxiety.” EKS – Kubernetes. For people who enjoy suffering professionally. Auto Scaling – Your app gets famous overnight. This makes sure it doesn’t die from the attention. S3 – A bucket that never fills up. Jeff Bezos’s gift to humanity. EBS – A hard drive for your EC2. Loyal. But only to one instance at a time. EFS – EBS but for people who like sharing. Multiple instances, one file system. FSx – EFS but for enterprises who need Windows compatibility and a bigger invoice. Snowball – When your internet is too slow to upload data, AWS ships you a literal box. VPC – Your private neighborhood inside AWS. Strangers not allowed. Route 53 – The GPS of your app. Tells traffic where to go. ELB – The bouncer at the club. Splits traffic so no one server gets overwhelmed. CloudFront – Your content, cached globally. Because nobody likes a slow website. Direct Connect – A private highway between your office and AWS. No public internet drama. RDS – A managed database. AWS handles backups so you can sleep at night. DynamoDB – NoSQL at insane speed. Schema? We don’t do that here. Aurora – RDS on steroids. Faster, smarter, slightly more expensive. Redshift – A warehouse for your data. Not clothes. Petabytes of analytics data. ElastiCache – RAM for your app. Because hitting the database every time is embarrassing. IAM – The bouncer for your entire AWS account. Get this wrong and you’re headlines. KMS – Locks your secrets in a vault. AWS holds the key. You trust them. Mostly. Cognito – “Login with Google” but you built it on AWS. GuardDuty – The security camera that never blinks. Watches for sketchy behavior 24/7. WAF – Stops hackers at the door before they touch your app. Bookmark it.

@RDarrylR Were this a trivia question, I would have never guessed that solution, but it makes sense.

NAT gateways work well for many things but they're not always needed and can really add up in cost. For Lambda functions in VPCs, they charge by the hour whether you're using them or not. For workloads that run sporadically, you're essentially paying for idle infrastructure around the clock, a cost that adds up quickly. There's a simpler approach using IPv6. By enabling dual-stack mode and using an egress-only internet gateway, your #Lambda functions can reach AWS services and external APIs directly over #IPv6. Internal VPC communication continues over IPv4 as before. Petri Kallberg walks through the configuration changes needed: associating an IPv6 CIDR block, updating subnets and route tables, and enabling Ipv6AllowedForDualStack on your Lambda. While some AWS services still lack IPv6 support, AWS has made significant progress on this throughout 2025. lckhd.eu/m7Vf35

Who can describe what each of these AWS services does? AppSync AppStream App Runner AppConfig AppFlow App Mesh

@codeculturecob @brankopetric00 Magic... and parallelization plus AWS backbone connectivity

@brankopetric00 how does it work? 😅

S3 uploads were 30sec for 100MB files. Enabled S3 Transfer Acceleration + multipart uploads. Now 4 seconds.

@nixcraft @0xF2 Crappy AI thumbnail. Also Bezos has not been CEO for 4 years now.

Amazon service (AWS) was taken down by AI coding bot named Kiro futurism.com/artificial-int…

@apparentorder genius.com/1076379/Billy-…

How long does it take AWS to build a Local Zone? Vienna was announced more than four years ago. Nothing since.

@brankopetric00 What do you think of EKS Auto Mode that uses Karpenter?

Nodes took 8min to scale up, pods pending. Switched to Karpenter with AWS spot. New nodes ready in 45 seconds, costs down 60%.