Amazon ECS-Optimized Amazon Linux AMI
Amazon Web Services | 2016.09.fLinux/Unix, Amazon Linux AMI 2016.03 - 64-bit Amazon Machine Image (AMI)
instance-store AMI should be provided as well
Paying for EBS root device is not good if you want to run several ECS instances. If we had an instance-store version of ECS optimized we would be able to benefit from running this with EC2 Spot Fleet and using much more disk space (ephemeral0).
- Leave a Comment |
- Mark review as helpful
This service still has a beta feel to it
Not fact that deleting(cleaning up) task definitions isn't even supported yet says it all. Strange behavior from time to time, and following the instructions on how to get the agent to pull from my private registry did not net the results I wanted. It's not all bad, however, I expected a more consistent experience for something out of beta.
Definitely a good start
This is definitely a hugely desired feature for us and we are so happy that AWS did it. The potential to scale at a micro level seems to be awesome. We can go from one micro server with multiple segmented technologies in it and yet quick add little by little to the system, growing only what needs to be grown. My two biggest complaints:
1. Containers would crash/shutdown/etc with no indication of what happened (nothing in the event log or any other log that I could find). I believe it may have been a lack of resources but again I have no clue.
2. There is no registry built into AWS. I don't need the automatic build of Docker Hub and the prices are ridiculous, so I was really hoping for AWS to release an S3 backed docker registry. Charge us for the storage and a small amount for the service availability, but that shouldn't be anything near what Docker Hub charges. Plus it being directly built into AWS would allow them to create better integration in ECS.