[ECS] [RunTask]: logConfiguration Override
**Tell us about your request** Extend the `overrides` parameter of RunTask and StartTask with logConfiguration. ``` "overrides": { "containerOverrides": [{ "command": ["string"], "cpu": number, "environment": [{ "name": "string", "value": "string" }], "memory": number, "memoryReservation": number, "name": "string", "logConfiguration" { logDriver: 'configurable', options: { 'awslogs-group': 'configurable', 'awslogs-region': 'configurable', 'awslogs-stream-prefix': 'configurable' } } }], "executionRoleArn": "string", "taskRoleArn": "string" }, ``` **Which service(s) is this request for?** ECS **Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?** When running one-off tasks, on a copy a Taskdefinition of an existing running services. The logs end up in Cloudwatch in the same Loggroup as the live service. This makes it hard to lookup the logs in Cloudwatch. I'm also using RunTask for creating Cloudwatch cron events which trigger RunTask through a lambda. Having a seperate Cloudwatch Loggroup would really make it easier to have the logs of those cron-tasks in a seperate group. **Are you currently working around this issue?** Search for keyword in cloudwatch **Additional
Posted by maartenvanderhoef on Dec 19, 2018, 3:31 PM
Tags
Related issues
- To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
- > The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
- Custom trigger IDs are not displayed in the new 2026.10 trigger selector
- I hate that too, but I think it’s more the ux than the concept of a default.
- > The biggest problem with UX developers is they know better than you AND force you into their paradigm.
- "Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments
ux (Other)
To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
> The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
Custom trigger IDs are not displayed in the new 2026.10 trigger selector
I hate that too, but I think it’s more the ux than the concept of a default.
> The biggest problem with UX developers is they know better than you AND force you into their paradigm.
"Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
The biggest problem with this is if the target URL doesn't load but also doesn't quickly error out, like e.g.
Google wants to build up a private web here.
[ECS] [RunTask]: logConfiguration Override
**Tell us about your request** Extend the `overrides` parameter of RunTask and StartTask with logConfiguration. ``` "overrides": { "containerOverrides": [{ "command": ["string"], "cpu": number, "environment": [{ "name": "string", "value": "string" }], "memory": number, "memoryReservation": number, "name": "string", "logConfiguration" { logDriver: 'configurable', options: { 'awslogs-group': 'configurable', 'awslogs-region': 'configurable', 'awslogs-stream-prefix': 'configurable' } } }], "executionRoleArn": "string", "taskRoleArn": "string" }, ``` **Which service(s) is this request for?** ECS **Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?** When running one-off tasks, on a copy a Taskdefinition of an existing running services. The logs end up in Cloudwatch in the same Loggroup as the live service. This makes it hard to lookup the logs in Cloudwatch. I'm also using RunTask for creating Cloudwatch cron events which trigger RunTask through a lambda. Having a seperate Cloudwatch Loggroup would really make it easier to have the logs of those cron-tasks in a seperate group. **Are you currently working around this issue?** Search for keyword in cloudwatch **Additional
Comments (0)
No comments yet. Start the discussion.