Deploy your own production-ready Jenkins in AWS ECS

Deploying a continuous integration service such as Jenkins is an important step when kicking off your development project. In this video you’ll discover how to deploy Jenkins into the AWS Elastic Container Service (ECS), meaning you’ll have your own highly available Jenkins instance ready for you over the internet. We’ll be following all the best practices to get Jenkins production-ready, including making sure: ✅ Jenkins is always available to you even if an entire AWS availability zone goes down ✅ all Jenkins data is stored on a persistent volume ✅ Jenkins runs inside a private network with strict security controls to ensure nobody except authenticated users have access ✅ any changes to the infrastructure can be made easily via AWS CloudFormation templates This video follows a full worked example that you can afterwards apply to your own AWS account. It has the following sections: ▶️ Introduction 0:00 ▶️ Jenkins architecture 1:28 ▶️ ECS summary 2:58 ▶️ Why use ECS & Jenkins? 4:50 ▶️ Prerequisites for example 8:41 ▶️ Applying the CloudFormation example 10:27 ▶️ Viewing the new Jenkins deployment 13:17 LAUNCH STACK 🚀 the following link will launch the CloudFormation stack in your AWS account https://console.aws.amazon.com/cloudformation/home#/stacks/new?stackName=jenkins-for-ecs&templateURL=https://tomgregory-cloudformation-examples.s3-eu-west-1.amazonaws.com/jenkins-for-ecs.yml CLOUDFORMATION TEMPLATE this is the main template to create the Jenkins resources https://tomgregory-cloudformation-examples.s3-eu-west-1.amazonaws.com/jenkins-for-ecs.yml NESTED STACK TEMPLATE this template is used by the one above to create the underlying networking resources https://tomgregory-cloudformation-examples.s3-eu-west-1.amazonaws.com/default-vpc.yml ACCOMPANYING ARTICLE check out the article on my website which goes into more detail https://jenkinshero.com/deploy-jenkins-into-aws-ecs/