There are lot of tutorials out there that show how to create a pipeline to deploy apps on AWS Beanstalk using CircleCI but they were either for Version 1 or simply didn’t work because incorrectly set AWS credentials. That’s why I decided to write a tutorial which has all the steps needed to automatically deploy to AWS Elastic Beanstalk.<\/p>\n
Beanstalk is an amazing service to deploy and scale web apps and services written in Java,\u00a0.NET, PHP, Node.js, Python, Ruby, Go, and\u00a0Docker.<\/p>\n
I find it super convenient, with our setup I can simply push my code into a repository and CircleCI deploys to Beanstalk which then takes care of the provisioning of the underlying EC2 instances.<\/p>\n
In this tutorial we are going to deploy a small dummy NodeJS application using Github and CircleCI 2.0.<\/p>\n
Overview of the tutorial:<\/h2>\n
1. Setup – We are going to create an AWS IAM user which will be used later with CircleCI to handle Beanstalk
\n2. Add Credentials to your local AWS EB CLI to spin up the Beanstalk environment
\n3. Beanstalk Environment – Deployment of the Beanstalk Environment
\n4. Connecting your Git Repository to CircleCI
\n5. Connect AWS to CircleCI using IAM Credentials
\n6. Create the CircleCI Config in the Repository
\n7. Happy Deploying<\/p>\n
Requirement:<\/strong><\/h2>\n\n- Python and PIP installed<\/li>\n
- AWS Account with Admin Access to generate API credentials<\/li>\n
- CircleCI account setup and linked to a GitHub or Bitbucket Repository<\/li>\n<\/ul>\n
Step 1: Setup IAM User<\/strong><\/h2>\nBefore starting to use CircleCI to deploy apps to Beanstalk, we need to generate API credentials that will then be used by CircleCI to execute the necessary commands. In order to generate the API credentials, sign into your\u00a0AWS Management Console<\/strong><\/a>\u00a0and go to \u201cIdentity and Access Management \u2013 IAM<\/strong>\u201d:<\/p>\nThen, click on \u201cAdd user<\/strong>\u201d :<\/p>\n![\"circleci](\"https:\/\/kevingoedecke.com\/blog\/wp-content\/uploads\/2018\/03\/Add-user-1st-page-1024x471.png\")
<\/a><\/p>\nAssign a\u00a0username<\/strong>\u00a0for the new account and select \u201cProgrammatic access<\/strong>\u201c:<\/p>\n![\"circleci](\"https:\/\/kevingoedecke.com\/blog\/wp-content\/uploads\/2018\/03\/IAM-user-programmatic-access-1024x507.png\")
<\/a><\/p>\nAdd \u201cAmazonElasticBeanstalkFullAccess<\/strong>\u201d to user permissions list, this is whats needed for CircleCI to deploy to Beanstalk.<\/p>\n![\"circleci](\"https:\/\/kevingoedecke.com\/blog\/wp-content\/uploads\/2018\/03\/Full-permission-1024x507.png\")
<\/a><\/p>\nNext, click on \u201cReview<\/strong>\u201d then “Create User”<\/strong>:<\/p>\n![\"circleci](\"https:\/\/kevingoedecke.com\/blog\/wp-content\/uploads\/2018\/03\/Add-user-1024x434.png\")
<\/a><\/p>\nYou’ll see your Access key ID and your Secret access Key. Both will be used later to trigger the Beanstalk commands from CircleCI.<\/p>\n
Step 2: Add AWS Credentials locally<\/h2>\n
Using the AWS CLI locally we will spin up the Beanstalk environment that will be later used by CircleCI to deploy to. In order to use AWS CLI or EB CLI on your local computer we first need to create a credentials file (~\/.aws\/credentials<\/span>\u00a0) and store the IAM user credentials in it.<\/p>\nEdit\u00a0~\/.aws\/credentials<\/span>\u00a0 and add the following content (replace YOUR_ACCESS_KEY_ID and YOUR_SECRET_ACCESS_KEY with the credentials generated in the previous step):<\/p>\n[eb-cli]\r\naws_access_key_id=YOUR_ACCESS_KEY_ID\r\naws_secret_access_key=YOUR_SECRET_ACCESS_KEY<\/pre>\nStep 3:\u00a0 Install EB CLI<\/h2>\n
In this section, we are going to install\u00a0AWS EB CLI<\/a>.<\/strong><\/p>\nThis step requires Python and pip installed locally. If you have everything ready execute the following command:<\/p>\n
pip install --upgrade --user awsebcli<\/pre>\nAfter you’ve installed the\u00a0EB CLI<\/strong>, add the path to the executable file to your\u00a0PATH<\/strong>\u00a0variable.<\/p>\nStep 4: Create your Elastic Beanstalk environment<\/h2>\n
It’s time to create your Elastic Beanstalk Environment using the EB CLI from your local machine. Just navigate to your app directory (that needs to be deployed to Beanstalk later) and execute eb init<\/span>\u00a0 to initialize the directory as a Beanstalk application. NOTE: Alternatively you also use the AWS Management dashboard to create your Elastic Beanstalk environment.<\/strong><\/p>\nChange into the directory of your app:<\/p>\n
cd ~\/workspace\/my-dummy-app\r\n<\/pre>\nInitialize the app as a Beanstalk application:<\/p>\n
eb init --profile eb-cli\r\n\r\nSelect a default region\r\n1) us-east-1 : US East (N. Virginia)\r\n2) us-west-1 : US West (N. California)\r\n3) us-west-2 : US West (Oregon)\r\n4) eu-west-1 : EU (Ireland)\r\n5) eu-central-1 : EU (Frankfurt)\r\n6) ap-south-1 : Asia Pacific (Mumbai)\r\n7) ap-southeast-1 : Asia Pacific (Singapore)\r\n8) ap-southeast-2 : Asia Pacific (Sydney)\r\n9) ap-northeast-1 : Asia Pacific (Tokyo)\r\n10) ap-northeast-2 : Asia Pacific (Seoul)\r\n11) sa-east-1 : South America (Sao Paulo)\r\n12) cn-north-1 : China (Beijing)\r\n13) cn-northwest-1 : China (Ningxia)\r\n14) us-east-2 : US East (Ohio)\r\n15) ca-central-1 : Canada (Central)\r\n16) eu-west-2 : EU (London)\r\n17) eu-west-3 : EU (Paris)\r\n(default is 3): 5\r\n\r\nSelect an application to use\r\n1) server-backend\r\n2) [ Create new Application ]\r\n(default is 2): 2\r\n\r\nEnter Application Name\r\n(default is \"circleci-beanstalk-example\"):\r\nApplication circleci-beanstalk-example has been created.\r\n\r\nIt appears you are using Node.js. Is this correct?\r\n(Y\/n): Y\r\nNote: Elastic Beanstalk now supports AWS CodeCommit; a fully-managed source control service. To learn more, see Docs: https:\/\/aws.amazon.com\/codecommit\/\r\nDo you wish to continue with CodeCommit? (y\/N) (default is n):\r\nDo you want to set up SSH for your instances?\r\n(Y\/n): n<\/pre>\nThis will initialize your application and the environment, you’ll notice that the command has created a .elasticbeanstalk<\/span>\u00a0 folder in your application. Afterwards we can go ahead and actually spin up the enviroment.<\/p>\nExecute the following command, make sure you use eb-cli<\/span>\u00a0 as the profile, because thats how we named our credentials in the ~\/.aws\/credentials<\/span>\u00a0 file<\/p>\neb create --profile eb-cli\r\nEnter Environment Name\r\n(default is circleci-beanstalk-example-dev):\r\nEnter DNS CNAME prefix\r\n(default is circleci-beanstalk-example-dev):\r\n\r\nSelect a load balancer type\r\n1) classic\r\n2) application\r\n3) network\r\n(default is 1): 2\r\nWARNING: You have uncommitted changes.\r\nCreating application version archive \"app-6207-180303_000424\".\r\nUploading circleci-beanstalk-example\/app-6207-180303_000424.zip to S3. This may take a while.\r\nUpload Complete.\r\nEnvironment details for: circleci-beanstalk-example-dev\r\n Application name: circleci-beanstalk-example\r\n Region: eu-central-1\r\n Deployed Version: app-6207-180303_000424\r\n Environment ID: e-x4dhchqab3\r\n Platform: arn:aws:elasticbeanstalk:eu-central-1::platform\/Node.js running on 64bit Amazon Linux\/4.4.5\r\n Tier: WebServer-Standard-1.0\r\n CNAME: circleci-beanstalk-example-dev.eu-central-1.elasticbeanstalk.com\r\n Updated: 2018-03-02 23:04:27.933000+00:00\r\nPrinting Status:\r\nINFO: createEnvironment is starting.\r\nINFO: Using elasticbeanstalk-eu-central-1-216820535158 as Amazon S3 storage bucket for environment data.\r\nINFO: Created target group named: arn:aws:elasticloadbalancing:eu-central-1:216820535158:targetgroup\/awseb-AWSEB-1ESP9MVJF03WM\/c0c2e625e11502da\r\nINFO: Created security group named: sg-3017c85d\r\nINFO: Created security group named: awseb-e-x4dhchqab3-stack-AWSEBSecurityGroup-389LSAY1654Q\r\nINFO: Created Auto Scaling launch configuration named: awseb-e-x4dhchqab3-stack-AWSEBAutoScalingLaunchConfiguration-1363I5EH0W93A\r\n -- Events -- (safe to Ctrl+C)\r\nINFO: Created Auto Scaling group named: awseb-e-x4dhchqab3-stack-AWSEBAutoScalingGroup-618KCZ091L2D\r\nINFO: Waiting for EC2 instances to launch. This may take a few minutes.\r\nINFO: Created Auto Scaling group policy named: arn:aws:autoscaling:eu-central-1:216820535158:scalingPolicy:968245fa-08a9-434c-ae14-2683532a868b:autoScalingGroupName\/awseb-e-x4dhchqab3-stack-AWSEBAutoScalingGroup-618KCZ091L2D:policyName\/awseb-e-x4dhchqab3-stack-AWSEBAutoScalingScaleDownPolicy-J2G5Z2VU5CU2\r\nINFO: Created Auto Scaling group policy named: arn:aws:autoscaling:eu-central-1:216820535158:scalingPolicy:74b34e27-91b2-4654-ae4a-1adac1f12bd1:autoScalingGroupName\/awseb-e-x4dhchqab3-stack-AWSEBAutoScalingGroup-618KCZ091L2D:policyName\/awseb-e-x4dhchqab3-stack-AWSEBAutoScalingScaleUpPolicy-1084AE1QSLJED\r\nINFO: Created CloudWatch alarm named: awseb-e-x4dhchqab3-stack-AWSEBCloudwatchAlarmLow-1N62LDQ99LOQU\r\nINFO: Created CloudWatch alarm named: awseb-e-x4dhchqab3-stack-AWSEBCloudwatchAlarmHigh-1RKTU1TGKSTPM\r\nINFO: Created load balancer named: arn:aws:elasticloadbalancing:eu-central-1:216820535158:loadbalancer\/app\/awseb-AWSEB-1SMYH0Q88CKQP\/31bb253db6f8c427\r\nINFO: Created Load Balancer listener named: arn:aws:elasticloadbalancing:eu-central-1:216820535158:listener\/app\/awseb-AWSEB-1SMYH0Q88CKQP\/31bb253db6f8c427\/26fbd477342dee44\r\nINFO: Successfully launched environment: circleci-beanstalk-example-devssss<\/pre>\nStep 4: Connect Repo with CircleCI<\/h2>\n
Now that our application environment is up and running (please verify that it actually is using the AWS Management Dashboard), we can go ahead and connect CircleCI to Beanstalk.<\/p>\n
CircleCI needs a repository to pull the code from. Currently CircleCI supports GitHub and BitBucket. Go to\u00a0https:\/\/circleci.com\/signup\/<\/a><\/p>\nand Click on Signup with Github or Bitbucket. You should login into Github and Bitbucket before this.<\/p>\n
![\"circleci](\"https:\/\/kevingoedecke.com\/blog\/wp-content\/uploads\/2018\/03\/Screen-Shot-2018-03-09-at-12.54.06-1024x336.png\")
<\/a><\/p>\nStep 5:<\/strong> Add IAM user Credentials in CircleCI<\/h2>\nAfter you’ve linked your repository to your CircleCI account, head over to the CircleCI Dashboard<\/a> and navigate into your project. Click on the settings icon of the repository that you want to setup.<\/p>\n![\"circleci](\"https:\/\/kevingoedecke.com\/blog\/wp-content\/uploads\/2018\/03\/circleci-beanstalk-settings-1024x624.png\")
<\/a><\/p>\nIn the Settings section scroll down and click on “AWS Permissions” as shown in the screenshot below. Insert your access and secret key of the “circleci” programmatic user that we created previously using the AWS Dashboard.<\/p>\n
![\"circleci](\"https:\/\/kevingoedecke.com\/blog\/wp-content\/uploads\/2018\/03\/AWS-permissions-1024x455.png\")
<\/a><\/p>\nStep 6: Create CircleCI config<\/strong><\/h2>\nWe are going to use CircleCI version 2.0 <\/strong>because\u00a0<\/strong>CircleCI<\/strong> is officially discontinuing support for\u00a0CircleCI 1.0\u00a0<\/strong>builds after August 31st, 2018.<\/p>\nCreate\u00a0.circleci\/config.yml<\/span>\u00a0\u00a0inside the root directory of your application\u00a0and add it to your repository. CircleCI automatically sets two environment variables ($AWS_ACCESS_KEY_ID<\/span>\u00a0 and $AWS_SECRET_ACCESS_KEY<\/span>\u00a0). We will use those variables to configure the AWS EB CLI.<\/p>\nversion: 2\r\njobs:\r\n deploy:\r\n docker:\r\n - image: circleci\/python:2.7\r\n working_directory: ~\/repo\r\n steps:\r\n - checkout\r\n - run:\r\n name: Install awscli\r\n command: |\r\n sudo pip install awsebcli --upgrade\r\n - run:\r\n name: Create AWS credentials manually\r\n command: |\r\n mkdir ~\/.aws\r\n touch ~\/.aws\/config\r\n chmod 600 ~\/.aws\/config\r\n echo \"[profile eb-cli]\" > ~\/.aws\/config\r\n echo \"aws_access_key_id=$AWS_ACCESS_KEY_ID\" >> ~\/.aws\/config\r\n echo \"aws_secret_access_key=$AWS_SECRET_ACCESS_KEY\" >> ~\/.aws\/config\r\n - run:\r\n name: Deploy to EB if branch is Master\r\n command: |\r\n eb use circleci-beanstalk-example --profile eb-cli\r\n eb deploy -v --staged --profile eb-cli\r\n\r\nworkflows:\r\n version: 2\r\n build-deploy:\r\n jobs:\r\n - deploy:\r\n filters:\r\n branches:\r\n only:\r\n - master\r\n - develop<\/pre>\nLet’s discuss the importance of the\u00a0CircleCI<\/strong> config and also look into the run<\/span>\u00a0 steps that we’ve configured.<\/p>\n - run:\r\n name: Create AWS credentials manually\r\n command: |\r\n mkdir ~\/.aws\r\n touch ~\/.aws\/config\r\n chmod 600 ~\/.aws\/config\r\n echo \"[profile eb-cli]\" > ~\/.aws\/config\r\n echo \"aws_access_key_id=$AWS_ACCESS_KEY_ID\" >> ~\/.aws\/config\r\n echo \"aws_secret_access_key=$AWS_SECRET_ACCESS_KEY\" >> ~\/.aws\/config<\/pre>\nIn this step we are manually populate the AWS credentials from the environment variables that CircleCI sets. This is necessary because the AWS EB CLI is not able to use the environment variables directly.\u00a0Instead it needs them to be set in the config file (~\/.aws\/config<\/span>\u00a0).<\/p>\n - run:\r\n name: Deploy to EB if branch is Master\r\n command: |\r\n eb use circleci-beanstalk-example --profile eb-cli\r\n eb deploy -v --staged --profile eb-cli\r\n<\/pre>\nThe above step tells CircleCI\u00a0to use the environment named circleci-beanstalk-example<\/span>\u00a0with the credentials profile named eb-cli<\/span>, which we’ve defined in the config file. You might replace the name of the environment with the one of your application.<\/p>\nAfter we’ve successfully created the\u00a0CircleCI<\/strong> config file, commit the file and push it to your repository.<\/p>\nGo back to the CircleCI Dashboard and you should see your code building and deploying automatically to AWS ElasticBeanstalk.<\/p>\n
Step 1: Setup IAM User<\/strong><\/h2>\nBefore starting to use CircleCI to deploy apps to Beanstalk, we need to generate API credentials that will then be used by CircleCI to execute the necessary commands. In order to generate the API credentials, sign into your\u00a0AWS Management Console<\/strong><\/a>\u00a0and go to \u201cIdentity and Access Management \u2013 IAM<\/strong>\u201d:<\/p>\nThen, click on \u201cAdd user<\/strong>\u201d :<\/p>\n<\/a><\/p>\nAssign a\u00a0username<\/strong>\u00a0for the new account and select \u201cProgrammatic access<\/strong>\u201c:<\/p>\n<\/a><\/p>\nAdd \u201cAmazonElasticBeanstalkFullAccess<\/strong>\u201d to user permissions list, this is whats needed for CircleCI to deploy to Beanstalk.<\/p>\n<\/a><\/p>\nNext, click on \u201cReview<\/strong>\u201d then “Create User”<\/strong>:<\/p>\n<\/a><\/p>\nYou’ll see your Access key ID and your Secret access Key. Both will be used later to trigger the Beanstalk commands from CircleCI.<\/p>\n
Step 2: Add AWS Credentials locally<\/h2>\n
Using the AWS CLI locally we will spin up the Beanstalk environment that will be later used by CircleCI to deploy to. In order to use AWS CLI or EB CLI on your local computer we first need to create a credentials file (~\/.aws\/credentials<\/span>\u00a0) and store the IAM user credentials in it.<\/p>\nEdit\u00a0~\/.aws\/credentials<\/span>\u00a0 and add the following content (replace YOUR_ACCESS_KEY_ID and YOUR_SECRET_ACCESS_KEY with the credentials generated in the previous step):<\/p>\n[eb-cli]\r\naws_access_key_id=YOUR_ACCESS_KEY_ID\r\naws_secret_access_key=YOUR_SECRET_ACCESS_KEY<\/pre>\nStep 3:\u00a0 Install EB CLI<\/h2>\n
In this section, we are going to install\u00a0AWS EB CLI<\/a>.<\/strong><\/p>\nThis step requires Python and pip installed locally. If you have everything ready execute the following command:<\/p>\n
pip install --upgrade --user awsebcli<\/pre>\nAfter you’ve installed the\u00a0EB CLI<\/strong>, add the path to the executable file to your\u00a0PATH<\/strong>\u00a0variable.<\/p>\nStep 4: Create your Elastic Beanstalk environment<\/h2>\n
It’s time to create your Elastic Beanstalk Environment using the EB CLI from your local machine. Just navigate to your app directory (that needs to be deployed to Beanstalk later) and execute eb init<\/span>\u00a0 to initialize the directory as a Beanstalk application. NOTE: Alternatively you also use the AWS Management dashboard to create your Elastic Beanstalk environment.<\/strong><\/p>\nChange into the directory of your app:<\/p>\n
cd ~\/workspace\/my-dummy-app\r\n<\/pre>\nInitialize the app as a Beanstalk application:<\/p>\n
eb init --profile eb-cli\r\n\r\nSelect a default region\r\n1) us-east-1 : US East (N. Virginia)\r\n2) us-west-1 : US West (N. California)\r\n3) us-west-2 : US West (Oregon)\r\n4) eu-west-1 : EU (Ireland)\r\n5) eu-central-1 : EU (Frankfurt)\r\n6) ap-south-1 : Asia Pacific (Mumbai)\r\n7) ap-southeast-1 : Asia Pacific (Singapore)\r\n8) ap-southeast-2 : Asia Pacific (Sydney)\r\n9) ap-northeast-1 : Asia Pacific (Tokyo)\r\n10) ap-northeast-2 : Asia Pacific (Seoul)\r\n11) sa-east-1 : South America (Sao Paulo)\r\n12) cn-north-1 : China (Beijing)\r\n13) cn-northwest-1 : China (Ningxia)\r\n14) us-east-2 : US East (Ohio)\r\n15) ca-central-1 : Canada (Central)\r\n16) eu-west-2 : EU (London)\r\n17) eu-west-3 : EU (Paris)\r\n(default is 3): 5\r\n\r\nSelect an application to use\r\n1) server-backend\r\n2) [ Create new Application ]\r\n(default is 2): 2\r\n\r\nEnter Application Name\r\n(default is \"circleci-beanstalk-example\"):\r\nApplication circleci-beanstalk-example has been created.\r\n\r\nIt appears you are using Node.js. Is this correct?\r\n(Y\/n): Y\r\nNote: Elastic Beanstalk now supports AWS CodeCommit; a fully-managed source control service. To learn more, see Docs: https:\/\/aws.amazon.com\/codecommit\/\r\nDo you wish to continue with CodeCommit? (y\/N) (default is n):\r\nDo you want to set up SSH for your instances?\r\n(Y\/n): n<\/pre>\nThis will initialize your application and the environment, you’ll notice that the command has created a .elasticbeanstalk<\/span>\u00a0 folder in your application. Afterwards we can go ahead and actually spin up the enviroment.<\/p>\nExecute the following command, make sure you use eb-cli<\/span>\u00a0 as the profile, because thats how we named our credentials in the ~\/.aws\/credentials<\/span>\u00a0 file<\/p>\neb create --profile eb-cli\r\nEnter Environment Name\r\n(default is circleci-beanstalk-example-dev):\r\nEnter DNS CNAME prefix\r\n(default is circleci-beanstalk-example-dev):\r\n\r\nSelect a load balancer type\r\n1) classic\r\n2) application\r\n3) network\r\n(default is 1): 2\r\nWARNING: You have uncommitted changes.\r\nCreating application version archive \"app-6207-180303_000424\".\r\nUploading circleci-beanstalk-example\/app-6207-180303_000424.zip to S3. This may take a while.\r\nUpload Complete.\r\nEnvironment details for: circleci-beanstalk-example-dev\r\n Application name: circleci-beanstalk-example\r\n Region: eu-central-1\r\n Deployed Version: app-6207-180303_000424\r\n Environment ID: e-x4dhchqab3\r\n Platform: arn:aws:elasticbeanstalk:eu-central-1::platform\/Node.js running on 64bit Amazon Linux\/4.4.5\r\n Tier: WebServer-Standard-1.0\r\n CNAME: circleci-beanstalk-example-dev.eu-central-1.elasticbeanstalk.com\r\n Updated: 2018-03-02 23:04:27.933000+00:00\r\nPrinting Status:\r\nINFO: createEnvironment is starting.\r\nINFO: Using elasticbeanstalk-eu-central-1-216820535158 as Amazon S3 storage bucket for environment data.\r\nINFO: Created target group named: arn:aws:elasticloadbalancing:eu-central-1:216820535158:targetgroup\/awseb-AWSEB-1ESP9MVJF03WM\/c0c2e625e11502da\r\nINFO: Created security group named: sg-3017c85d\r\nINFO: Created security group named: awseb-e-x4dhchqab3-stack-AWSEBSecurityGroup-389LSAY1654Q\r\nINFO: Created Auto Scaling launch configuration named: awseb-e-x4dhchqab3-stack-AWSEBAutoScalingLaunchConfiguration-1363I5EH0W93A\r\n -- Events -- (safe to Ctrl+C)\r\nINFO: Created Auto Scaling group named: awseb-e-x4dhchqab3-stack-AWSEBAutoScalingGroup-618KCZ091L2D\r\nINFO: Waiting for EC2 instances to launch. This may take a few minutes.\r\nINFO: Created Auto Scaling group policy named: arn:aws:autoscaling:eu-central-1:216820535158:scalingPolicy:968245fa-08a9-434c-ae14-2683532a868b:autoScalingGroupName\/awseb-e-x4dhchqab3-stack-AWSEBAutoScalingGroup-618KCZ091L2D:policyName\/awseb-e-x4dhchqab3-stack-AWSEBAutoScalingScaleDownPolicy-J2G5Z2VU5CU2\r\nINFO: Created Auto Scaling group policy named: arn:aws:autoscaling:eu-central-1:216820535158:scalingPolicy:74b34e27-91b2-4654-ae4a-1adac1f12bd1:autoScalingGroupName\/awseb-e-x4dhchqab3-stack-AWSEBAutoScalingGroup-618KCZ091L2D:policyName\/awseb-e-x4dhchqab3-stack-AWSEBAutoScalingScaleUpPolicy-1084AE1QSLJED\r\nINFO: Created CloudWatch alarm named: awseb-e-x4dhchqab3-stack-AWSEBCloudwatchAlarmLow-1N62LDQ99LOQU\r\nINFO: Created CloudWatch alarm named: awseb-e-x4dhchqab3-stack-AWSEBCloudwatchAlarmHigh-1RKTU1TGKSTPM\r\nINFO: Created load balancer named: arn:aws:elasticloadbalancing:eu-central-1:216820535158:loadbalancer\/app\/awseb-AWSEB-1SMYH0Q88CKQP\/31bb253db6f8c427\r\nINFO: Created Load Balancer listener named: arn:aws:elasticloadbalancing:eu-central-1:216820535158:listener\/app\/awseb-AWSEB-1SMYH0Q88CKQP\/31bb253db6f8c427\/26fbd477342dee44\r\nINFO: Successfully launched environment: circleci-beanstalk-example-devssss<\/pre>\nStep 4: Connect Repo with CircleCI<\/h2>\n
Now that our application environment is up and running (please verify that it actually is using the AWS Management Dashboard), we can go ahead and connect CircleCI to Beanstalk.<\/p>\n
CircleCI needs a repository to pull the code from. Currently CircleCI supports GitHub and BitBucket. Go to\u00a0https:\/\/circleci.com\/signup\/<\/a><\/p>\nand Click on Signup with Github or Bitbucket. You should login into Github and Bitbucket before this.<\/p>\n
<\/a><\/p>\nStep 5:<\/strong> Add IAM user Credentials in CircleCI<\/h2>\nAfter you’ve linked your repository to your CircleCI account, head over to the CircleCI Dashboard<\/a> and navigate into your project. Click on the settings icon of the repository that you want to setup.<\/p>\n<\/a><\/p>\nIn the Settings section scroll down and click on “AWS Permissions” as shown in the screenshot below. Insert your access and secret key of the “circleci” programmatic user that we created previously using the AWS Dashboard.<\/p>\n
<\/a><\/p>\nStep 6: Create CircleCI config<\/strong><\/h2>\nWe are going to use CircleCI version 2.0 <\/strong>because\u00a0<\/strong>CircleCI<\/strong> is officially discontinuing support for\u00a0CircleCI 1.0\u00a0<\/strong>builds after August 31st, 2018.<\/p>\nCreate\u00a0.circleci\/config.yml<\/span>\u00a0\u00a0inside the root directory of your application\u00a0and add it to your repository. CircleCI automatically sets two environment variables ($AWS_ACCESS_KEY_ID<\/span>\u00a0 and $AWS_SECRET_ACCESS_KEY<\/span>\u00a0). We will use those variables to configure the AWS EB CLI.<\/p>\nversion: 2\r\njobs:\r\n deploy:\r\n docker:\r\n - image: circleci\/python:2.7\r\n working_directory: ~\/repo\r\n steps:\r\n - checkout\r\n - run:\r\n name: Install awscli\r\n command: |\r\n sudo pip install awsebcli --upgrade\r\n - run:\r\n name: Create AWS credentials manually\r\n command: |\r\n mkdir ~\/.aws\r\n touch ~\/.aws\/config\r\n chmod 600 ~\/.aws\/config\r\n echo \"[profile eb-cli]\" > ~\/.aws\/config\r\n echo \"aws_access_key_id=$AWS_ACCESS_KEY_ID\" >> ~\/.aws\/config\r\n echo \"aws_secret_access_key=$AWS_SECRET_ACCESS_KEY\" >> ~\/.aws\/config\r\n - run:\r\n name: Deploy to EB if branch is Master\r\n command: |\r\n eb use circleci-beanstalk-example --profile eb-cli\r\n eb deploy -v --staged --profile eb-cli\r\n\r\nworkflows:\r\n version: 2\r\n build-deploy:\r\n jobs:\r\n - deploy:\r\n filters:\r\n branches:\r\n only:\r\n - master\r\n - develop<\/pre>\nLet’s discuss the importance of the\u00a0CircleCI<\/strong> config and also look into the run<\/span>\u00a0 steps that we’ve configured.<\/p>\n - run:\r\n name: Create AWS credentials manually\r\n command: |\r\n mkdir ~\/.aws\r\n touch ~\/.aws\/config\r\n chmod 600 ~\/.aws\/config\r\n echo \"[profile eb-cli]\" > ~\/.aws\/config\r\n echo \"aws_access_key_id=$AWS_ACCESS_KEY_ID\" >> ~\/.aws\/config\r\n echo \"aws_secret_access_key=$AWS_SECRET_ACCESS_KEY\" >> ~\/.aws\/config<\/pre>\nIn this step we are manually populate the AWS credentials from the environment variables that CircleCI sets. This is necessary because the AWS EB CLI is not able to use the environment variables directly.\u00a0Instead it needs them to be set in the config file (~\/.aws\/config<\/span>\u00a0).<\/p>\n - run:\r\n name: Deploy to EB if branch is Master\r\n command: |\r\n eb use circleci-beanstalk-example --profile eb-cli\r\n eb deploy -v --staged --profile eb-cli\r\n<\/pre>\nThe above step tells CircleCI\u00a0to use the environment named circleci-beanstalk-example<\/span>\u00a0with the credentials profile named eb-cli<\/span>, which we’ve defined in the config file. You might replace the name of the environment with the one of your application.<\/p>\nAfter we’ve successfully created the\u00a0CircleCI<\/strong> config file, commit the file and push it to your repository.<\/p>\nGo back to the CircleCI Dashboard and you should see your code building and deploying automatically to AWS ElasticBeanstalk.<\/p>\n
Then, click on \u201cAdd user<\/strong>\u201d :<\/p>\n Assign a\u00a0username<\/strong>\u00a0for the new account and select \u201cProgrammatic access<\/strong>\u201c:<\/p>\n Add \u201cAmazonElasticBeanstalkFullAccess<\/strong>\u201d to user permissions list, this is whats needed for CircleCI to deploy to Beanstalk.<\/p>\n Next, click on \u201cReview<\/strong>\u201d then “Create User”<\/strong>:<\/p>\n You’ll see your Access key ID and your Secret access Key. Both will be used later to trigger the Beanstalk commands from CircleCI.<\/p>\n Using the AWS CLI locally we will spin up the Beanstalk environment that will be later used by CircleCI to deploy to. In order to use AWS CLI or EB CLI on your local computer we first need to create a credentials file (~\/.aws\/credentials<\/span>\u00a0) and store the IAM user credentials in it.<\/p>\n Edit\u00a0~\/.aws\/credentials<\/span>\u00a0 and add the following content (replace YOUR_ACCESS_KEY_ID and YOUR_SECRET_ACCESS_KEY with the credentials generated in the previous step):<\/p>\n In this section, we are going to install\u00a0AWS EB CLI<\/a>.<\/strong><\/p>\n This step requires Python and pip installed locally. If you have everything ready execute the following command:<\/p>\n After you’ve installed the\u00a0EB CLI<\/strong>, add the path to the executable file to your\u00a0PATH<\/strong>\u00a0variable.<\/p>\n It’s time to create your Elastic Beanstalk Environment using the EB CLI from your local machine. Just navigate to your app directory (that needs to be deployed to Beanstalk later) and execute eb init<\/span>\u00a0 to initialize the directory as a Beanstalk application. NOTE: Alternatively you also use the AWS Management dashboard to create your Elastic Beanstalk environment.<\/strong><\/p>\n Change into the directory of your app:<\/p>\n Initialize the app as a Beanstalk application:<\/p>\n This will initialize your application and the environment, you’ll notice that the command has created a .elasticbeanstalk<\/span>\u00a0 folder in your application. Afterwards we can go ahead and actually spin up the enviroment.<\/p>\n Execute the following command, make sure you use eb-cli<\/span>\u00a0 as the profile, because thats how we named our credentials in the ~\/.aws\/credentials<\/span>\u00a0 file<\/p>\n Now that our application environment is up and running (please verify that it actually is using the AWS Management Dashboard), we can go ahead and connect CircleCI to Beanstalk.<\/p>\n CircleCI needs a repository to pull the code from. Currently CircleCI supports GitHub and BitBucket. Go to\u00a0https:\/\/circleci.com\/signup\/<\/a><\/p>\n and Click on Signup with Github or Bitbucket. You should login into Github and Bitbucket before this.<\/p>\n After you’ve linked your repository to your CircleCI account, head over to the CircleCI Dashboard<\/a> and navigate into your project. Click on the settings icon of the repository that you want to setup.<\/p>\n In the Settings section scroll down and click on “AWS Permissions” as shown in the screenshot below. Insert your access and secret key of the “circleci” programmatic user that we created previously using the AWS Dashboard.<\/p>\n We are going to use CircleCI version 2.0 <\/strong>because\u00a0<\/strong>CircleCI<\/strong> is officially discontinuing support for\u00a0CircleCI 1.0\u00a0<\/strong>builds after August 31st, 2018.<\/p>\n Create\u00a0.circleci\/config.yml<\/span>\u00a0\u00a0inside the root directory of your application\u00a0and add it to your repository. CircleCI automatically sets two environment variables ($AWS_ACCESS_KEY_ID<\/span>\u00a0 and $AWS_SECRET_ACCESS_KEY<\/span>\u00a0). We will use those variables to configure the AWS EB CLI.<\/p>\n Let’s discuss the importance of the\u00a0CircleCI<\/strong> config and also look into the run<\/span>\u00a0 steps that we’ve configured.<\/p>\n In this step we are manually populate the AWS credentials from the environment variables that CircleCI sets. This is necessary because the AWS EB CLI is not able to use the environment variables directly.\u00a0Instead it needs them to be set in the config file (~\/.aws\/config<\/span>\u00a0).<\/p>\n The above step tells CircleCI\u00a0to use the environment named circleci-beanstalk-example<\/span>\u00a0with the credentials profile named eb-cli<\/span>, which we’ve defined in the config file. You might replace the name of the environment with the one of your application.<\/p>\n After we’ve successfully created the\u00a0CircleCI<\/strong> config file, commit the file and push it to your repository.<\/p>\n Go back to the CircleCI Dashboard and you should see your code building and deploying automatically to AWS ElasticBeanstalk.<\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nStep 2: Add AWS Credentials locally<\/h2>\n
[eb-cli]\r\naws_access_key_id=YOUR_ACCESS_KEY_ID\r\naws_secret_access_key=YOUR_SECRET_ACCESS_KEY<\/pre>\n
Step 3:\u00a0 Install EB CLI<\/h2>\n
pip install --upgrade --user awsebcli<\/pre>\n
Step 4: Create your Elastic Beanstalk environment<\/h2>\n
cd ~\/workspace\/my-dummy-app\r\n<\/pre>\n
eb init --profile eb-cli\r\n\r\nSelect a default region\r\n1) us-east-1 : US East (N. Virginia)\r\n2) us-west-1 : US West (N. California)\r\n3) us-west-2 : US West (Oregon)\r\n4) eu-west-1 : EU (Ireland)\r\n5) eu-central-1 : EU (Frankfurt)\r\n6) ap-south-1 : Asia Pacific (Mumbai)\r\n7) ap-southeast-1 : Asia Pacific (Singapore)\r\n8) ap-southeast-2 : Asia Pacific (Sydney)\r\n9) ap-northeast-1 : Asia Pacific (Tokyo)\r\n10) ap-northeast-2 : Asia Pacific (Seoul)\r\n11) sa-east-1 : South America (Sao Paulo)\r\n12) cn-north-1 : China (Beijing)\r\n13) cn-northwest-1 : China (Ningxia)\r\n14) us-east-2 : US East (Ohio)\r\n15) ca-central-1 : Canada (Central)\r\n16) eu-west-2 : EU (London)\r\n17) eu-west-3 : EU (Paris)\r\n(default is 3): 5\r\n\r\nSelect an application to use\r\n1) server-backend\r\n2) [ Create new Application ]\r\n(default is 2): 2\r\n\r\nEnter Application Name\r\n(default is \"circleci-beanstalk-example\"):\r\nApplication circleci-beanstalk-example has been created.\r\n\r\nIt appears you are using Node.js. Is this correct?\r\n(Y\/n): Y\r\nNote: Elastic Beanstalk now supports AWS CodeCommit; a fully-managed source control service. To learn more, see Docs: https:\/\/aws.amazon.com\/codecommit\/\r\nDo you wish to continue with CodeCommit? (y\/N) (default is n):\r\nDo you want to set up SSH for your instances?\r\n(Y\/n): n<\/pre>\n
eb create --profile eb-cli\r\nEnter Environment Name\r\n(default is circleci-beanstalk-example-dev):\r\nEnter DNS CNAME prefix\r\n(default is circleci-beanstalk-example-dev):\r\n\r\nSelect a load balancer type\r\n1) classic\r\n2) application\r\n3) network\r\n(default is 1): 2\r\nWARNING: You have uncommitted changes.\r\nCreating application version archive \"app-6207-180303_000424\".\r\nUploading circleci-beanstalk-example\/app-6207-180303_000424.zip to S3. This may take a while.\r\nUpload Complete.\r\nEnvironment details for: circleci-beanstalk-example-dev\r\n Application name: circleci-beanstalk-example\r\n Region: eu-central-1\r\n Deployed Version: app-6207-180303_000424\r\n Environment ID: e-x4dhchqab3\r\n Platform: arn:aws:elasticbeanstalk:eu-central-1::platform\/Node.js running on 64bit Amazon Linux\/4.4.5\r\n Tier: WebServer-Standard-1.0\r\n CNAME: circleci-beanstalk-example-dev.eu-central-1.elasticbeanstalk.com\r\n Updated: 2018-03-02 23:04:27.933000+00:00\r\nPrinting Status:\r\nINFO: createEnvironment is starting.\r\nINFO: Using elasticbeanstalk-eu-central-1-216820535158 as Amazon S3 storage bucket for environment data.\r\nINFO: Created target group named: arn:aws:elasticloadbalancing:eu-central-1:216820535158:targetgroup\/awseb-AWSEB-1ESP9MVJF03WM\/c0c2e625e11502da\r\nINFO: Created security group named: sg-3017c85d\r\nINFO: Created security group named: awseb-e-x4dhchqab3-stack-AWSEBSecurityGroup-389LSAY1654Q\r\nINFO: Created Auto Scaling launch configuration named: awseb-e-x4dhchqab3-stack-AWSEBAutoScalingLaunchConfiguration-1363I5EH0W93A\r\n -- Events -- (safe to Ctrl+C)\r\nINFO: Created Auto Scaling group named: awseb-e-x4dhchqab3-stack-AWSEBAutoScalingGroup-618KCZ091L2D\r\nINFO: Waiting for EC2 instances to launch. This may take a few minutes.\r\nINFO: Created Auto Scaling group policy named: arn:aws:autoscaling:eu-central-1:216820535158:scalingPolicy:968245fa-08a9-434c-ae14-2683532a868b:autoScalingGroupName\/awseb-e-x4dhchqab3-stack-AWSEBAutoScalingGroup-618KCZ091L2D:policyName\/awseb-e-x4dhchqab3-stack-AWSEBAutoScalingScaleDownPolicy-J2G5Z2VU5CU2\r\nINFO: Created Auto Scaling group policy named: arn:aws:autoscaling:eu-central-1:216820535158:scalingPolicy:74b34e27-91b2-4654-ae4a-1adac1f12bd1:autoScalingGroupName\/awseb-e-x4dhchqab3-stack-AWSEBAutoScalingGroup-618KCZ091L2D:policyName\/awseb-e-x4dhchqab3-stack-AWSEBAutoScalingScaleUpPolicy-1084AE1QSLJED\r\nINFO: Created CloudWatch alarm named: awseb-e-x4dhchqab3-stack-AWSEBCloudwatchAlarmLow-1N62LDQ99LOQU\r\nINFO: Created CloudWatch alarm named: awseb-e-x4dhchqab3-stack-AWSEBCloudwatchAlarmHigh-1RKTU1TGKSTPM\r\nINFO: Created load balancer named: arn:aws:elasticloadbalancing:eu-central-1:216820535158:loadbalancer\/app\/awseb-AWSEB-1SMYH0Q88CKQP\/31bb253db6f8c427\r\nINFO: Created Load Balancer listener named: arn:aws:elasticloadbalancing:eu-central-1:216820535158:listener\/app\/awseb-AWSEB-1SMYH0Q88CKQP\/31bb253db6f8c427\/26fbd477342dee44\r\nINFO: Successfully launched environment: circleci-beanstalk-example-devssss<\/pre>\n
Step 4: Connect Repo with CircleCI<\/h2>\n
<\/a><\/p>\nStep 5:<\/strong> Add IAM user Credentials in CircleCI<\/h2>\n
<\/a><\/p>\n<\/a><\/p>\nStep 6: Create CircleCI config<\/strong><\/h2>\n
version: 2\r\njobs:\r\n deploy:\r\n docker:\r\n - image: circleci\/python:2.7\r\n working_directory: ~\/repo\r\n steps:\r\n - checkout\r\n - run:\r\n name: Install awscli\r\n command: |\r\n sudo pip install awsebcli --upgrade\r\n - run:\r\n name: Create AWS credentials manually\r\n command: |\r\n mkdir ~\/.aws\r\n touch ~\/.aws\/config\r\n chmod 600 ~\/.aws\/config\r\n echo \"[profile eb-cli]\" > ~\/.aws\/config\r\n echo \"aws_access_key_id=$AWS_ACCESS_KEY_ID\" >> ~\/.aws\/config\r\n echo \"aws_secret_access_key=$AWS_SECRET_ACCESS_KEY\" >> ~\/.aws\/config\r\n - run:\r\n name: Deploy to EB if branch is Master\r\n command: |\r\n eb use circleci-beanstalk-example --profile eb-cli\r\n eb deploy -v --staged --profile eb-cli\r\n\r\nworkflows:\r\n version: 2\r\n build-deploy:\r\n jobs:\r\n - deploy:\r\n filters:\r\n branches:\r\n only:\r\n - master\r\n - develop<\/pre>\n
- run:\r\n name: Create AWS credentials manually\r\n command: |\r\n mkdir ~\/.aws\r\n touch ~\/.aws\/config\r\n chmod 600 ~\/.aws\/config\r\n echo \"[profile eb-cli]\" > ~\/.aws\/config\r\n echo \"aws_access_key_id=$AWS_ACCESS_KEY_ID\" >> ~\/.aws\/config\r\n echo \"aws_secret_access_key=$AWS_SECRET_ACCESS_KEY\" >> ~\/.aws\/config<\/pre>\n
- run:\r\n name: Deploy to EB if branch is Master\r\n command: |\r\n eb use circleci-beanstalk-example --profile eb-cli\r\n eb deploy -v --staged --profile eb-cli\r\n<\/pre>\n
![\"circleci](\"https:\/\/kevingoedecke.com\/blog\/wp-content\/uploads\/2018\/03\/CircleCI-build-1024x498.png\")
<\/a><\/p>\n![\"circleci](\"https:\/\/kevingoedecke.com\/blog\/wp-content\/uploads\/2018\/03\/Screen-Shot-2018-03-09-at-12.34.09-1024x582.png\")
<\/a><\/p>\n