Go live - front end application is not accessible

Hello,

I understand that the application is successfully created and deployed to AWS Blu Age environment and you performed all the listed steps and the application is in running state as mentioned but you can’t access the frontend application and getting the HTTP 404 error.

I would like to mention that HTTP Status Code: 404 [1] indicates that the action or operation requested is invalid. Therefore would request you to kindly verify that the action is typed correctly.

On further research, I found that if you can't access the URL for a running AWS Mainframe Modernization application that you created and deployed to an AWS Mainframe Modernization runtime environment, you might need to configure the inbound rules on the security group that you associated with the runtime environment.

I would request you to kindly refer the AWS Mainframe Modernization documentation [2] on troubleshooting the cannot access an application URL error.

Please note that in case the issue still persists post referencing the shared documentations then kindly open a support case with AWS using the following link: [https://console.aws.amazon.com/support/home#/case/create], as we require details that are non-public information to answer your question.

References: [1] https://docs.aws.amazon.com/apptest/latest/APIReference/CommonErrors.html [2] https://docs.aws.amazon.com/m2/latest/userguide/both-application-connectivity.html

The issue you're experiencing with the frontend application not being accessible and receiving an HTTP 404 error could be due to several factors. Based on the information provided, here are some potential causes and solutions:

1. Network Configuration: Ensure that the AppStream instance and the Mainframe Modernization environment are in the same VPC. This is crucial for proper communication between components.

2. Security Group Settings: Verify that the security group associated with your Mainframe Modernization environment allows all traffic inside the VPC. This is necessary for the AppStream instance to access the application.

3. Public Accessibility: Check if you've enabled the option "Allow application deployed to this environment to be publicly accessible" when creating the Mainframe Modernization environment. This option assigns a public IP address to the environment, allowing resources outside the VPC to connect.

4. Application Configuration: Review your application's configuration files, particularly the carddemo-application.json and application-carddemo.yaml files. Ensure that all paths, URLs, and port numbers are correctly specified.

5. Database Connection: The logs you've shared indicate potential issues with database connections. Verify that your database configurations (including URLs, usernames, and passwords) are correct in your application properties files.

6. Secrets Manager: There seems to be a warning about a missing secret key. Double-check that all necessary secrets are properly set up in AWS Secrets Manager and that your application has the correct permissions to access them.

7. Server Configuration: Although the logs show that the server has started, there might be issues with how the application is configured to serve the frontend. Verify that the correct context path is set for your web application.

8. Deployment Process: Ensure that all steps in the deployment process were completed successfully, including the packaging of both backend and frontend applications.

If these steps don't resolve the issue, you may need to review the entire deployment process, checking each configuration file and deployment step carefully. It's also worth considering opening a support case with AWS for more detailed assistance, as some of the required troubleshooting may involve non-public information about your specific setup.
Sources
Accessing go-live application - AWS Blu Age L3 certification workshop | AWS re:Post
My carddemo-karla application (Frankfurt) is not being accessible online | 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