BluAge L3 workshop go-live region selection

For the AWS Blu Age L3 certification workshop, there is a specific setup regarding regions that you need to follow:

1. The development environment, including the AppStream setup, should be in the Frankfurt region (eu-central-1). This is because the BluAge-L3-Workshop-Image is only available in this region.

2. However, for the go-live step and deployment of the application, you should use a different region. Typically, the rest of the setup for go-live, including AWS Mainframe Modernization, EC2 instances, and AWS RDS, is done in a separate region, such as Mumbai (ap-south-1).

This split setup can cause some connectivity issues when trying to access the deployed application. To resolve this, you have a few options:

1. Create an EC2 instance in the same VPC as your Mainframe Modernization application deployment. This allows you to access the application while staying isolated within the deployment region.

2. When creating the Mainframe Modernization environment, you can check the option to "Allow application deployed to this environment to be publicly accessible." However, this is not the recommended approach for the L3 workshop.

3. You might need to adjust security group rules to allow traffic between the different regions and resources.

In summary, while the development environment uses the EU region (eu-central-1) due to image availability constraints, you should choose a different region for the actual go-live deployment of your application. Just be prepared to handle the cross-region connectivity challenges that may arise.
Sources
Accessing go-live application - AWS Blu Age L3 certification workshop | AWS re:Post

Perfect. L3 workshop users can utilize eu-central-1 for end to end cycle to minimize the risk of cross region issues.