How to use multiple AWS accounts as a way to segregate users and resources
H4 Blog
last update:My thoughts on how responsibility works within a DevOps team
Blue/Green Deployment, AB Testing and Feature Flags with Serverless and Lambda
An example of using a Lambda backed CloudFormation Custom Resource for CloudFront Origin Access Identities (OAI)
An overview of Continuous Integration (CI) and Continuous Delivery (CD). What they are and what they do.
Using IAM Roles is one of the most important security measures you can take when running systems on AWS. They let you use short-lived credentials to access AWS resources rather than long-lived credentials. In this blog I'll explain why short-lived credentials are important from a security perspective, and I'll investigate the use of roles in combination with Multi-Factor Authentication (MFA) when using the command line (CLI). Are roles and MFA worth the hassle? How much extra effort is there on the users' part? How does this setup affect user activity logging?
This is my personal technical blog. I'm currently studying for AWS certification, so this is a place where I can record my research and results from getting hands-on with AWS.