Last week I got to visit Seattle for Microsoft Build. Azure is... well, it's no AWS, but that's not really its fault. I did get to speak with the excellently named Corey Sanders, Corporate VP of Azure Compute while I was there. I shoved a microphone in his face; check out Cloud Coreyography.

This week's issue is sponsored by DigitalOcean:

Looking for a high-performance cloud platform with no billing surprises? Always know what you'll pay each month on DigitalOcean with monthly caps and flat pricing across regions. Get started with a $100 credit. https://do.co/lastweek

Community Contributions

As AWS readies the AWS/400 it must surely be constructing, this article helps put us into the mindset of the mainframe managers who are just now approaching cloud-- Demystifying Cloud for Mainframe Managers.

I missed this when it came out a few months ago. There were some changes a year or three back to make this globally consistent, so it's worth reviewing the S3 Consistency Model if you have a minute.

Honeycomb has a public postmortem about their experience with RDS pooping itself. They of course took a slightly more professional approach to it than I did.

Continuous delivery of a static website is now more feasible due to GitHub webhook support.

This well written reddit post goes into depth on where to get started if you've taken a blow to the head and thus want to be a cloud engineer.

And now, the first of many re:Invent guides for 2018. I'll see some of you there.

Xero goes into depth about the impact that their massive AWS migration had upon their business.

LucidChart, a great program that I recommend, discusses their database migration to Aurora. I'd love to chat with the folks there about a few things the article doesn't get into depth with, if any of you know someone I can talk to...

"What do you mean we pay per unattached elastic IP address?!"

"YOU TRIED TO CHARGE PEOPLE TO USE THE BATHROOM ON YOUR PLANES!"

The bill fights between AWS and RyanAir must be the stuff of freaking LEGEND now that the latter has selected the former as its cloud provider of choice.

Get Latest Console Output on EC2 Instances - It doesn't stand up to Azure's "virtual serial console" feature for one. For another... this is designed to be used outside of state transition events such as a start or stop. ...I'm sorry, I have to ask: what the heck terrible workflow is this empowering?! "If there are more than forty characters in the last line of console output" is a terrible conditional.

Introducing Optimize CPUs for Amazon EC2 Instances - "You can now disable CPUs at instance launch. We're not going to charge you a penny less for doing that, but Oracle licensing is done on a per-core basis" says Amazon, firing a warning shot directly into Larry Ellison's front door.

Introducing the IoT Device Simulator - I can't want to simulate IoT Devices, but first I need to wait for AWS to release a Business Model Simulator so I can come up with a viable use case for it.

I'm somewhat skeptical that aws_public_ips can fetch all public IP addresses tied to your account, but I'd give it a shot if I needed such a thing.

If you're working with Terraform and want to do some automated testing, Terratest is a go library that may help out.

Sked is a Python utility to make working with scheduled instances a lot easier.

Terrible Tip of the Week

...and that's what happened Last Week in AWS.

I’m Corey Quinn. I help people significantly reduce and understand their AWS bills and speak broadly on the conference circuit. I advise companies doing interesting things in the cloud space, such as ReactiveOps.

If you've enjoyed reading this, tell your friends to sign up at lastweekinaws.com (or post a link in your company Slack team!) about it. As always, if you've seen a blog post, a tool, or anything else AWS related that you think the rest of the community should hear about, send them my way. You can either hit reply-- or join the #lastweekinaws channel on the og-aws Slack team.