- Newest
- Most votes
- Most comments
Hello.
awslogs stands for CloudWatch logs Agent.
Please use CloudWatch Agent as CloudWatch logs Agent is deprecated.
https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/UsePreviousCloudWatchLogsAgent.html
CloudWatch includes a unified CloudWatch agent that can collect both logs and metrics from EC2 instances and on-premises servers. The older logs-only agent is deprecated and is no longer supported.
For information about migrating from the older logs-only agent to the unified agent, see Create the CloudWatch agent configuration file with the wizard.
The rest of this section explains the use of the older CloudWatch Logs agent for customers who are still using it.
The Amazon Linux 2023 repository includes CloudWatch Agent (amazon-cloudwatch-agent).
https://docs.aws.amazon.com/linux/al2023/release-notes/all-packages-AL2023.2.html
Thanks Riku,
I understand the reason behind the removal of awslogs
now, but I have a follow-up question: I don't have any existing awslogs configuration so I guess there is no thing to migrate. The guide you provided in the link https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/UsePreviousCloudWatchLogsAgent.html seems to be for the old Cloud Watch Logs Agent, not how to use Cloud Watch Agent to forward application logs to Cloud Watch.
My use case is this: I have a docker container running in an EC2 (running AL2023), and I want to forward container logs to CloudWatch using the agent. Can you please point me to any relevant doco?
Best, Tony
Relevant content
- asked 6 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago
Docker container logs can be output to CloudWatch using a log driver. This means that CloudWatch Agent should be usable even if it is not installed. https://docs.docker.com/config/containers/logging/awslogs/ https://repost.aws/knowledge-center/cloudwatch-docker-container-logs-proxy