- 최신
- 최다 투표
- 가장 많은 댓글
The best way is to create an EC2 instance in VPC1 and access to the application deployed in Mainframe Modernization service from the EC2 instance so that you stay isolated.
Another option is to check the option Allow application deployed to this environment to be publicly accessible when creating the Mainframe Modernization environment.
Allow applications deployed to this environment to be publicly accessible.
Mainframe Modernization service assigns a public IP address to the environment.
Amazon EC2 instances and other resources outside of the VPC can connect to your environment. Resources inside the VPC can also connect to the environment.
Choose one or more security groups that specify which resources can connect to the environment.
This is not the recommended way to do in the L3 workshop: https://catalog.workshops.aws/aws-blu-age-l3-certification-workshop/en-US/go-live/deploy/create-env
Even with this option it did not work for me. Allow application deployed to this environment to be publicly accessible
Did you try creating an EC2 instance in VPC1 as well ?
I have updated my question with the observation. It'll very helpful if you can have a look.
관련 콘텐츠
- AWS 공식업데이트됨 일 년 전
Just a note: Peering would fail since both the VPC have an overlapping CIDR range.