197 articles
Knowledge Base
AWS
197 articles in the AWS category · page 4 of 9.
- Hosting a static website on S3 + CloudFront: the current correct way The current correct way to host a static website on S3 with CloudFront: a private bucket behind Origin Access Control, an ACM certificate in us-east-1, and a function for subdirectory index pages.
- How to evaluate an AWS cloud management company: 12 questions that expose the pretenders Choosing an AWS cloud management company is hard because every website says the same things. These 12 questions separate firms that run production from firms that sell dashboards.
- How to reduce your AWS bill: the 12 levers, ranked by effort-to-savings A ranked, practical list of the 12 levers that actually reduce an AWS bill — from deleting orphaned resources to Savings Plans — ordered by effort versus savings, with the commands to verify each one.
- IAM Identity Center (SSO): moving humans off IAM users How to set up IAM Identity Center (AWS SSO) and migrate human access off IAM users: permission sets, external identity providers, aws configure sso, and the migration runbook that does not break anyone.
- IAM permission boundaries: delegating IAM safely to teams IAM permission boundaries let teams create their own roles without being able to escalate privileges. How boundaries actually work, the delegation pattern with working JSON, and the gaps they do not cover.
- IAM policy examples: the 12 policies every AWS account ends up needing Twelve IAM policy examples that show up in practically every production AWS account — app roles scoped to one bucket, region lockdowns, tag-based EC2 control, MFA enforcement, and more, with working JSON.
- IAM roles vs users: when each is right (and why access keys should be rare) IAM roles vs users is settled for workloads — roles win. The real decision is what to do with humans and the handful of cases where a user with access keys still earns its place.
- InsufficientInstanceCapacity error: what it means and the real workarounds The InsufficientInstanceCapacity error means AWS has no spare hardware for that instance type in that Availability Zone right now. Here is what actually works: other AZs, other types, and capacity reservations.
- Lambda cold starts: what actually helps in 2026 (and what is cargo cult) Most Lambda cold start advice is outdated. What actually reduces cold start latency in 2026 — package size, init discipline, SnapStart, provisioned concurrency — and which popular tricks do nothing.
- Lambda dead letter queues and destinations: catching failed events before they vanish Async Lambda events that fail all retries are silently dropped unless you configure a dead letter queue or an on-failure destination. How the two differ, which to pick, and how to set them up.
- Lambda environment variables and secrets: Parameter Store vs Secrets Manager in practice Lambda environment variables are not a secrets store. When to use Parameter Store, when Secrets Manager earns its cost, and how to fetch secrets from Lambda without paying an API call on every invocation.
- Lambda in a VPC: the networking mistakes that break internet and RDS access Attach a Lambda function to a VPC and suddenly it cannot reach the internet, or it still cannot reach RDS. The five networking mistakes behind almost every Lambda VPC failure, and how to fix each one.
- Lambda layers: sharing dependencies without version chaos Lambda layers let functions share dependencies, but unpinned layer versions quietly desynchronize environments. How layers actually work, the limits that bite, and the versioning discipline that prevents chaos.
- Lambda memory sizing: the memory-CPU link and finding the cost sweet spot Lambda memory controls CPU too, so more memory often means faster and sometimes cheaper. How to find the memory setting where cost and duration balance, with real measurement instead of guessing.
- Lambda task timed out: diagnosing where the time went The Lambda "Task timed out after X seconds" error means the function hit its configured timeout, not that something crashed. Here is how to find where the time actually went and fix the right thing.
- Lambda throttling (Rate exceeded, 429): concurrency limits explained and fixed Lambda 429 TooManyRequestsException and Rate exceeded errors mean you have hit a concurrency limit. How Lambda concurrency actually works, how to see which limit you hit, and how to fix it.
- Least privilege in practice: Access Analyzer and unused-permission pruning Least privilege on AWS is a pruning loop, not a rewrite. How IAM Access Analyzer external and unused-access findings, last-accessed data, and CloudTrail-based policy generation shrink permissions safely.
- Managed WordPress hosting on AWS: performance, security, backups, and updates owned end to end AWS WordPress hosting management means someone owns every layer a managed host used to own: updates, security, backups, restores, and scaling. Here is what end-to-end ownership actually covers.
- Migrating servers to AWS: the runbook from inventory to cutover A practical runbook to migrate servers to AWS with Application Migration Service: inventory, replication, test instances, cutover, and the checks that keep the weekend boring.
- Moving an EC2 instance to another AZ or Region: the AMI copy runbook You cannot move an EC2 instance directly — you image it and relaunch. The full runbook for moving an instance to another Availability Zone or Region: AMI creation, copy-image, networking, and cutover.
- NAT Gateway errors and port allocation exhaustion: symptoms and fixes Intermittent outbound timeouts through a NAT Gateway usually mean ErrorPortAllocation: too many concurrent connections to the same destination. How to confirm it and the four ways to fix it.
- On-premises to AWS: retiring the server room without a weekend disaster An AWS migration from on premise fails on the things around the servers — AD, DNS, file shares, the VPN, the bandwidth math. Here is how to retire the server room in the right order.
- Post-migration optimization: it works, but it is expensive, fragile, and unmonitored AWS post migration optimization in the order that pays: rightsizing and storage cleanup first, then reliability gaps the lift-and-shift left behind, then the monitoring nobody set up.
- Provisioned concurrency: when it is worth paying to skip Lambda cold starts Provisioned concurrency eliminates Lambda cold starts by keeping initialized environments waiting — billed whether traffic arrives or not. The break-even logic, the setup, and the cases where it is money wasted.