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.
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
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.
Why has my bill got IP costs is still talked about since AWS started charging for public IPs. This post looks at what you could do to reduce the impact of the charges.
We often get trapped by working out what something is or should be rather than getting started. These are my views on the elephant in the room and why you need to fail fast.