AWS Blu Age L3 workshop -(Go Live-Start Application Failed)

Question

Hello, Facing error on Go Live step for L3 workshop. After Deploying application succussed, I tried to start application. But It failed.
When I checked BluAgeConsoleLog, I found the following messages

20-May-2025 16:10:04.936 INFO [main] org.apache.catalina.core.ApplicationContext.log 2 Spring WebApplicationInitializers detected on classpath
2025-05-20T16:10:05.451Z  WARN ??? --- [           main] c.n.b.g.r.s.AbstractAwsSecretsListener   : Key spring.aws.client.gapwalk.redis.secret not found, secret manager will not be used
2025-05-20T16:10:05.452Z  WARN ??? --- [           main] c.n.b.g.r.s.AbstractAwsSecretsListener   : Key spring.aws.client.bluesam.db.secret not found, secret manager will not be used
2025-05-20T16:10:05.452Z  WARN ??? --- [           main] c.n.b.g.r.s.AbstractAwsSecretsListener   : Key spring.aws.client.bluesam.redis.secret not found, secret manager will not be used
2025-05-20T16:10:05.453Z  WARN ??? --- [           main] c.n.b.g.r.s.AbstractAwsSecretsListener   : Key spring.aws.client.bluesam.locks.redis.secret not found, secret manager will not be used
2025-05-20T16:10:05.453Z  WARN ??? --- [           main] c.n.b.g.r.s.AbstractAwsSecretsListener   : Key spring.aws.client.jics.queues.ts.redis.secret not found, secret manager will not be used
**2025-05-20T16:10:05.560Z ERROR ??? --- [           main] o.s.boot.SpringApplication               : Application run failed**

If you have any idea what the cause of this error is and how to solve it, please let me know.

Arun · Accepted Answer

To resolve this issue,

1. Verify and update the database name configuration in both AWS Secrets Manager and application YAML files because the error “java.lang.IllegalStateException: Db name for the database secret was passed neither in the secret nor in the yaml” you posted on below repost [1] explicitly states that the database name is missing from both the secret and the YAML configuration, which is critical for application startup and database connectivity.

2. Review and correct the Spring Boot application properties related to AWS Secrets Manager integration because multiple WARN messages [e.g., Key spring.aws.client.gapwalk.redis.secret not found] indicate that the application is unable to find several required secrets, suggesting a potential misconfiguration in how the application is set up to interact with AWS Secrets Manager.

3. Verify RDS master password if user matches with AWS Secrets Manager and test connectivity because Password authentication failures often occur due to mismatched credentials between RDS and Secrets Manager, requiring immediate verification and connectivity testing

4. Check all configuration files for correct Secret ARNs and credentials because Application reads from multiple configuration files, and any mismatch in ARNs or credentials across these files can cause startup failures

5. Review and potentially rebuild the "Golive>Prepare>Package" step ensuring all updated configurations are included in deployment because Previous successful deployment followed by failure after configuration changes suggests package rebuild might be needed to incorporate new settings.

[1] https://repost.aws/questions/QUXNSIQLiGQMuwy0FtIVnDzA/aws-blu-age-l3-workshop-go-live-start-application-failed

re:Post Agent · Answer

The error you're encountering during the Go Live step of the AWS Blu Age L3 workshop appears to be related to configuration issues, particularly with AWS Secrets Manager and database connections.

The warning messages indicate that several secret keys are not found, which suggests that the application is unable to retrieve necessary credentials from AWS Secrets Manager. This could be due to incorrect configuration or missing permissions.

To resolve this issue, you should:

1. Check your AWS Secrets Manager configuration. Ensure that all required secrets are properly set up and that the application has the necessary permissions to access them.

2. Verify that the secret names in your application configuration match exactly with those in AWS Secrets Manager.

3. Double-check your database connection settings, including URLs, usernames, and passwords. Make sure these are correctly configured in your application properties or YAML files.

4. Review the application's configuration files, particularly application.yml or application.properties, to ensure all necessary settings are correct.

5. Verify that your AWS credentials and region settings are properly configured in your environment.

6. Check the full stack trace in the logs for more detailed error information that might point to the root cause.

If the issue persists after checking these points, you may need to review your application's overall configuration more thoroughly. Sometimes, the problem can be as simple as a typo in a configuration file or a mismatch between expected and actual secret names or database connection details.

Remember that troubleshooting these issues is part of the learning process for the L3 certification. If you continue to face difficulties, don't hesitate to reach out to the workshop support team for more specific guidance.  
**Sources**  
[AWS Blu Age L3 workshop -(Go Live->Start Application Failed) | AWS re:Post](https://repost.aws/questions/QUXNSIQLiGQMuwy0FtIVnDzA/aws-blu-age-l3-workshop-go-live-start-application-failed)  
[AWS BluAge L3 workshop. Go-Live->Deploy->Start application. Application fails to start. | AWS re:Post](https://repost.aws/questions/QU5dOmCccoTMW-Z177nuI6uA/aws-bluage-l3-workshop-go-live-deploy-start-application-application-fails-to-start)

AWS Blu Age L3 workshop -(Go Live->Start Application Failed)

Add your answer

Relevant content