1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
1
Putting JSON in the command might be tricky via the UI. When you use docker-compose, given it's in YAML, it is much easier to write that up.
To go from docker-compose to ECS, I would recommend to try out ECS Compose-X which will translate your docker-compose files into CFN templates. If anything, you might be able to generate the JSON/YAML template that will contain your task and containers definition which will quote / escape your JSON argument accordingly. Might help you get on the right track.
As an alternative, something I have done in multiple places, you can set a complex string value as an environment variable and use that in the command.
Hope this helps,
beantwortet vor 2 Jahren
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 10 Monaten- AWS OFFICIALAktualisiert vor 2 Jahren
So basically what we want is to have task definition and the make changes to it depending on situation , we want to move away from the cli and spin up multiple containers with different ports form the task definition which we will be able to control through lambda . In our use case we don't want have to access cli options.