How can I connect my autoscaling group to my ecs cluster?

Question

In all tutorials for ECS you need to create a cluster and after that an autoscaling group, that will spawn instances. Somehow in all these tutorials the instances magically show up in the cluster, but noone gives a hint what's connecting the autoscaling group and the cluster.

my autoscaling group spawns instances as expected, but they just dont show up on my ecs cluster, who holds my docker definitions.

Where is the connection I'm missing?

Solution 1

Well, i found out. Its all about the ecs-agent and its config file /etc/ecs/ecs.config (This file will be created through the Userdata field, when creating EC2 instances, even from an autoscaling configuration.) Read about its configuration options here: http://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html

But you can even copy a ecs.config stored on Amazon S3, do it like this (following lines go into Userdata field):

#!/bin/bash
yum install -y aws-cli
aws configure set default.s3.signature_version s3v4
aws configure set default.s3.addressing_style path
aws configure set default.region eu-central-1
aws s3 cp s3://<bucketname>/ecs.config /etc/ecs/ecs.config

note: Signature_version v4 is specific for some regions, like eu-central-1. This ofc only works, if your IAM role for the instance (in my case its ecsInstanceRole) has the right AmazonS3ReadOnlyAccess

---

The AWS GUI console way for that would be: Use the cluster wizard at https://console.aws.amazon.com/ecs/home#/firstRun . It will create an autoscaling grou for your cluster, a loadbalancer in front of it, and connect it all nicely.

Solution 2

I was struggling with this for a while. The key to getting the instances in the autoscaling group associated with your ECS cluster is in the user data. When you are creating your launch config when you get to step 3 "Configure Details" hit the advanced tab and enter a simple bash script like the following for your user data.

#!/usr/bin/env bash
echo ECS_CLUSTER=your_cluster_name >> /etc/ecs/ecs.config

All the available parameters for agent configuration can be found here http://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html

Solution 3

An autoscaling group is not strictly associated to a cluster. However, an autoscaling group can be configured such that each instance launched registers itself into a particular cluster.

Registering an instance into a cluster is the responsibility of the ECS Agent running on the instance. If you're using the Amazon ECS-optimized AMI, the ECS Agent will launch when the instance boots and register itself into the configured cluster. However, you can also use the ECS Agent on other Linux AMIs by following the installation instructions.

Comments

[cari]

yes, i already got to that point. but thanks for adding this here. you can even load the ecs.config from amazon S3. Im adding that to my answer.

[RoberMP]

To complete a bit more the response, this is the command needed to re(start) the agent: sudo start ecs. Use it after configure the agent.

[Andy]

Thanks, this answer helped me to realize that my issue wasn't a lack of association, but that my ASG launch configs were creating ec2 instances with no public IP, which was preventing the ECS agent from registering the instances.

[Sarang]

This is actually the right answer. ECS_CLUSTER in /etc/ecs/ecs.config needs to have the correct name. That's all!