Can I use AWS code Deploy for pulling application code while autoscaling?

I want to autoscale the infrastructure when load gets high. I am running my infrastructure on AWS. I have a requirement where I need to pull the application code from Github when autoscaling happens. As the code changes frequently, we can’t take an AMI and launch an instance from that AMI. So I want to pull the latest code from repositories. AWS just launched a service called AWS CodeDeploy. How can I use this service to automate the process of pulling the code when the instances start?

P.S. I have written an init script to automatically attach an EIP, whitelist that IP on different Security Groups and put the instance under a load-balancer when the instance boots and revoking everything when instance is terminated in autoscaling.

  • cannot connect to my repository in AWS Code commit
  • Git GUI for AWS CodeCommit
  • eb deploy --staged usage
  • aws.push to more than one environment
  • Develping with Django, Git, and Cloud Server
  • Error on first git aws.push to elastic beanstalk
  • What is the different between Parse-server and Parse-server-example on ParsePlatform on GitHub?
  • Can I use CodeStar's deployment infrastructure with an existing CodeCommit repo?
  • aws codecommit cannot push
  • Problems migrating git repository server without access to original
  • Specific git branches for aws elastic beanstalk environments
  • Hosting a Git repository on an AWS Windows Server
  • One Solution collect form web for “Can I use AWS code Deploy for pulling application code while autoscaling?”

    CodeDeploy is a great solution to your problem. If configured correctly, it can automatically deploy to new EC2 instances that are spun up by Autoscaling. To get this working you’ll need three things:

    1. An Auto Scaling group that launches instances with the latest host agent installed and running.
    2. A Code Deploy deployment group configured to deploy to that Auto Scaling group (as a Auto Scaling group not by tags).
    3. A target revision to deploy automatically to new instances. If there is no target revision, Code Deploy will see the instance launch, but won’t deploy anything.

    Here’s a tutorial you can use to help get started: Tutorial: Using AWS CodeDeploy to Deploy an Application to an Auto Scaling Group. That tutorial will walk you through baking an AMI with the agent installed and setting up the deployment group to deploy your code to new instances.

    If you do bake a AMI with the agent pre-installed, you would need to update that image regularly with agent releases. Once the agent is installed it will update itself, but Auto Scaling might fail your instance launches if the agent version is no longer supported by Code Deploy. For actual production use, I would recommend not baking an AMI and instead installing the latest agent when your instances are launched. (The tutorial should be updated to use this method soon.)

    You can setup your instances to automatically download and run the latest installer on boot. Essentially, you paste in a shell script as user data when creating the Auto Scaling group.

    For example, I tested the following script on Amazon Linux (taken from Set Up a New Amazon EC2 Instance to Work with AWS CodeDeploy):

    yum -y update
    yum install -y aws-cli
    cd /home/ec2-user
    aws s3 cp s3://aws-codedeploy-us-east-1/latest/install . --region us-east-1
    chmod +x ./install
    ./install auto

    You should be able to paste this in as user data when you are creating the Auto Scaling group. For Auto Scaling, you set that up when creating the launch configuration under configure details -> advanced details.

    To set up the deployment group and set the target revision:

    1. Create or edit a deployment group to include the Auto Scaling group. (Note: the Auto Scaling group must exist first for this to work.)
    2. Make sure there is at least 1 instance in the Auto Scaling group.
    3. Deploy the artifact bundle you want to be automatically deployed to the deployment group.
    4. Assuming step 3 was successful, the deployment group will now have that bundle set as it’s target revision. For automatic deployments, this becomes the known good revision to deploy.

    New instances that are launched by Auto Scaling in that Auto Scaling group will have the target revision of the deployment group automatically deployed to them. Revisions from failed manual deployments won’t be automatically deployed automatically.

    Git Baby is a git and github fan, let's start git clone.