In this project, you will build on the skills acquired during this course. You will create and run an instance on AWS, configure Jenkins, and create a pipeline to deploy a static website on S3.
| CRITERIA | MEETS SPECIFICATIONS | COMPLETED | GRADED |
|---|---|---|---|
| Set up IAM credentials properly | A new user with EC2 and S3 access is created that is not the root/admin user in AWS. A screenshot with the unique AWS URL showing should be provided. | ✔️ | |
| Launch EC2 instance | An Ubuntu 18.04 t2.micro is launched and can be accessed via SSH using the PEM file. A screenshot with the unique AWS URL showing should be provided. | ✔️ |
| CRITERIA | MEETS SPECIFICATIONS | COMPLETED | GRADED |
|---|---|---|---|
| Jenkins is installed and running | The Jenkins instance can be reached over HTTP publicly, a login screen should show if not logged in. A screenshot with unique AWS url should be provided. | ✔️ | |
| 'Blue Ocean' is enabled | The 'Blue Ocean' link should show in the sidebar and should load its interface, which is completely different from the standard Jenkins. A screenshot with unique AWS url should be provided. | ✔️ | |
| Barebones Pipeline is added | The GitHub repository is added and shows in the BlueOcean dashboard, automatically recognizing the Jenkinsfile and setting up the initial pipeline that has 1 stage. A screenshot with unique AWS url should be provided. | ✔️ |
| CRITERIA | MEETS SPECIFICATIONS | COMPLETED | GRADED |
|---|---|---|---|
| Publishes the static site to S3 | The index.html file is published to the correct bucket in the right region, and the url is accessible via HTTP from anywhere. A screenshot with unique AWS url should be provided. | ✔️ | |
| Linter catches issues with HTML | After adding a linter, it catches HTML problems with the sample index.html, after addressing the problems with the html, the job passes and publishes the contents once again - build is passing. A screenshot with unique AWS url should be provided. | ✔️ | |
| Jenkinsfile is demonstrated | A Jenkinsfile exists, that has the stages and steps defined that match how the pipeline looks in the Jenkins dashboard. For example 'stage('Lint HTML')' should show as 'Lint HTML' in the pipeline. The AWS credentials and bucket name should all map to an existing S3 bucket that is publicly accessible and that it displays the contents of the index.html file. A screenshot with the S3 URL should be provided. | ✔️ |
The solution consisted of creating an instance EC2 with Jenkins installed and create a pipeline for deploy a static web on S3 bucket, with a Jenkinsfile, also, we connect to this instance by SSH using a KeyPair. Although in the project requirements it did not say about using a CloudFormation stack, instead it specified that everything had to be created through the AWS console, I decided to use a CloudFormation stack template to create the entire infrastructure, including the instance, the S3 bucket, the user and the group with the associated policies, seemed to be a better way since this way I can practice the knowledge acquired in the previous course and it is all more automated, also I installed Jekins using a docker container with docker-compose.
- The
imgfolder has screenshots of the whole process and the diagram solution. - The
srcfolder has the website files to deploy. - The
utilsfolder has the code files using to help such as utilities. - The
docker-composefile is used to install a docker container (on EC2 instance created in the stack) with an image of Jenkins. - The
stack-template.ymlandparameters.jsonfiles are uses to deploy the stack in CloudFormation with all the requirements to this project. - The
Jenkinsfilefile specifies the stages of pipeline in Jenkins to deploy the webpage, this pipeline is created in a declarative way. There is a webhook that was added to the repository, this is useful because any push active a trigger to deploy in Jenkins automatically.
You can access to the final website deployed using this S3 bucket link
