197 articles
Knowledge Base
AWS
197 articles in the AWS category · page 6 of 9.
- S3 cost optimization: storage classes, lifecycle rules, and the requests line nobody reads S3 cost optimization beyond storage classes: lifecycle rules that actually pay off, the request charges nobody reads, versioning bloat, and abandoned multipart uploads.
- S3 Intelligent-Tiering: when it saves money and when it just adds monitoring fees S3 Intelligent-Tiering moves objects between access tiers automatically, but the per-object monitoring fee means it only pays off for larger objects. Here is how to decide.
- S3 Inventory and Storage Lens: seeing what is actually in your buckets How to use S3 Inventory and S3 Storage Lens to see what is actually in your buckets — object-level reports queryable with Athena, fleet-wide cost metrics, and the setup for both.
- S3 multipart uploads: the incomplete-part charges hiding in your bucket and how to clean them up Failed multipart uploads leave parts in S3 that bill as storage but never show in object listings. How to find incomplete multipart uploads, abort them, and stop them recurring with a lifecycle rule.
- S3 Transfer Acceleration: when it helps and how to test if it does S3 Transfer Acceleration routes uploads through CloudFront edge locations for a per-GB fee. When it actually speeds things up, when multipart tuning beats it for free, and how to test before paying.
- Scheduling non-production environments off-hours: the easiest 60%+ on dev/staging compute How to schedule AWS dev and staging environments to stop off-hours: ASG scheduled actions, EventBridge Scheduler, RDS stop automation, and the 7-day restart trap.
- Signs your AWS environment has outgrown your team When AWS infrastructure management starts consuming your developers, the signs are concrete: stale patches, untested backups, mystery spend, one-person knowledge. Here is the honest checklist.
- Staging environments on AWS without doubling the bill A useful AWS staging environment keeps production's architecture, not its capacity or its uptime. Scheduling, smaller instances, Spot, and expiry dates typically hold staging to a fraction of the production bill.
- The AWS Well-Architected review, explained for non-enterprise teams What an AWS Well-Architected review actually is: a structured question set across six pillars, free tooling in the console, and how a small team gets real value from it without enterprise ceremony.
- The monthly AWS operations checklist: what disciplined accounts review every 30 days A monthly AWS operations checklist covering cost anomalies, rightsizing, orphaned resources, IAM hygiene, backup verification, Health events, and patching — the 90-minute review that keeps accounts from drifting.
- Using the EC2 serial console when SSH is dead The EC2 serial console gives you an out-of-band terminal into an instance when SSH is dead — no working network required. Here is how to enable it, log in, and fix the firewall, fstab, or sshd mistake that locked you out.
- VPC DNS resolution failures: Route 53 Resolver, enableDnsHostnames, and hybrid DNS DNS inside a VPC fails for a short list of reasons: VPC attributes turned off, private hosted zones not associated, resolver endpoints missing for hybrid, or the per-ENI query limit. Here is the diagnostic path.
- VPC endpoint not being used: why traffic still goes through the NAT Gateway You created a VPC endpoint but the NAT Gateway bill did not move. Gateway endpoints fail on route table association, interface endpoints fail on private DNS. Here is how to prove which and fix it.
- VPC peering not working: the route, security group, and DNS checklist An active VPC peering connection that passes no traffic almost always has missing routes on one side, security groups that block the peer CIDR, or DNS resolution left off. Work this checklist in order.
- VPC Reachability Analyzer: proving exactly where a connection dies Reachability Analyzer walks your VPC configuration hop by hop and names the security group, route table, or NACL that blocks a path. How to run it, read the findings, and know its limits.
- VPC route tables debugged: why traffic is not going where you think When VPC traffic takes the wrong path, the cause is almost always route table association, longest-prefix matching, or a blackhole route. Here is how to debug AWS route tables methodically.
- What a real AWS cost audit covers (and what a free "assessment" skips) A real AWS cost audit examines usage data, architecture, commitments, and governance — not just a Cost Explorer screenshot. Here is the full scope, and what free assessments leave out.
- What an AWS architecture review actually finds: the recurring failures in real accounts An AWS architecture review keeps finding the same eight problems: single-AZ databases, one NAT gateway, untested backups, IAM sprawl, and alarms that page nobody. Here is the list and how to self-check.
- WooCommerce on AWS: the operations checklist for stores that cannot drop orders Running WooCommerce on AWS without dropping orders comes down to a checklist: durable order writes, sessions off local disk, cache rules that never touch checkout, and restore drills that count orders.
- Scaling on a custom metric — queue depth, not CPU CPU is a lagging proxy on workloads where the bottleneck is the queue. The right metric is the thing you actually want to control. Here is how to publish it, alarm on it, and do the math for what 100 requests per instance means after the scale event lands.
- ASG lifecycle hooks done right — draining, deregistering, and the heartbeat pattern The default ASG terminates a spot instance two minutes after the warning. Two minutes is fine if your hook drains the LB, flushes logs, and deregisters from service discovery. Here is the pattern that does all three reliably.
- Parameter group tuning for production Postgres / MySQL on RDS — the diff that actually matters max_connections, shared_buffers, work_mem, log retention. The static-vs-dynamic restart trap that catches teams who edit the wrong parameter group at the wrong time. A real diff for a 4-core 32GB Postgres SaaS workload.
- CodeBuild Docker layer caching — from 6-minute builds to 90 seconds Local docker layer cache vs ECR --cache-from, BuildKit on CodeBuild, build-time secrets. Real timing numbers and the configuration that actually works.
- Canary deploys on Lambda — the pre/post-traffic hooks that actually catch regressions CodeDeployDefault.LambdaCanary10Percent5Minutes only works if the validation hook does something real. Here is the hook that runs a smoke probe and checks CloudWatch error rate before promoting.