How I Built a File Watcher Program After Forgetting Where I Saved My AWS S3 Files

Too Long; Didn't Read

Part 1: In the first part of the series, the author discusses the challenges of migrating from an Apache server to AWS CloudFront. They emphasize the importance of configuring CloudFront settings correctly, addressing CORS issues in both S3 and CloudFront, and using AWS Route53 for DNS management. The article also touches on SEO strategy adjustments, handling file extensions, and leveraging CloudFront functions for achieving pretty URLs, index behavior in subfolders, and enhancing security headers in responses. Part 2: In this installment, the author provides corrections and insights into their AWS S3 and CloudFront setup. They emphasize the need to maintain old canonical URLs and clarify the misconceptions surrounding HTTP status codes 301 and 304. The article also discusses the advantages of using an AWS SSL certificate, managing DNS records, and highlights the importance of having separate S3 buckets for www versions. It addresses the nuances of SEO in the AWS environment and advises against unnecessary re-SEO efforts. Part 3: This part delves into how to make AWS S3 behave more like a web server by using CloudFront Functions. The author focuses on three aspects: managing pretty URLs and handling redirects, enabling default index behavior for subfolders, and configuring response security headers. They explain the importance of these functions in enhancing the S3 and CloudFront setup to mimic an Apache server more effectively, making it suitable for hosting websites.