There were a couple of recent AWS updates that can have a positive impact on your AWS usage: Lambda is now in the Savings Plan, and the new CalledVia IAM property allows you to limit calls to be through an AWS service.
The AWS CLI is one of the major ways of interacting with AWS, so in that regard the release of version 2.0 last week is a major milestone. Therefore, I want to take a look at what it is, how it's different, and what's good not so good about it.
During Andy Jassy's keynote at re:Invent he spent an entire section talking about several new products that would extend AWS 'Beyond the Region'. While this will no doubt give some more options, the main way we'll all be running our AWS services is still going to be within a Region. So let's have a look at how these evolved over time.
Once again we have reached the start of a new year and even decade. So, as I've done the past couple of years I'll take that time to reflect on the past year and what my plans are going forward.
With Midnight Madness, AWS kicked off the official re:Invent announcements. For some reason, I didn’t go to Midnight Madness, but jet lag woke me up early enough that I can at least write about some of the announcements before I’m immersed in re:Invent activities.
With re:Invent less than a week out, I figured it was a good time to see how last year's re:Invent held up. After all, every year we get wowed with all the new services and features that are announced, but how long does it take until we can use those? In fact, it's a year later now, but can we actually use everything that was promised?
As I don’t believe I can replicate the back and forth that (hopefully) made the talk itself entertaining, the structure of this writeup will be slightly different than the talk. If you are interested in the slide deck however, you can find that below.
Back in July I, together with my friend Prateek, presented at Container Camp in Sydney. It’s taken me a while, but I finally got around to doing a writeup of the contents. If you just want to watch the video, I’ve embedded that below.
This is the third post in a series about connecting to your EC2 instances. In the first post I talked about EC2 Instance Connect and the second one was all about Systems Manager Session Manager. In this third post, I’ll have a brief comparison between the two, before looking at some ways to minimise needing this access.
Instead of a normal weekly note, I decided to take a close look at the good and bad of the new device based MFA support in AWS SSO.
This is the second entry in a series of three posts about accessing your EC2 instances. The first entry concerned EC2 Instance Connect, and in this post I’ll discuss the awkwardly named AWS Systems Manager Session Manager.
AWS introduced CloudWatch Anomaly Detection as a way to get smarter alarms for your metrics. There were also a couple of smaller updates to the AWS container services.
Two weeks ago was Cloudflare's birthday week, during which they tend to release new features. This year was no exception, and I'm taking a look at their new Workers Sites. In addition, AWS launches IQ, which is basically experts as a service.
This is the first entry in a series of three posts about accessing your EC2 instances. EC2 Instance Connect, which I’ll call Instance Connect from here, allows you to connect to an instance that doesn’t have a key installed.
