Day 71: Secure your Naked Domain & Stop SQS from DDOSing your API

Today I fixed two major production risks in my Serverless Fintech app.

1. Fixing the HTTPS "Not Secure" warning on Apex Domains
   If users type duromoney.com, they shouldn't see a security error.
   Fix: Go to your DNS registrar (e.g., IONOS) and delete standard redirects. Create an A-Record for @ pointing to your hosting provider's Load Balancer IP. Then, provision an SSL certificate that explicitly covers both the root and www domains.

2. Preventing SQS from breaking downstream APIs
   My SES email limit is 14/sec. If SQS dumps 10k messages into AWS Lambda, the system crashes from 429 Rate Exceeded errors.
   Fix: Do NOT use Lambda Reserved Concurrency (it blocks your web API traffic if you use a Fat Lambda pattern). Instead, set the Maximum Concurrency directly on the SQS Trigger (Event Source Mapping) to 10. SQS is now bottlenecked at the source, processing messages smoothly without hitting rate limits.

Build for speed, but configure for control!