The open source version of the AWS Elastic Beanstalk Developer Guide. You can submit feedback and requests for changes by submitting issues in this repo or by making proposed changes and submitting a pull request.
I followed the Elastic Beanstalk custom CloudWatch logs documentation, but stumbled into permissions errors. I've laid the issues out in great detail in my Stack Overflow question.
This reference is for the older deprecated CloudWatch Logs agent. If you use Instance Metadata Service Version 2 (IMDSv2), you must use the new unified CloudWatch agent. Even if you are not using IMDSv2, we strongly recommend that you use the newer unified CloudWatch agent instead of the older logs agent.
I was able to create a new configuration file that sets up Elastic Beanstalk to use the new CloudWatch agent. You can check my Stack Overflow answer, but here's the gist of it:
Closing this issue or pull request in advance of archiving this repo. For more information about the decision to archive this repo (and others in the 'awsdocs' org), see the announcement on the AWS News Blog.
I followed the Elastic Beanstalk custom CloudWatch logs documentation, but stumbled into permissions errors. I've laid the issues out in great detail in my Stack Overflow question.
The problem is that the Elastic Beanstalk docs encourage the usage of the CloudWatch Logs agent, but it states the following:
I was able to create a new configuration file that sets up Elastic Beanstalk to use the new CloudWatch agent. You can check my Stack Overflow answer, but here's the gist of it:
.ebextensions/custom-cloudwatch-logs.config
The official Elastic Beanstalk docs should provide a solution that revolves around this new approach, rather than the outdated CloudWatch Logs agent.