- Newest
- Most votes
- Most comments
The missing logback-default.xml file in your AWS Blu Age Runtime configuration is not an uncommon issue. While this file is typically expected to be present in the config folder, its absence doesn't necessarily mean your setup is incorrect or that you can't proceed with the certification.
Here are some options to resolve this issue:
-
Check if there's a logback-cloudwatch.yml file in your config folder instead. This file is sometimes used for CloudWatch logging configuration and may be referenced in the application-main.yml file (though it's usually commented out by default).
-
You can create a basic logback-default.xml file yourself if needed. This is a standard logging configuration file for the Logback logging framework.
-
Configure logging directly in the application-main.yml file, which is one of the primary configuration files for AWS Blu Age Runtime.
For most AWS Blu Age Runtime setups, the absence of logback-default.xml shouldn't prevent your application from running. The core configuration is handled by the YAML files you've already copied (application-bac.yml, application-main.yml, and application-utility-pgm.yml).
You can proceed with the next steps of the certification process without this file. If you encounter specific errors related to logging when trying to run your application, you may need to adjust your setup further, but many users have successfully completed the workshop without this specific file.
Sources
AWS Blu Age backend/configuration: logback-default.xml missing | AWS re:Post
answered a year ago
Relevant content
- AWS OFFICIALUpdated 4 years ago
