Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

I’m getting an error in my agent logs, using an ECSTask Infrastructure Block
```An error occured while monitoring flow run '793a0ee8-fe06-48d3-8858-31b2e99e4c50'. The flow run will not be marked as failed, but an issue may have occurred.```
I think the Agent is trying to watch the created ECS Task’s logs, and using the wrong parameters to watch them

here’s the line of code in `prefect-aws` that shows up in the stack trace <https://github.com/PrefectHQ/prefect-aws/blob/267d973fcf9f9ccf1a4508140daf5b033a53c609/prefect_aws/ecs.py#L1013>

the ECSTask is configured like
```ECSTask(
  ...
  stream_output = True,
  configure_cloudwatch_logs = True,
)```


and the error that’s at the top (?) of the stack trace:

```An error occurred (ResourceNotFoundException) when calling the GetLogEvents operation: The specified log stream does not exist.```

I'm getting the same error. It looks like the `prefect-aws`  <https://github.com/PrefectHQ/prefect-aws/blob/267d973fcf9f9ccf1a4508140daf5b033a53c609/prefect_aws/ecs.py#L964-L970|code> is being built using `log-stream-prefix/family/task-definition:revision`.
```stream_name = "/".join(
                    [
                        log_config["awslogs-stream-prefix"],
                        task_definition["family"],
                        task_arn.rsplit("/")[-1],
                    ]
                )```
Meanwhile, aws creates the logs stream using `log-stream-prefix/container-name/container-id`

I'm getting the same error. It looks like the `prefect-aws`  <https://github.com/PrefectHQ/prefect-aws/blob/267d973fcf9f9ccf1a4508140daf5b033a53c609/prefect_aws/ecs.py#L964-L970|code> is being built using `log-stream-prefix/family/task-definition:revision`.
```stream_name = "/".join(
                    [
                        log_config["awslogs-stream-prefix"],
                        task_definition["family"],
                        task_arn.rsplit("/")[-1],
                    ]
                )```
Meanwhile, <https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_awslogs.html|aws docs> creates the log stream using `log-stream-prefix/container-name/ecs-task-id`

We have not been able to reproduce this and the tests are working — it’d be great to have a simple example so we can fix this.

More details at <https://github.com/PrefectHQ/prefect-aws/issues/177> would be appreciated.

Thanks! <https://github.com/PrefectHQ/prefect-aws/pull/186>