AWS BluAge L3 workshop. Go-Live-Deploy-Start application. Application start is failing

Question

The carddemo application is failed to start after successful deployment.
Logs attached.
2025-08-03T18:04:30.815Z
Caused by: org.postgresql.util.PSQLException: FATAL: password authentication failed for user "carddemo"
2025-08-03T18:04:30.815Z
at org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:698)
2025-08-03T18:04:30.815Z
at org.postgresql.core.v3.ConnectionFactoryImpl.tryConnect(ConnectionFactoryImpl.java:207)
2025-08-03T18:04:30.815Z
at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:262)
2025-08-03T18:04:30.815Z
at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:54)
2025-08-03T18:04:30.815Z
at org.postgresql.jdbc.PgConnection.(PgConnection.java:273)
2025-08-03T18:04:30.815Z
at org.postgresql.Driver.makeConnection(Driver.java:446)
2025-08-03T18:04:30.815Z
at org.postgresql.Driver.connect(Driver.java:298)
2025-08-03T18:04:30.815Z
at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:138)
2025-08-03T18:04:30.815Z
at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:359)
2025-08-03T18:04:30.815Z
at com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:201)
2025-08-03T18:04:30.815Z
at com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:470)
2025-08-03T18:04:30.815Z
at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:561)
2025-08-03T18:04:30.815Z
at com.zaxxer.hikari.pool.HikariPool.(HikariPool.java:100)
2025-08-03T18:04:30.815Z
at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:112)
2025-08-03T18:04:30.815Z
... 164 more
2025-08-03T18:04:30.815Z
03-Aug-2025 18:04:30.041 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio-8194"]
2025-08-03T18:04:30.815Z
03-Aug-2025 18:04:30.041 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Catalina]
2025-08-03T18:04:30.815Z
03-Aug-2025 18:04:30.043 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-8194"]
2025-08-03T18:04:30.815Z
03-Aug-2025 18:04:30.056 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [gapwalk-application] appears to have started a thread named [idle-connection-reaper] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
2025-08-03T18:04:30.815Z
java.base@17.0.16/java.lang.Thread.sleep(Native Method)
2025-08-03T18:04:30.815Z
software.amazon.awssdk.http.apache.internal.conn.IdleConnectionReaper$ReaperTask.run(IdleConnectionReaper.java:151)
2025-08-03T18:04:30.815Z
java.base@17.0.16/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
2025-08-03T18:04:30.815Z
java.base@17.0.16/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
2025-08-03T18:04:30.815Z
java.base@17.0.16/java.lang.Thread.run(Thread.java:840)

re:Post Agent · Answer

The error in your AWS Blu Age L3 workshop application is a database authentication issue. The logs show a clear error message: "FATAL: password authentication failed for user 'carddemo'", which indicates that the application is unable to connect to the PostgreSQL database with the provided credentials.

To resolve this issue, you should:

1. Verify that the password in AWS Secrets Manager matches the actual password set for the "carddemo" user in your PostgreSQL database. There might be a mismatch between the credentials stored in Secrets Manager and the actual database credentials.

2. Check the configuration files (carddemo-application.json and application-carddemo.yaml) to ensure they have the correct Secret ARNs referenced for database access.

3. Confirm that the database name configuration is correct in both AWS Secrets Manager and your application YAML files.

4. If you recently made changes to configuration files on S3 without rebuilding the package, you might need to go back to the "Golive>Prepare>Package>Package backend and frontend applications" step and rebuild the package to incorporate your changes.

5. Ensure that case sensitivity is correct in all resource names. In some cases, resources might have been created with capital letters but referenced with lowercase in the application, causing connectivity issues.

Once you've made these corrections, try starting the application again. If the issue persists, check the full application logs for additional error messages that might provide more context.  
**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 Blu Age L3 workshop -(Go Live->Start Application Failed) | AWS re:Post](https://repost.aws/questions/QUXovA6aqcTWqW1Ddsy0hbzg/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 BluAge L3 workshop. Go-Live->Deploy->Start application. Application start is failing

Add your answer

Relevant content