IssueRaiser

[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

Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments

ux (Other)

[ECS] [RunTask]: logConfiguration Override

maartenvanderhoefDec 19, 2018, 3:31 PM

**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.

Comment on this issue