If you’ve been paying attention, you’ll know that I love the AWS Graviton Processor. The AWS Graviton processor is a custom-designed processor by AWS designed to deliver the best price performance for cloud workloads. They are based on the ARM64/AARCH64 architecture, which is more efficient than the x86 architecture that is traditionally used in servers. This makes Graviton processors ideal for a wide range of workloads, including web applications, databases, and machine learning. Read more

For any followers I’m an advocate for modern technologies. This is across the sustainability, performance and security. I’ve written a lot about Graviton in the past and I’ve also filmed videos with the AWS team about Graviton and I’ve also talked about security features and modern http protocols. The question I’ve got, can I run a reasonable complex website using modern technologies that employ all the modern protocols and security features. Read more

Recently AWS released Graviton 3 processes (at least in the US initially anyway) and it was time to take them for a run against our everyday performance test. There are a few things to keep in mind before we dig into these stats. First off, the stated performance improvements may not reflect significantly in ’everyday’ workloads, as it looks like there were efforts put into specific areas as follows: up to 2x better floating-point performance up to 2x faster crypto performance up to 3x better ML performance Compared to Graviton2. Read more

I often read or hear about people starting their AWS journey by setting up new AWS account and getting themselves into trouble when someone breaks in and runs up a huge bills. With that in mind I thought I would write a CloudFormation template with the services I recommend in a base setup and also describe some of the things I setup. Root MFA Once you’ve signed up with your “Root” user, setup MFA: Read more

In the last post I covered off how to create a REGIONAL WAF in CDK. In this post I’m going to create a CLOUDFRONT WAF. This is a little bit more involved. I’m going to assume that your application stack is not in us-east-1 and thus we’ll need to create another stack in us-east-1. This is going to use several of the tricks we discussed in an earlier post. Existing Let’s say you have an existing stack that has a CloudFront distribution in it. Read more