Citizens download large zoning PDFs that currently hairpin through EC2 and a NAT Gateway before reaching users. Which delivery path is more cost-efficient for public downloads?
Select an answer to reveal the explanation.
Short Explanation
Don't route the town newsletter through the basement boiler room. Put public PDFs on S3 and CloudFront instead of NAT/EC2 hairpins.
Full Explanation
Public static downloads are most cost-efficient from S3 and CloudFront, avoiding EC2 proxy compute and NAT data-processing charges. Intentionally hairpinning through NAT/EC2 increases cost. RDS email triggers and per-home Direct Connect are impractical and expensive delivery paths for citizen PDFs.