New featureMedium

Amazon ECS now provides Action Logs for deployment and orchestration visibility

Amazon ECS introduces Action Logs, delivering detailed records of service-side operations during deployments and managed daemon updates to improve monitoring and troubleshooting

Amazon Elastic Container Service (Amazon ECS) now introduces Action Logs, a new observability feature that delivers detailed, timestamped records of the actions Amazon ECS performs on behalf of customers during service deployments and ECS Managed Daemon updates. This visibility into previously invisible service-side operations allows you to monitor and troubleshoot your workloads directly, without contacting AWS Support or manually correlating data from multiple sources. Action Logs provide visibility into key deployment state transitions of service deployments and Managed Daemon updates. Each log entry includes the event name, log level (INFO, WARN, or ERROR), relevant resource ARNs, and a status reason, helping reduce mean time to resolution when issues arise. You can opt in at the cluster level through the Amazon ECS console or by using Amazon CloudWatch vended logs APIs, and choose to deliver logs to Amazon CloudWatch Logs, Amazon S3, or Amazon Kinesis Data Firehose depending on your operational needs. At launch, Amazon Q in the Amazon ECS console integrates with Action Logs to automatically detect deployment issues such as circuit breaker rollbacks and unstable service revisions, providing customers with root cause analysis, resource-level comparisons, and step-by-step remediation guidance without leaving the console. Standard CloudWatch Logs, Amazon S3, or Amazon Data Firehose pricing applies for log ingestion and storage. For pricing details, see Amazon CloudWatch Pricing. Amazon ECS Action Logs are available in all AWS Regions, including the AWS GovCloud (US) Regions.

Read the original AWS announcement

Related articles and terms

Why CloudWatch Logs Costs More Than You Expect - The Cost Structure of Ingestion, Storage, and AnalysisThis article explains the pricing structure where CloudWatch Logs ingestion costs over 20 times more than storage, the cost explosions caused by VPC Flow Logs and Lambda logs, and optimization strategies using the Infrequent Access class and S3 export.The Integration Power of the AWS Observability Stack - Operational Transparency Through CloudWatch, X-Ray, and CloudTrailThis article examines the integration level of the AWS observability stack centered on CloudWatch, X-Ray, and CloudTrail, comparing it with Azure Monitor and GCP Cloud Logging to explain how the three pillars of metrics, traces, and logs drive differences in operational quality.Amazon CloudWatchA service that provides monitoring, log management, and alarms for AWS resources and applicationsAmazon ECSA fully managed container orchestration service for deploying, managing, and scaling Docker containers, offering both Fargate and EC2 launch typesBuilding a Security Data Lake with Amazon Security Lake - Unified Analysis in OCSF FormatLearn about Security Lake's automatic aggregation of CloudTrail, VPC Flow Logs, and Route 53 logs, OCSF normalization, and integration with subscribers.