ECS Agent Multi-Region Resiliency about amazon-ecs-init HOT 8 CLOSED

facing the same issue

from amazon-ecs-init.

👍

from amazon-ecs-init.

+1

from amazon-ecs-init.

I guess more specifically, it looks like if we add more regions here:

from amazon-ecs-init.

Also facing the same issue.

from amazon-ecs-init.

Thank you all for reporting this, originally the ecs-agent was only stored in us-east-1, and it was replicated to cn-north-1 when we support the BJS region. Since then I think it is reasonable to replicate the ecs-agent to all the regions to support the use case above, beyond that we also need to make some change to the ecs-init to support downloading from specified region. I'll mark this as a feature request, please keep tracking this for updates.

Thanks,
Peng

from amazon-ecs-init.

@richardpen you already have support for this you just need to upload to additional buckets and update these lines of code:

This is pretty important for high-availability especially with the 2 major recent AWS s3 outages in us-east-1 any way you can prioritize it, shouldn't take a lot of time?

from amazon-ecs-init.

Regional buckets are now used by amazon-ecs-init with #170. It is worth noting that the downloader's behavior is to attempt a download from the bucket in us-east-1 first and then fail over to the instance's region's bucket (eg: an instance in us-west-2 will attempt download from a bucket in us-east-1 and then us-west-2).

Please feel free to reopen and comment if and why this doesn't satisfy your environment's needs so that we can drive the appropriate change.

Thanks for the input folks!

from amazon-ecs-init.