Support enhanced health reporting, managed platform updates, immutable updates, immutableĭeployments, and rolling deployments with an additional batch. In addition, platform versions earlier than v2.0.0 don't For details, see Viewing Logs from Amazon EC2 Instances in Your Elastic Beanstalk Environment In the AWS Elastic Beanstalk Developer Guide.īundle logs. For details, see AWS Elastic Beanstalk Worker Environments įor information about previous platform versions, see Tomcat platform history.NET Core on LinuxĮlastic Beanstalk supports the following.
#Apache tomcat on windows server 2012 update
You can alsoĮnable automated managed updates as part of normal update practices.įor more information about security-related software updates for Amazon Linux, see the Amazon Linux Security Center. Your application dependency, we recommend that you upgrade to the latest Elastic Beanstalk platform version to mitigate CVE-2021-44228 or CVE-2021-45046. If you've customized log4j installation as Out of caution, Elastic Beanstalk released new platform versions that use the latest Amazon Linux default package repositories, which include the Log4j hotpatched JDK, in our Amazon Linux platform release on December 21, 2021. Take action to update your application’s code to mitigate this issue.
If you've made configuration changes to your application’s use of log4j, or installed newer versions of log4j, then we recommend that you The Amazon Linux 1 and Amazon Linux 2 repositories are not affected by CVE-2021-44228 or CVE-2021-45046 in their default configuration. AWS Elastic Beanstalk installs Log4j from the Amazon Linux default package repositories in its Tomcat platforms for Amazon Linux 1 and Amazon Linux 2.
0 kommentar(er)
