- \n
- How to configure the 2 application servers<\/li>\n
- How to upload application code to our GitLab instance<\/li>\n
- How to write a Jenkins pipeline that integrates with GitLab AWS Fargate to download code<\/li>\n
- How to build a Docker Image<\/li>\n
- How to push the image to Elastic Container Registry (ECR); and<\/li>\n
- How to deploy the demo application as a container into the Fargate service behind a publicly accessible application load balancer<\/li>\n<\/ul>\n
Let\u2019s get started\u2026<\/h2>\n
At the end of part three, we ran a \u2018terraform apply\u2019 command to build out the container services in a VPC. As a result, we produced the following terraform output:<\/p>\n
![\"Terraform\"](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2019\/04\/AWS-Fargate-Blog-4-1.png\")
<\/a><\/p>\nSeveral important variables are printed out at the end, including the Bastion\u2019s Public IP address and the Load Balancer\u2019s Public IP address. We will reference these variables to configure our applications. After we deploy our Jenkins job, we will point our browser to this DNS Name to test the application deployment, so we will need to take note of the DNS Name.<\/p>\n
A couple of one-time tasks are required to setup the GitLab and Jenkins applications. The Jenkins root password must be entered into the Jenkins console and the GitLab database must be initialized and populated using the gitlab-rake command. I will begin by walking you through the initial configuration of both services, beginning with Jenkins.<\/p>\n
Configure Jenkins<\/h2>\n
Accessing the Jenkins Web Console<\/h4>\n
To access the Jenkins web console, enter this DNS Name (printed above) into your favorite browser and append :8080 to the end of the URL. From there, you set the root password, install desired plugins, customize the configuration and begin to build your pipelines.<\/p>\n
Example: http:\/\/private-apps-alb-1114129372.us-east-2.elb.amazonaws.com:8080\/<\/strong><\/p>\n
Jenkins one-time setup tasks<\/h4>\n
![\"Jenkins\"](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2019\/04\/AWS-Fargate-Blog-4-2.png\")
<\/a><\/p>\nWhen you first install the Jenkins Master server, you will be required to locate the auto-generated root password which is stored on the server in \/var\/lib\/jenkins\/secrets\/initialAdminPassword.<\/p>\n
Log into the Bastion host using SSH. From there SSH into the private IP address (obtained from the EC2 console) of the Jenkins Master server and display the contents of the password file. Use this password to log into the Jenkins Master web console by pasting the password into the Jenkins console at the \u2018Administrator password\u2019 prompt shown above.<\/p>\n
![\"Jenkins\"](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2019\/04\/AWS-Fargate-Blog-4-3.png\")
<\/a><\/p>\nExample output<\/h4>\n
![\"Jenkins\"](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2019\/04\/AWS-Fargate-Blog-4-4.png\")
<\/a><\/p>\nOnce the password is entered, you will be led through a few initial configuration screens (shown below). When you see the main user interface, the HA configuration will be complete. By HA, we mean that all data is stored externally on the EFS filesystems, allowing you to complete destroy the EC2 instance without losing data.<\/p>\n
The autoscaling group will automatically deploy a new replacement EC2 instance and attach it to the shared data store allowing you to resume where you left off.<\/p>\n
Jenkins Initial Configuration Screens \u2013 One-Time Task<\/h4>\n
![\"Jenkins\"](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2019\/04\/AWS-Fargate-Blog-4-5png.png\")
<\/a><\/p>\n![\"Jenkins\"](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2019\/04\/AWS-Fargate-Blog-6.png\")
<\/a><\/p>\n![\"Jenkins\"](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2019\/04\/AWS-Fargate-Blog-7.png\")
<\/a><\/p>\nJenkins is now ready!<\/strong><\/p>\n
Configure GitLab<\/h2>\n
Accessing the GitLab Web Console<\/h4>\n
When the terraform script completed successfully, it printed out the Public DNS Name of the Application Load Balancer. Enter this DNS Name into your favorite browser to access the GitLab web console. Once in the console, you can create users, groups and projects and test remote access from your workstation.<\/p>\n
Example: http:\/\/private-apps-alb-1114129372.us-east-2.elb.amazonaws.com\/<\/strong><\/p>\n
Until you complete the initial configuration tasks below, you will see this screen.<\/p>\n
![\"Gitlab\"](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2019\/04\/AWS-Fargate-Blog-8.png\")
<\/a><\/p>\nGitlab one-time setup tasks<\/h4>\n
Log into the Bastion host from your workstation using the previously created SSH key. From the Bastion host, you will SSH into the first GitLab servers to initialize the database with the gitlab-rake command.<\/p>\n
![\"Gitlab\"](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2019\/04\/AWS-Fargate-Blog-9.png\")
<\/a><\/p>\nYou will see a long list of commands running, which is populating the external PostgreSQL database.\u00a0 A snip of the output is below.<\/p>\n
![\"Gitlab\"](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2019\/04\/AWS-Fargate-Blog-10.png\")
<\/a><\/p>\nAfter the gitlab-rake is complete, you can enter the public DNS name again into your browser and GitLab will be ready for you to enter your email address, change the root password and login with the root account. Sample screen flows follow.<\/p>\n
![\"Gitlab\"](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2019\/04\/AWS-Fargate-Blog-11.png\")
<\/a><\/p>\nNext, sign in using Username \u201croot\u201d and the password you entered above.<\/p>\n
![\"Gitlab\"](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2019\/04\/AWS-Fargate-Blog-12.png\")
<\/a><\/p>\nThe Home screen will be presented, and you can create a new user, log in as the new user and create a new project to house your application code.<\/p>\n
The application code you upload will be used to later build a docker image which will be run in as a container in the AWS serverless container service known as Fargate.<\/p>\n
![\"Gitlab\"](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2019\/04\/AWS-Fargate-Blog-13.png\")
<\/a><\/p>\nAt this point, you have a working GitLab instance with all configuration data stored on shared EFS Storage.\u00a0 It is time to scale up the autoscaling group for GitLab from 1 to 2.\u00a0 This will spin up another GitLab instance behind the load balancer and provide for a highly available architecture.<\/p>\n
To do this, simply update the variables.tf file as indicated below and run terraform apply<\/em><\/strong>. Shortly after, a 2nd<\/sup> EC2 instance will be deployed for the second GitLab instance.\u00a0 Verify the new instance in the AWS console.<\/p>\n
![\"Gitlab\"](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2019\/04\/AWS-Fargate-Blog-14.png\")
<\/a><\/p>\nCongratulations! The DevOps platform is setup and ready. Because all of the servers, databases and cache servers are highly available, you can safely terminate any component and within a few minutes, a replacement will be spun up and back to normal operation with no user interaction.<\/p>\n
GitLab Define a Project<\/h2>\n
Create a new user and project to upload your PHP application code.<\/h4>\n
Define a new project named \u201chello-world\u201d in GitLab to house your application code. Click the \u201c+\u201d sign, then \u201cNew project.\u201d<\/p>\n
![\"Gitlab\"](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2019\/04\/AWS-Fargate-Blog-15.png\")
<\/a><\/p>\nEnter project name \u201chello-world.\u201d Set Visibility to \u201cInternal\u201d and select \u201cCreate project.\u201d<\/p>\n
![\"Gitlab\"](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2019\/04\/AWS-Fargate-Blog-16.png\")
<\/a><\/p>\nThe new project will be created and a link to the project will be presented for SSH and HTTP access. The HTTP link will be utilized for the demo purposes to upload code and integrate with Jenkins.<\/p>\n
![\"Gitlab\"](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2019\/04\/AWS-Fargate-Blog-17.png\")
<\/a><\/p>\nClone Hello-World PHP application from the provided demo GitHub repo. This code will then be pushed up to your new GitLab repository created above.<\/p>\n
Create a new working directory for the local repository and run the following \u2018git clone\u2019 command. Verify the code is downloaded.<\/p>\n
![\"Gitlab\"](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2019\/04\/AWS-Fargate-Blog-18.png\")
<\/a><\/p>\nThe sample application code is now cloned from the public GitHub repository to your local repository and can be uploaded to your GitLab repository.<\/p>\n
Change your remote repository to the GitLab repository, changing the repo URL to match the repo name you created in GitLab.<\/p>\n
Note: Change the highlighted repository name to the name of the GitLab repository you created above and ensure you are using HTTP protocol. Next, verify the remote repository and finally push the code to GitHub.<\/p>\n
![\"Gitlab\"](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2019\/04\/AWS-Fargate-Blog-19-273x300.png\")
<\/a><\/p>\nVerify the GitLab project was updated to include the sample PHP application files cloned from GitLab by accessing the URL of your GitLab instance and refreshing the page. (e.g. http:\/\/private-apps-alb-869593036.us-east-2.elb.amazonaws.com\/rich\/hello-temp<\/a>)<\/p>\n