-
Notifications
You must be signed in to change notification settings - Fork 15
aws ecs - how to update a task definition #406
Comments
Hmm, I'm not sure. In general, the best place for usage related questions would be on stack overflow, as mentioned in our README. Looking over the docs though, it seems like just using
I would give that a shot first. |
thanks, sorry for the noise. I was expecting it to be a separate command consistent with others like |
Hello @extrawurst I have the same issue. I was wondering if you found a solution. |
After flattening the top-level dictionary:
|
I think this should be reopened as a feature request. Currently, CLI for ECS Task update, required for CI/CD, is not straight forward and requires additional tricks. Flow most commonly found on the web is to call Using Fargate I came across a problem with this flow - task couldn't be updated with the same JSON, it required additional parameters, and I basically had to put all top-level values from So the better solution for me was to use JSON as full input for the task, but it has it own problems mentioned by @shatil. Finally I ended with script like this: TASK_DEFINITION=$(aws ecs describe-task-definition --task-definition "$TASK_FAMILY" --region "us-east-1")
NEW_TASK_DEFINTIION=$(echo $TASK_DEFINITION | jq --arg IMAGE "$NEW_IMAGE" '.taskDefinition | .containerDefinitions[0].image = $IMAGE | del(.taskDefinitionArn) | del(.revision) | del(.status) | del(.requiresAttributes) | del(.compatibilities)')
aws ecs register-task-definition --region "us-east-1" --cli-input-json "$NEW_TASK_DEFINTIION" |
Thanks @m-radzikowski I slightly modified your solution so it also works when using git hash as image tag instead of "latest". Needs some some environmental variables to work though
|
What's the status on this? how can we create a task definition revision? I would think there would be something like: aws ecs update-task-definition --task-definition "$task_fam" --revision "ecr/name:tag" so yes I am looking for: aws ecs update-task-definition I checked using I created this ticket: aws/aws-cli#4401 |
aws-cli support, if you don't like us to discuss just don't use github, sorry, this is still valid and should be reopened |
You might not need aws describe-task-definition --task-definition myapp \
--query 'taskDefinition.{containerDefinitions:containerDefinitions}' \
> /tmp/task-definitions.json Fargate users might need long commands like this: aws ecs register-task-definition \
--family myapp \
--cli-input-json file:///tmp/task.json \
--requires-compatibilities FARGATE \
--network-mode awsvpc \
--cpu 1024 --memory 2048 \
--task-role-arn <arn> --execution-role-arn <arn> |
As a fargate user, I've found a hack using for ecs cli and --tags. Whatever you put in to the version number, it'll set the revision as the next one.
|
I've switched to Fargate CLI. It automatically updates a suitable task definition. |
Thanks for sharing that - hadn't seen it. Look forward to checking it out. |
fargatecli does not work if you have volumes defined |
Here is a full version that does not require JQ:
|
Adding to @sashokbg's answer, register-task-definition is complaining that it needs strings for the cpu and memory values. The --query command uses JMESPath syntax, which supports to_string($arg) type casting, so just wrap those two in to_string() |
If you just want to update your ECS cluster to use the latest image (tag with "latest"), this should be enough:
The |
@oalagtash Thanks for the info. I'll try it. |
What if I don't want to use the latest tag, and my task definitions contain secrets? I have figured out, thanks to this thread, how to generate a new task definition revision, but it always strips out my secrets. Is there a simple way to just create an exact replica of the task def but with updated image tag? |
@alto9 For secret, you should store it to S3 (with proper policy) and get it when you start a container. It's more flexible. |
Or autoscaling |
@alto9 Have you looked into SSM parameter store? You can link those ARNs inside the fargate task definition. |
@RamiAwar that's actually what I was doing. the problem is the secrets are literally stripped out of the task definition while it gets created and I don't get why. |
@alto9 That's weird. I just set it up for the first time and it works out of the box. I made 100% sure that the environment variables were read from SSM and passed to the container. One thing that you notice is that environment is different from secrets. Secrets is where I add the SSM params. This is the task definition that I'm using, along with the commands I use to update it:
|
If you are that bizarre person who wants to use a single one-liner to update the task definition, with no intermediate files, here you go..... CLUSTER="my-cluster"
SERVICE="my-service-name"
aws ecs describe-services \
--cluster "$CLUSTER" \
--services "$SERVICE" \
--query 'services[].taskDefinition[]' \
--output text \
| xargs -n1 \
aws ecs describe-task-definition \
--query 'taskDefinition.taskDefinitionArn' \
--output text \
--task-definition \
| xargs -n1 \
aws ecs describe-task-definition \
--query '{
containerDefinitions: taskDefinition.containerDefinitions,
family: taskDefinition.family,
taskRoleArn: taskDefinition.taskRoleArn,
executionRoleArn: taskDefinition.executionRoleArn,
networkMode: taskDefinition.networkMode,
volumes: taskDefinition.volumes,
placementConstraints: taskDefinition.placementConstraints,
requiresCompatibilities: taskDefinition.requiresCompatibilities,
cpu: taskDefinition.cpu,
memory: taskDefinition.memory
}' \
--task-definition \
| xargs -0 \
aws ecs register-task-definition \
--cli-input-json \
| cat |
Thanks to @sashokbg 's comment, my deploy script become like this: .
|-- bin
| `-- update-fargate-service.sh
`-- my-api
`-- Dockerfile
#!/bin/bash
docker build -t $ECR_URI $SOURCE
aws ecr get-login-password | docker login --username AWS --password-stdin $ECR_URI
docker push $ECR_URI
# @see https://github.com/aws/aws-sdk/issues/406
NEW_TASK_DEFINTION=$(aws ecs describe-task-definition --task-definition $NAME \
--query '{ containerDefinitions: taskDefinition.containerDefinitions,
family: taskDefinition.family,
taskRoleArn: taskDefinition.taskRoleArn,
executionRoleArn: taskDefinition.executionRoleArn,
networkMode: taskDefinition.networkMode,
volumes: taskDefinition.volumes,
placementConstraints: taskDefinition.placementConstraints,
requiresCompatibilities: taskDefinition.requiresCompatibilities,
cpu: taskDefinition.cpu,
memory: taskDefinition.memory}')
aws ecs register-task-definition --family $NAME --cli-input-json "$NEW_TASK_DEFINTION"
aws ecs update-service --cluster $NAME --service $NAME --task-definition $NAME And run $ env \
ECR_URI=<account_id>.dkr.ecr.us-west-1.amazonaws.com/my-api \ # ECR URL
NAME=my-api \
SOURCE=my-api \
bin/update-fargate-service.sh Hope this helps someone |
This is buried in the documentation for
|
Are there any updates from the ECS team on these issues? Would it be possible to just expose an interface that would just create a new task def from the current task def and just update the image?
It seems like that functionality is already in place. When you click "Create new revision" it creates a new revision with a copy of the current. Just allow us to update the image and that would make so many of us happy!! |
* sam pipeline bootstrap (aws#2811) * two-stages-pipeline plugin * typos * add docstring * make mypy happy * removing swap file * delete the two_stages_pipeline plugin as the pipeline-bootstrap command took over its responsibility * remove 'get_template_function_runtimes' function as the decision is made to not process the SAM template during pipeline init which was the only place we use the function * sam pipeline bootstrap command * move the pipelineconfig.toml file to .aws-sam * UX - rewriting Co-authored-by: Chris Rehn <[email protected]> * UX improvements * make black happy * apply review comments * UX - rewriting Co-authored-by: Chris Rehn <[email protected]> * refactor * Apply review comments * use python way of array elements assignments * Update samcli/lib/pipeline/bootstrap/stage.py Co-authored-by: _sam <[email protected]> * apply review comments * typo * read using utf-8 * create and user a safe version of the save_config method * apply review comments * rename _get_command_name to _get_command_names * don't save generated ARNs for now, will save during init * Revert "don't save generated ARNs for now, will save during init" This reverts commit d184e164022d9560131c62a826436edbc93da189. * Notify the user to rotate periodically rotate the IAM credentials * typo * Use AES instead of KMS for S3 SSE * rename Ecr to ECR and Iam to IAM * Grant lambda service explicit permissions to thhe ECR instead of relying on giving this permissions on ad-hoc while creating the container images Co-authored-by: Chris Rehn <[email protected]> Co-authored-by: _sam <[email protected]> * sam pipeline init command (aws#2831) * sam pipeline init command * apply review comments * apply review comments * display a message that we have successfully created the pipeline configuration file(s). * doc typo * Let 'sam pipeline init' prefills pipeline's infrastructure resources… (aws#2894) * Let 'sam pipeline init' prefills pipeline's infrastructure resources' values from 'sam pipeline bootstrap' results. * save bootstrapped sateg region * make black happy * exclude non-dict keys from samconfig.get_env_names method. * Rename the pipeline 'Stage' concept to 'Environment' (aws#2908) * Rename the pipeline 'Stage' concept to 'Environment' * typo * Rename --environment-name argument to --environment * Sam pipelines ux rename ecr repo to image repository (aws#2910) * Rename ecr-repo to image-repository * UT Fixes * typo * typo * feat: Support creating pipeline files directly into . without hooks (aws#2911) * feat: Support creating pipeline files directly into . without hooks * Integration test for pipeline init and pipeline bootstrap (aws#2841) * Expose Environment._get_stack_name for integ test to predict stack name * Add integ test for pipeline bootstrap * Add init integ test * small UX improvements: (aws#2914) * small UX improvements: 1. show a message when the user cancels a bootstrapping command. 2. Don't prompt for CI/CD provider or provider templates if there is only one choice. 3. Make PipelineFileAlreadyExistsError a UserError. 4. use the Colored class instead of fg='color' when prompting a colored message. 5. Fix a bug where we were not allowing empty response for not required questions. * Fix Integration Test: We now don't ask the user to select a provider's pipeline template if there is only one * Add docs for PipelineFileAlreadyExistsError * make black happy * Sam pipelines s3 security (aws#2975) * Deny non https requests for the artifacts S3 bucket * enable bucket serverside logging * add integration tests for artifacts bucket SSL-only requests and access logging * typo * Ensure the ArtifactsLoggingBucket denies non ssl requests (aws#2976) * Sam pipelines ux round 3 (aws#2979) * rename customer facing message 'CI/CD provider' to 'CI/CD system' * add a note about what 'Environment Name' is during the pipeline bootstrap guided context * Apply suggestions from code review typo Co-authored-by: Chris Rehn <[email protected]> Co-authored-by: Chris Rehn <[email protected]> * let pipeline IAM user assume only IAM roles tagged with Role=pipeline-execution-role (aws#2982) * Adding AWS_ prefix to displayed out. (aws#2993) Co-authored-by: Tarun Mall <[email protected]> * Add region to pipeline bootstrap interactive flow (aws#2997) * Ask AWS region in bootstrap interactive flow * Read default region from boto session first * Fix a unit test * Inform write to pipelineconfig.toml at the end of bootstrap (aws#3002) * Print info about pipelineconfig.toml after resources are bootstrapped * Update samcli/commands/pipeline/bootstrap/cli.py Co-authored-by: Chris Rehn <[email protected]> Co-authored-by: Chris Rehn <[email protected]> * List detected env names in pipeline init when prompt to input the env name (aws#3000) * Allow question.question can be resolved using key path * Pass the list of env names message (environment_names_message) into pipeline init interactive flow context * Update samcli/commands/pipeline/init/interactive_init_flow.py Co-authored-by: Chris Rehn <[email protected]> * Fix unit test (trigger pr builds) * Fix integ test * Fix integ test Co-authored-by: Chris Rehn <[email protected]> * Adding account id to bootstrap message. (aws#2998) * Adding account id to bootstrap message. * adding docstring * Addressing PR comments. * Adding unit tests. * Fixing unit tests. Co-authored-by: Tarun Mall <[email protected]> * Cfn creds fix (aws#3014) * Removing pipeline user creds from cfn output. This maintains same user exp. Co-authored-by: Tarun Mall <[email protected]> * Ux bootstrap revamp 20210706 (aws#3021) * Add intro paragraph to bootstrap * Add switch account prompt * Revamp stage definition prompt * Revamp existing resources prompt * Revamp security prompt * Allow answers to be changed later * Add exit message for bootstrap * Add exit message for bootstrap (1) * Add indentation to review values * Add "Below is the summary of the answers:" * Sweep pylint errors * Update unit tests * Update samcli/commands/pipeline/bootstrap/guided_context.py Co-authored-by: Chris Rehn <[email protected]> * Update samcli/commands/pipeline/bootstrap/guided_context.py Co-authored-by: Chris Rehn <[email protected]> * Update samcli/commands/pipeline/bootstrap/guided_context.py Co-authored-by: Chris Rehn <[email protected]> * Update samcli/commands/pipeline/bootstrap/guided_context.py Co-authored-by: Chris Rehn <[email protected]> * Update samcli/commands/pipeline/bootstrap/guided_context.py Co-authored-by: Chris Rehn <[email protected]> * Update samcli/commands/pipeline/bootstrap/guided_context.py Co-authored-by: Chris Rehn <[email protected]> * Update samcli/commands/pipeline/bootstrap/guided_context.py Co-authored-by: Chris Rehn <[email protected]> * Update samcli/commands/pipeline/bootstrap/guided_context.py Co-authored-by: Chris Rehn <[email protected]> * Update samcli/commands/pipeline/bootstrap/cli.py Co-authored-by: Chris Rehn <[email protected]> * Update unit tests * Add bold to other literals Co-authored-by: Chris Rehn <[email protected]> * Adding account condition for CFN execution role. (aws#3027) Co-authored-by: Tarun Mall <[email protected]> * pipeline UX revamp 20210707 (aws#3031) * Allow running bootstrap inside pipeline init * Select account credential source within bootstrap * Add bootstrap decorations within pipeline init * Removing ip range option from bootstrap. (aws#3036) * Removing ip range option from bootstrap. * Fixing unit test from UX PR. Co-authored-by: Tarun Mall <[email protected]> * Fix toml file incorrect read/write in init --bootstrap (aws#3037) * Temporarily removing account fix. (aws#3038) Co-authored-by: Tarun Mall <[email protected]> * Rename environment to stage (aws#3040) * Improve account source selection (aws#3042) * Fixing various cosmetics UX issues with pipeline workflow. (aws#3046) * Fixing credential to credentials * Forcing text color to yellow. * Adding new line after stage diagram. * Adding extra line after checking bootstrap message. * Renaming config -> configuration * account source -> credential source * Removing old message. * Fixing indentation in list. * Fixing bunch of indentation. * fixing f string Co-authored-by: Tarun Mall <[email protected]> * Auto skip questions if stage detected (aws#3045) * Autofill question if default value is presented * Allow to use index to select stage names (aws#3051) * Updating message when bootstrap stages are missing. (aws#3058) * Updating message when bootstrap stages are missing. * Fixing indendation Co-authored-by: Tarun Mall <[email protected]> * Fixing bootstrap integ tests. (aws#3061) * Fixing bootstrap integ tests. * Cleaning up some integ tests. * Using environment variables when running integ test on CI. * Using expression instead of full loop. * Adding instruction to use default profile on local. Co-authored-by: Tarun Mall <[email protected]> * Fix bootstrap test region (#3064) * Fix bootstrap region in integ test * Fix regions in non-interactive mode as well * Add more pipeline init integ test (aws#3065) * Fix existing pipeline init integ test * Add more pipeline init integ tests * Config file bug (aws#3066) * Validating config file after bootstrap stack creation. * Validating config file after bootstrap. Co-authored-by: Tarun Mall <[email protected]> * Fix pipeline init integ test because of pipelineconfig file exists (aws#3067) * Make stage name randomized to avoid race condition among multi canary runs (aws#3078) * Load number of stages from pipeline template (aws#3059) * Load number of stages from templates * Rename variable and add debug log * Add encoding to open() * Allow roles with Tag aws-sam-pipeline-codebuild-service-role to assume PipelineExecutionRole (aws#2950) * pipeline init UX: Ask to confirm when file exists (aws#3079) * Ask to confirm overriding if files already exist, or save to another directory * Add doc links (aws#3087) * Adding accidentally removed tests back. (aws#3088) Co-authored-by: Tarun Mall <[email protected]> Co-authored-by: elbayaaa <[email protected]> Co-authored-by: Chris Rehn <[email protected]> Co-authored-by: Ahmed Elbayaa <[email protected]> Co-authored-by: Tarun <[email protected]> Co-authored-by: Tarun Mall <[email protected]>
I recently ran into a similar, but more frustrating issue. Due to an inefficient build pipeline, our developers currently rollback to a previous task definition via the console. Since this is a number of manual steps, one of our engineers attempted to recreate the manual process via the CLI. Despite the engineers having the permissions to perform the action via the console, running the command in the CLI produces a permission error that the role denies |
@fszymanski-blvd That is vaguely related, but definitely not something that is suitable for this issue. Just pay up the 29 USD for developer support and create a case. They will figure it out. Best 29$ I have ever spent. |
@fatso83 We're following that path as well. Just wasn't sure if the console had a different capability than the CLI, which would be slightly more related to this issue. |
I'm using this python program (ecs-deploy,
https://github.com/fabfuel/ecs-deploy) which is working really well to
update ecs task definitions and services.
Been using it for two years now.
It makes automated deploys really easy. Maybe you should check it out...
…On Fri, Jul 1, 2022, 11:46 Frank Szymanski ***@***.***> wrote:
@fatso83 <https://github.com/fatso83> We're following that path as well.
Just wasn't sure if the console had a different capability than the CLI,
which would be slightly more related to this issue.
—
Reply to this email directly, view it on GitHub
<#406>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAXTBKVSIE6KD6HT75F6O4TVR4AEZANCNFSM4EJ4NL2Q>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
It's amazing to me how cumbersome it is to create a task definition considering that it's provided so readily in JSON all over the place. Here I have task definitions "backed up" locally but it's like pulling teeth to "restore" them. |
How after so many years we still don't have functionality to do this natively? |
Is there any update on this? Surely there has to be a simple command that could be used to duplicate the latest task definition and update specific inputs. Currently I'm doing this by describing and then using jq to manipulate the JSON. Not ideal. |
Same problem. Tons of bash scripts needed just to be able run single container... That is a first time when I clearly felt heavy inconvenience of ECS in comparison with Kubernetes even for small projects By the way here is my workaround for
Freaking Frankenstein sewn piece by piece In my lucky case |
@5er9e1 I think you can use |
We still haven't received an update from the ECS team regarding this feature request but I have once again reached out to them for feedback. You can also consider reaching out through AWS Support if this is something you'd like to escalate further. I'm going to transfer this to our cross-SDK repository as it relates to a service API rather than the CLI directly. I will leave a comment here when we hear back from the ECS team. (P88746615) |
I have built a tool called ---
version: v1
cluster: example
tasks:
pre:
- family: app-database-migrate
count: 1
containers:
- rails
launch_type: ec2
services:
- name: app-web-server
force: false
containers:
- rails It is easy to deploy a new version of your application using the $ ecs-toolkit deploy --image-tag=49779134ca1dcef21f0b5123d3d5c2f4f47da650
INFO[0000] using config file: .ecs-toolkit.yml
INFO[0000] reading .ecs-toolkit.yml config file
INFO[0000] starting rollout of pre-deployment tasks cluster=example
INFO[0001] building new task definition from app-database-migrate:24 cluster=example task=app-database-migrate
WARN[0001] skipping container image tag update, no changes cluster=example container=rails task=app-database-migrate
WARN[0001] skipping registering new task definition, no changes cluster=example task=app-database-migrate
INFO[0001] preparing running task parameters cluster=example task=app-database-migrate
INFO[0001] no changes to previous task definition, using latest cluster=example task=app-database-migrate
INFO[0001] running new task, desired count: 1 cluster=example task=app-database-migrate
INFO[0001] watching task [1] ... last status: pending, desired status: running, health: unknown cluster=example task=app-database-migrate task-id=87356f4b0da94232b39e3527781d55a2
INFO[0004] watching task [1] ... last status: running, desired status: running, health: unknown cluster=example task=app-database-migrate task-id=87356f4b0da94232b39e3527781d55a2
INFO[0007] watching task [1] ... last status: running, desired status: running, health: unknown cluster=example task=app-database-migrate task-id=87356f4b0da94232b39e3527781d55a2
INFO[0010] watching task [1] ... last status: running, desired status: running, health: unknown cluster=example task=app-database-migrate task-id=87356f4b0da94232b39e3527781d55a2
INFO[0013] watching task [1] ... last status: stopped, desired status: stopped, health: unknown cluster=example task=app-database-migrate task-id=87356f4b0da94232b39e3527781d55a2
INFO[0013] successfully stopped task [1], reason: essential container in task exited cluster=example task=app-database-migrate task-id=87356f4b0da94232b39e3527781d55a2
INFO[0013] tasks ran to completion, desired count: 1 cluster=example task=app-database-migrate
INFO[0013] tasks report - total: 1, successful: 1, failed: 0 cluster=example
INFO[0013] completed rollout of pre-deployment tasks cluster=example
INFO[0013] starting rollout to services cluster=example
INFO[0014] building new task definition from app-web-server:103 cluster=example service=app-web-server
WARN[0014] skipping container image tag update, no changes cluster=example container=rails service=app-web-server
WARN[0014] skipping registering new task definition, no changes cluster=example service=app-web-server
INFO[0014] no changes to previous task definition, using latest cluster=example service=app-web-server
INFO[0015] updated service successfully cluster=example service=app-web-server
INFO[0015] watch service rollout progress cluster=example service=app-web-server
INFO[0015] watching ... service: active, deployment: primary, rollout: 1/1 (0 pending) cluster=example deployment-id=ecs-svc/6300252591410027253 service=app-web-server
INFO[0015] checking if service is stable cluster=example service=app-web-server
INFO[0016] service is stable cluster=example service=app-web-server
INFO[0016] services report - total: 1, successful: 1, failed: 0 cluster=example
INFO[0016] completed rollout to services cluster=example
WARN[0016] skipping rollout of post-deployment tasks, none found cluster=example Obviously, I've focused on my use-case but I have tried to leave room for other use-cases. Supported functionality:
|
@itskingori Your |
i have Blue/Green deployment implemented |
FYI: Copilot CLI looks a better replacement for the CLI |
For those who have looked at fargatecli, here is a fork that is more actively maintained that gives you a one-liner to deploy a new image. It also has several other useful commands for working with envvars, secrets, logs, ops, and also works with docker-compose.yml files.
|
It seems the following attributes should also be removed. del(.registeredAt) | del(.registeredBy) |
We heard back from the ECS team that this is not something currently on their roadmap and they recommended using this public roadmap for tracking updates: https://github.com/aws/containers-roadmap Looking through this issue, several workarounds have been noted. But if those do not suffice then I recommend letting the ECS team know in this new issue I created for them to track: aws/containers-roadmap#2058 |
This issue is now closed. Comments on closed issues are hard for our team to see. |
I have slightly modified this that doesn't need 'jq' but can use custom tag #!/bin/sh
# Define the full image name with tag
FULL_IMAGE="registry/project:mycustomtag"
# Retrieve details of the existing ECS task definition
TASK_DEFINITION=$(aws ecs describe-task-definition \
--task-definition "$TASK_DEFINATION_NAME" \
--region "$REGISTRY_REGION" \
--query '{ containerDefinitions: taskDefinition.containerDefinitions,
family: taskDefinition.family,
executionRoleArn: taskDefinition.executionRoleArn,
volumes: taskDefinition.volumes,
placementConstraints: taskDefinition.placementConstraints,
cpu: taskDefinition.cpu,
memory: taskDefinition.memory
}')
# Modify the task definition to update the image name with the provided full image
NEW_TASK_DEFINITION=$(echo "$TASK_DEFINITION" | sed "s|\"image\": \".*\"|\"image\": \"$FULL_IMAGE\"|")
echo $NEW_TASK_DEFINITION
# Register the modified task definition
NEW_TASK_INFO=$(aws ecs register-task-definition \
--region "$REGISTRY_REGION" \
--cli-input-json "$NEW_TASK_DEFINITION")
echo $NEW_TASK_INFO
# Extract the revision number of the newly registered task definition
REVISION=$(echo "$NEW_TASK_INFO" | grep -o '"revision":[^,]*' | cut -d':' -f2)
# Remove leading and trailing whitespaces from the revision number
NEW_REVISION=$(echo $REVISION | tr -d ' ')
echo $NEW_REVISION
# Update ecs service
UPDATE_SERVICE=$(aws ecs update-service \
--region $REGISTRY_REGION \
--cluster ${CLUSTER_NAME} \
--service ${SERVICE_NAME} \
--task-definition ${TASK_DEFINATION_NAME}:${NEW_REVISION})
|
Is there a way to add a new revision to a ECS task definition?
In my case I want to update the container URL in my CD pipeline using the command line. Either the documentation is missing how to do that or it is only possible currently using the management console?
see aws/amazon-ecs-cli#91 (but i am not using docker compose)
The text was updated successfully, but these errors were encountered: