AWS Managed CloudFront

Hey there!,

For your first question, when you connect an API Gateway to a custom domain in AWS, it automatically configures **CloudFront **with settings aimed at security and efficient request handling. Key points include HTTPS as the only protocol, using port 443, and a strict TLSv1.2 minimum for secure connections. The setup is optimized for dynamic content, meaning caching is generally disabled to ensure live data is always served.

If you're thinking of switching to a user-managed CloudFront setup instead of the default AWS managed one, it's crucial to replicate these security and performance settings closely. Ensure your **CloudFront **distribution sticks to HTTPS, maintains high security standards with TLSv1.2, and carefully considers any caching strategies to suit your dynamic content. Adjustments like custom paths, headers, and timeout settings will help match AWS's default setup but give you the freedom to tailor your configuration further.

Hope this helps clarify things!