AWS L3 Troubleshooting CARDDEMO application start fails after previously being successful

Based on the error you're encountering, it appears that your CARDDEMO application is failing during startup due to database connectivity or configuration issues. The specific error indicates a problem with creating the metadata table for the Bluesam component, which is a critical part of the AWS Blu Age runtime.

Here are some troubleshooting steps to resolve this issue:

1. Check your database credentials: The error suggests there might be an authentication problem with your database. Verify that the passwords in AWS Secrets Manager match the actual passwords for your database users, particularly for the "carddemo" user.

2. Verify database configuration: Ensure that the database name configuration is correct in both AWS Secrets Manager and your application YAML files. The application needs to find the database name either in the secret or in the YAML configuration.

3. Check Secret ARNs: Review your carddemo-application.json file and application-carddemo.yaml file to ensure they contain the correct ARNs for your AWS Secrets Manager secrets.

4. Check for case sensitivity issues: One common issue is a mismatch in resource naming. For example, if your database was created with capital letters but is referenced with lowercase letters in your application configuration, this can cause connectivity problems.

5. Review configuration files: Make sure all necessary configurations for Redis, database, and other components are correctly set in your application properties files.

6. Rebuild and redeploy: If you've made configuration changes directly on S3 without rebuilding the application package, try going back to the "Golive>Prepare>Package>Package backend and frontend applications" step and rebuild the package with all your updated configurations.

Since the application was working previously and then failed after being stopped, it's possible that either a resource was changed/deleted or there's an issue with the configuration that wasn't apparent during the initial successful deployment.
Sources
AWS Blu Age L3 workshop -(Go Live->Start Application Failed) | AWS re:Post
AWS Blu Age L3 workshop -(Go Live->Start Application Failed) | AWS re:Post
AWS BluAge L3 workshop. Go-Live->Deploy->Start application. Application fails to start. | AWS re:Post