The Snarkive is generated on a two week delay-- by a Lambda function, because of course it is.
China Hasn't Subverted AWS
Issue #78: Clouds Above the Stratosphere
Issue #77: Aurora Queries No Longer Unparalleled
Issue #76: When a Giraffe Breaks a HIPAA
Issue #75: The Digital Equivalent of a SuperFund Site
Issue #74: Codesplaining People's Own Projects To Them
Issue #73: Your Ship has LightSailed
Issue #72: Staring at the Sky Waiting for CloudFormations
Issue #71: Aurora Serverless Probably Runs On Blockchain
Issue #70: A Farewell to ARNs
Issue #69: The Wizard of AWS
Issue #68: Protesting Clouds Doesn't Stop the Rain
Issue #67: Pouring Glue on DynamoDB Makes Cloud Services Stickier
Issue #66: Getting Hopped Up on GCP and Fighting a Customer
Issue #65: Apparently 2018 is the Year of Linux on the Desktop
Issue #64: Getting Five Neins on Global Dynamo DB Tables
Issue #63: CloudFront Discovers Africa is a Real Place
Issue #62: EKScuse me a second...
Issue #61: The General Availability of Giraffe Databases
Issue #60: Not a Privacy Policy Update
Issue #59: Bear Metal Instances
Issue #58: Smushit Real Good
Issue #57: phpMyAdmin For DynamoDB
Issue #56: $22 billion a year and all I got was a T-shirt...
Issue #55: AWS Starts Supporting Dunning-Krugerrands
Issue #54: Seattle's Randall Hunting Season
Issue #53: reInvent.micro2xl
Issue #52: A Peak at the Summit
Issue #51: Screaming in the Cloud
Issue #50: New AWS Community Gyros
Issue #49: Even Alexa is Laughing At You
Issue #48: All Quiet on the Western CloudFront
Issue #47: It's All About Seoul
Issue #46: Owl Let You Title This One Yourselves
Issue #45: Making Thyme for SageMaker
Issue #44: Data Residency Permits
Profoundly Snarky Survey
Issue #43: Amazon Maintains Laser Focus on-- 🐿SQRRL! 🐿
Issue #42: Flow Logs for Algernon
Issue #41: ♪ ♫ ♬ Uptime Girl / Serverless Monitoring Around the World... ♪ ♫ ♬
Issue #40: Intel Insider Trading
Issue #39: All the world's a tagged API Stage
Issue #38: Amazon Linux 2: Electric GNU/galoo
Issue #37: AWS Single Sigh On
Issue #36: We Didn't re:Invent the Fire
Issue #35: An Ounce of Pre:Invention
Issue #34: My Database Migrations Went South for the Winter
Issue #33: RIs: Turning "I have some reservations" into a positive since 2009
Issue #32: Unencrypted Data Becomes a CryFS
Issue #31: Self-aware instances for Machine Yearning
Issue #30: The Means to VPC Endpoints
Issue #29: Less fog. More cloud.
Issue #28: Black-Scholes Hun
Issue #27: Screaming With Kinesis
Issue #26: See Spot run. See Spot stop. See Spot resume.
Issue #25: The "Boston / S3 / Party" Issue
Issue #24: ♪ ♫ ♬ From Phoenix, Arizona to maybe Tacoma / Is Amazon Moving down to LA? ♪ ♫ ♬
Issue #23: S3 Permissions are Hit or Myth
Issue #22: The Silence of the Lambdas
Issue #21: You Macie Amazon Blot Out the Sun Today
Issue #20: A Snowball's Chance in São Paulo
Issue #19: "We'll Always Have Paris, Paris, and now Paris."
Issue #18: The Amazonian Pooping Chihuahua 🐕💨💩
Issue #17: The S3-for-all Continues
Issue #16: Hey Now, You're A CodeStar
Issue #15: Not All Heroes Fear CapEx
Issue #14: US-East-1 Drops An F-Bomb
Issue #13: ♪ ♫ ♬ "Hey! You! Get off of Amazon's Cloud!" ♪ ♫ ♬ -- Walmart
Issue #12: Attack of the Database Clones
Issue #11: The Greengrass is always greener and/or grassier...
Quinnterlude
Issue #10: Kicking the S3 Bucket
Issue #9: There is no Cloud Computing, it's just somebody else's horse.
Issue #8: AMI Losing My Mind?
Issue #7: ♪ ♫ ♬ IAM... IAM Superman ♪ ♫ ♬
Issue #6: Come Scale Away With Me
Issue #5: To AWS Summit All Up
Issue #4: Kick the Tires and Make the Hires
Issue #3: Swedening the Pot
Issue #2: Tag! You're it...
Issue #1: Mary Had a Little Lambda

What our readers say: