how to override / set Docker Labels by using the AWS-cli ecs run-task

Unfortunately, there isn't a direct way to override or set Docker labels using the AWS CLI's ecs run-task command for AWS Fargate. The run-task command doesn't provide a specific parameter for modifying Docker labels at runtime.

However, you can use the "overrides" parameter in the run-task command to override certain aspects of your task definition. While this doesn't directly allow you to set Docker labels, you can use it to override environment variables, which might help you achieve a similar goal in some cases.

For example, you could use the overrides parameter to set environment variables that your application could then use to modify its behavior or configuration at runtime. Here's an example of how you might use overrides in a run-task command:

aws ecs run-task --cluster your-cluster-name --task-definition your-task-definition \
--overrides '{"containerOverrides": [{"name": "your-container-name", "environment": [{"name": "ENV_VAR_NAME", "value": "ENV_VAR_VALUE"}]}]}'

This approach allows you to pass in dynamic values at runtime, which your application could then use to set up its configuration or behavior.

If you absolutely need to modify Docker labels, you would need to do this at the task definition level before running the task. Docker labels are typically set in the Dockerfile or when the image is built, and they become part of the image metadata. Once an image is built and pushed to a registry, its labels cannot be changed without rebuilding the image.

For truly dynamic labeling needs, you might need to consider alternative approaches, such as using environment variables and having your application logic handle the desired functionality that you were hoping to achieve with Docker labels.

Sources
RunTask - Amazon Elastic Container Service
Run Amazon ECS or Fargate tasks with Step Functions - AWS Step Functions