197 articles
Knowledge Base
AWS
197 articles in the AWS category · page 3 of 9.
- AWS operations support: who owns incidents, patching, scaling, and backups AWS operations support only works when every recurring duty has one named owner. A practical ownership map for incidents, patching, scaling, and backups — and how to verify each is real.
- AWS performance optimization: locating the real bottleneck across compute, database, and network AWS performance optimization starts with finding the one constraint that is actually slow — burst credits, EBS limits, a bad query, or cross-AZ hops — not resizing everything. Here is the diagnostic order.
- aws s3 sync and cp: the CLI patterns operators actually use The aws s3 sync and aws s3 cp patterns that hold up in production — dry runs, safe deletes, exclude/include ordering, streaming, storage classes, and the transfer tuning that actually moves the needle.
- AWS Security Hub setup: turning a wall of findings into a workable queue A default AWS Security Hub setup produces hundreds of findings and no plan. Here is how to enable it across accounts and regions, pick standards, suppress the noise, and end up with a queue a real team can work.
- AWS support for small business: practical help vs enterprise consulting theatre What AWS support for small business actually looks like: which AWS support plan is worth paying for, what it does not cover, and when third-party help beats a bigger support tier.
- AWS unused resources cleanup: the orphan hunt checklist A practical AWS unused resources cleanup checklist: find unattached EBS volumes, idle load balancers, aged snapshots, and unused Elastic IPs — and delete them safely.
- Cloning Aurora databases for staging: how fast clones actually work Aurora fast clones create a full copy of a production database in minutes using copy-on-write storage. How cloning works, what it costs, the CLI runbook, and where clones stop being the right tool.
- CloudFront 502 and 504 errors from the origin: the origin-side checklist CloudFront 502 means the origin connection or TLS handshake failed; 504 means the origin timed out. Here is the origin-side checklist that finds the cause, in order.
- CloudFront cache invalidation: doing it fast, cheap, and rarely How CloudFront invalidation works, what the 1,000 free paths per month actually mean, and the versioning strategy that makes invalidation something you almost never need.
- Continuous AWS security management vs one-time hardening: why the audit report rots AWS security management services exist because one-time hardening decays: findings reopen, new resources ship unhardened, and nobody watches the alerts. Here is the honest comparison and what continuous actually means.
- Debugging EC2 user-data scripts that never ran: reading the cloud-init logs When an EC2 user-data script never ran, the answer is in the cloud-init logs. Here is where to look, the once-per-instance rule that catches everyone, and the shebang and syntax mistakes that fail silently.
- EBS and snapshot costs: lifecycle policies before the storage line quietly doubles AWS EBS snapshot cost cleanup in practice: gp2 to gp3 migration, Data Lifecycle Manager retention policies, snapshot archive tier, and the orphans left behind by old AMIs.
- EC2 instance status check failed (1/2 or 2/2): what each check means and how to recover An EC2 status check failed alert means either AWS's hardware layer or your operating system is unhealthy. Here is what each check tests, how to tell which one failed, and the recovery path for each.
- EC2 launch template versioning: how to manage instance config without breaking your fleet How EC2 launch template versions, $Default and $Latest actually work, and a versioning discipline that keeps Auto Scaling groups from launching config you never approved.
- EC2 placement groups explained: cluster, spread, partition — and when they matter What EC2 placement groups actually do: cluster for lowest network latency, spread for hard rack isolation, partition for Kafka and Cassandra style fault domains — and when to use none at all.
- EC2 rightsizing in practice: beyond what Compute Optimizer tells you AWS EC2 rightsizing beyond Compute Optimizer: get memory metrics in place, account for burst credits and app constraints, and downsize without causing an incident.
- EC2 security group cookbook: the rules a real web stack actually needs A practical EC2 security group cookbook: the exact inbound and outbound rules for a load balancer, app tier, and database tier, using group references instead of IP ranges.
- EC2 spot interruptions: the two-minute warning and surviving it EC2 spot instances get a two-minute interruption warning before AWS reclaims them. Here is how to catch the notice, drain work in time, and design so an interruption is a shrug instead of an outage.
- EC2 SSH connection timed out: the five causes in order of likelihood An EC2 SSH connection timed out error means your packets are being dropped before they reach sshd. Here are the five causes ranked by likelihood, and how to test each one in minutes.
- EC2 t3/t4g instance suddenly slow: CPU credits and the burstable surprise Why a t3 or t4g EC2 instance slows to a crawl under sustained load: how CPU credits work, how to read CPUCreditBalance, and when unlimited mode quietly bills you instead.
- Elastic IPs on AWS: when you actually need one, the limits, and the idle charges When an Elastic IP is the right tool on EC2, when DNS or an NLB does the job better, the five-per-Region quota, and how the public IPv4 charge changed the cost math.
- Enforcing MFA on AWS accounts: the policies that actually force it Asking people to enable MFA does not work; policy does. The deny-unless-MFA IAM policy that actually enforces MFA on AWS accounts, the BoolIfExists trap, root account MFA, and Identity Center settings.
- Golden AMIs without drift: building EC2 images that stay trustworthy How to build and maintain a golden AMI pipeline on EC2 so every instance launches identical — using EC2 Image Builder, versioned images, and replacement instead of in-place patching.
- High availability on AWS: multi-AZ patterns that survive real failures An AWS high availability setup that works when a zone actually degrades: multi-AZ load balancing, autoscaling with capacity to lose, Multi-AZ databases, NAT per zone, and the failure tests that prove it.