iac.htora.dev · security templates

Home/By platform/Everything for AWS

Everything for AWS

Every template, lesson, refresher, and planner on this site that applies to AWS, in one place.

The list includes Okta, whose template builds its alerts in AWS with EventBridge, CloudWatch Logs, and SNS.

To compare the four clouds with each other, service by service, read The four clouds side by side.

Alerts

The templates below create 39 alerts for AWS. Each link opens the alerts table filtered to one platform, with what fires each alert, the log it reads, and how someone hears.

Standard and Hardened also install 16 saved queries for working a case. The incident response lesson lists them, with the template that installs each one.

Templates

19 templates have code for AWS, written for Terraform. All 57 levels are Ready. What each level includes.

TemplatePlatformQuick startStandardHardenedRefresher
Evidence that survives terminationLogging and evidenceAWSReadyReadyReadyOne page
Evidence from a compromised containerLogging and evidenceAWSReadyReadyReadyOne page
Audit logs nobody can deleteLogging and evidenceAWSReadyReadyReadyOne page
Get cloud logs into your SIEMLogging and evidenceAWSReadyReadyReadyOne page
Keep network records long enough to be usefulLogging and evidenceAWSReadyReadyReadyOne page
An analysis machine that cannot reach productionLogging and evidenceAWSReadyReadyReadyOne page
Emergency access that works when login is brokenIdentity and accessAWSReadyReadyReadyOne page
Shell access without opening a portIdentity and accessAWSReadyReadyReadyOne page
Somewhere to keep secrets that rotates themIdentity and accessAWSReadyReadyReadyOne page
Encryption keys you control and can switch offIdentity and accessAWSReadyReadyReadyOne page
Cloud access for pipelines and pods without stored keysIdentity and accessAWSReadyReadyReadyOne page
Block the changes you never wantGuardrails and complianceAWSReadyReadyReadyOne page
Check every resource against your rules, all the timeGuardrails and complianceAWSReadyReadyReadyOne page
Data that cannot leave your organisationGuardrails and complianceAWSReadyReadyReadyOne page
A record of every action against the cluster APIKubernetesAWSReadyReadyReadyOne page
Notice data walking out the doorDetection and responseAWSReadyReadyReadyOne page
Catch account takeover at the identity providerDetection and responseOktaReadyReadyReadyOne page
Know who is using your AI modelsAIAWSReadyReadyReadyOne page
A safe place to keep Terraform statePipeline and stateAWSReadyReadyReadyOne page

Incident response

The lessons to read before an incident on AWS, the most specific first, and to keep open during one.

Incident response on AWS

CloudTrail defaults, reading keys and role sessions, containment, EC2 forensics, and GuardDuty.

Leading a cloud incident

Phases, scoping, containment per cloud, preserving evidence, incident command, and reviews.

Containers on GKE and EKS

Audit logs, pod identities, nodes, and managed modes on GKE and EKS, and how to respond on each.

Stolen credentials running AI models

One LLMjacking case from alert to containment, the record each cloud keeps, the saved queries, and how to size the bill and the data exposure.

Running a cloud incident as an organisation

Roles adapted from the Incident Command System, the first hour and operational periods, decision records, disclosure clocks, NIST SP 800-61r3, and a maturity ladder.

One-page refreshers

Each prints on one page. Every template in the table above links its own.

Incident response on AWS

What CloudTrail records by default, how to follow a key or a role session, and the first moves for each kind of compromise.

Leading a cloud incident: the first hour

The same phases as any incident, with evidence that disappears faster, more ways for an attacker to come back, and most actions taken through APIs.

Containment by what was compromised

The fastest safe way to cut an attacker off, by what they have, and what each move leaves open.

Containers on GKE and EKS

What each cloud records about a cluster, how to keep a node, and what to rely on when you cannot reach it.

Incident command: roles and rhythm

Five roles adapted from the Incident Command System, the rhythm they work to, and how they pass from one person to a team.

The four clouds

AWS, Azure, Google Cloud, and Oracle Cloud share the same building blocks under different names.

Terraform and OpenTofu

A tool that creates and changes cloud resources to match .tf files. OpenTofu is its open-source fork, and takes the same files with tofu in place of terraform.

Log planning

The log source planner lists every log source to turn on, how long each is kept by default, and what it costs. This link opens it set to AWS and Amazon EKS.

Registry 0.23.0. Built 2026-11-17.

Made by Habibullah Tora. Source on GitHub. Code under the MIT licence, writing under CC BY 4.0.