My AWS Rocks!

A practical approach to protecting AI systems across their lifecycle.

Comprehensive guide to data security across three states - at rest, in transit, and in use - covering encryption, permissions, and resiliency patterns for protecting organizational data.

In this, the second of a multi-part series on securing your workloads, I’ll look more broadly and why, where, and how, you should be securing your network. I’ll look at both the principles and AWS services that help you reduce the risk of network based breaches. The introduction to the Security at all levels gives an overview of what I believe security in depth means and why we should all follow the principles.

Security in depth, defence in depth, layered security, zero trust; all terms that get spoken but often not fully understood. Mainly because much of these security principles have evolved over time and depending on the lens applied a different term has emerged. In this, the first of a series focused on security, I’ll try and unpack what security in depth means (at least for me) and why you should be considering a layered security approach. I will try and keep these posts a mix of technical and non-technical details, and where possible utilise real world examples to highlight my thoughts. Future post will focus on the implementation of security from different perspectives such as application, data, and infrastructure.

Are cost and sustainability really separate items to think off? I’d argue if you do the other 4 pillars of the well-architected framework they are 90% done.

Analysis of AWS public IPv4 address charging announced February 2024 - exploring costs, their impact, and strategies to reduce IPv4-related expenses.

Analysis of technology decision-making exploring why teams get stuck in planning and advocating for rapid iteration and fail-fast approaches.

Prevent bill shock and unexpected AWS charges through account security, budgets, cost anomaly detection, credential protection, and service cost understanding.