AWS Static Website Deployment

Back to Resume

Overview of the Architecture

  1. S3 (Simple Storage Service):

    I stored the website’s static assets, including HTML, CSS, and JavaScript files, in an S3 bucket. S3 is an ideal service for this because it provides a scalable and durable storage solution. The S3 bucket is configured to host a static website, making it publicly accessible.

  2. CloudFront Distribution:

    To improve the website’s performance and security, I set up a CloudFront distribution. CloudFront is a Content Delivery Network (CDN) that caches content in edge locations worldwide, reducing latency by serving content closer to users. It also provides HTTPS support, ensuring secure communication between users and the website.

    The CloudFront distribution is linked to the S3 bucket, fetching and delivering the stored files to the end-users.

  3. Public Hosted Zone and DNS Configuration:

    To make the website accessible via a custom domain name, I registered “franckyeboue.com” and set up a Public Hosted Zone in Amazon Route 53, which is AWS’s DNS service.

    I created an A record with an alias in the hosted zone. This record points to the CloudFront distribution, allowing users to access the website using the domain name “franckyeboue.com”.

  4. How it Works:

    When a user navigates to “franckyeboue.com”, their browser sends a request to the DNS service (Route 53), which resolves the domain to the CloudFront distribution.

    CloudFront then retrieves the requested content (e.g., index.html) from the S3 bucket and delivers it to the user’s browser, ensuring fast and secure access.