S3 to Lambda: Direct Trigger vs SQS in the Middle
Direct S3-to-Lambda triggers are simple, but burst traffic and slow downstream systems change the decision. Here is when SQS belongs in the middle.
Complete archive
All InfraTales articles.
Browse every published guide, architecture pattern, cost teardown, and failure analysis. Use search for titles, excerpts, tags, and authors, or move into a topic hub for a curated reading order.
Newest first
Published work
S3 to Lambda Through EventBridge: Cost, Audit, and Routing Trade-offs
Choose direct S3 events or CloudTrail data events for EventBridge without paying for an audit path your Lambda trigger does not require.
AWS CodeDeploy on EC2 Auto Scaling: ALB Health, Rollback, and Safe Releases
Wire CodeDeploy, an Auto Scaling group, and an ALB so new instances receive the right revision and failed releases stop and roll back.
AWS Web App on Fargate, Aurora, and CloudFront: Production Boundaries That Matter
Design the traffic, network, database, secret, scaling, and cost boundaries for a Fargate web application instead of stopping at deployment.
Orchestrating DataSync, DMS, and Glue with Step Functions Without Silent Gaps
Model DataSync, DMS, Glue, and indexing as observable jobs with explicit wait, validation, retry, and reconciliation states.
AWS IAM and VPC Security as Code: KMS, Endpoints, WAF, and Security Hub
Turn IAM, KMS, private service access, WAF, and Security Hub into testable controls without confusing detection with prevention.