This documentation outlines the architecture, setup steps, and maintenance practices for a CI/CD pipeline that automates the deployment of a Jekyll site hosted in an Amazon S3 bucket, using AWS CodePipeline and GitHub as the source repository.

The pipeline automates:

1. Source Management: Fetching code from a GitHub repository.
2. Build Process: Running Jekyll to generate static files.
3. Deployment: Uploading the generated static files to an S3 bucket under a specified folder.

+-----------------+             +------------------+             +---------------------+
|   GitHub Repo   |             |  AWS CodeBuild   |             |        S3           |
|  (Source Code)  |    --->     |  (Generate Site) |    --->     |  (Host /resume)     |
+-----------------+             +------------------+             +---------------------+
       Webhook                         Buildspec                          Static Site

1. CodePipeline: Orchestrates the pipeline workflow.
2. CodeBuild: Builds the Jekyll site and organizes files.
3. S3: Hosts the static website and serves it publicly.

• Log in to the AWS Management Console.
• Navigate to S3.
• Create a bucket (e.g., my-jekyll-site-bucket).
• Enable Static Website Hosting under the bucket's Properties.
• Set the Index Document to resume/index.html.

Configure the bucket policy to allow public read access for objects:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "PublicReadGetObject",
      "Effect": "Allow",
      "Principal": "*",
      "Action": "s3:GetObject",
      "Resource": "arn:aws:s3:::my-jekyll-site-bucket/*"
    }
  ]
}

Create a service role for CodePipeline:

• Attach the managed policy AWSCodePipelineFullAccess.

Create a service role for CodeBuild:

• Attach the managed policies:
  • AWSCodeBuildDeveloperAccess
  • AmazonS3FullAccess

• Navigate to CodePipeline in the AWS Management Console.
• Click Create Pipeline and provide a name (e.g., JekyllPipeline).

• Source Provider: Select GitHub Version 2.
• Connect to GitHub: Authenticate and select the repository and branch (e.g., main).
• Set up a webhook for automatic triggers.

• Build Provider: Select AWS CodeBuild.
• Create a CodeBuild Project:
  • Environment:
    • Runtime: Ubuntu with Ruby support.
    • Image: aws/codebuild/standard:5.0 (or latest).
  • Buildspec File: Select "Use a buildspec file."

• Deploy Provider: Select Amazon S3.
• Specify the target bucket (e.g., my-jekyll-site-bucket) and folder (resume).

Add the following buildspec.yml file to your GitHub repository root:

version: 0.2

phases:
  install:
    runtime-versions:
      ruby: 2.7
    commands:
      - gem install bundler
      - bundle install
  build:
    commands:
      - bundle exec jekyll build
      - mkdir -p build_output/resume
      - mv _site/* build_output/resume
artifacts:
  files:
    - '**/*'
  base-directory: 'build_output'

1. Push changes to the GitHub repository.

2. Monitor the pipeline in the AWS Console.

3. Access the site:

   http://your-bucket-name.s3-website-region.amazonaws.com/resume/resume.html

• Use the CodePipeline Console to monitor each stage.
• Check logs for failed builds in the CodeBuild Console.

• Source Changes:
  • Modify the GitHub branch or repository in the pipeline source stage.
• Build Changes:
  • Update the buildspec.yml file to include new build steps.
• Deployment Changes:
  • Adjust S3 bucket or folder configurations in the deployment stage.

• Periodically update Ruby gems in your project by running:

  bundle update

• Enable CloudFront for faster content delivery.
• Add caching policies for S3 objects.

• Monitor usage costs using the AWS Cost Explorer.
• Enable S3 Object Expiration to clean up old files.

• Regularly review and limit IAM roles’ permissions.
• Enable S3 Server Access Logging for audit purposes.

1. Hosted Website
2. Version Control System
3. CI/CD Pipeline Setup
4. Documentation

1. Add Testing:
   • Integrate testing tools (e.g., HTML validation) into the pipeline.
2. CloudFront with SSL:
   • Use Amazon CloudFront for HTTPS and faster delivery.
3. Multi-Environment Support:
   • Set up separate pipelines for staging and production.
4. Automate Pipeline Updates:
   • Use AWS CloudFormation to define and manage the pipeline as code.