1 Answer
- Newest
- Most votes
- Most comments
0
Hi,
There's nothing specific with containers you run on Fargate.
At a high-level, as long as you have a container you can just create a task definition (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/create-task-definition.html), specifying the FARGATE launch type and then either use the run-task API to start the task or create-service to create a service that runs one or more copies of the task. Based on your question, the run-task API is probably what you want to use.
Should you choose to stop using Fargate, you can keep the container and just run it on an EC2 instance instead.
There are a few caveats you should keep in mind:
- If you treat the containerized server as a stateful container (i.e. you are storing state in the container itself) you will need to change this to store state elsewhere otherwise you will lose the state when you stop the task (the same is true even if you run the container on an EC2 instance unless you take explicit steps to store the state outside of the container).
- Fargate gives you 10 Gb of Docker layer storage and 4 Gb for volume mounts. If your container image is larger than 10 Gb you won't be able to run it on Fargate (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/fargate-task-storage.html)
answered 4 years ago
Relevant content
- asked 2 years ago
- asked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago