Watch Desk posted an update
Amazon ECS Action Logs now cover tasks, container instances, clusters and capacity providers, giving operators more detail when tasks fail or clusters do not scale as expected.
Why it mattersThe logs can show why a task failed to start, including image-pull errors, missing EBS permissions or a lack of subnet IP addresses. For stopped tasks, they record the container exit code and the health check that triggered the stop. If Action Logs are already in use, AWS says the new events arrive without configuration changes. Otherwise, teams can opt in at cluster level and send logs to CloudWatch Logs, S3 or Data Firehose, with the usual destination charges. Less guesswork is welcome; another bill is less so.
Discuss: Should cloud platforms make detailed operational logs opt-in, or enable them by default and leave teams to manage the cost?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.