The service deployed as apply ignores the inbound rules of the ec2 instance
I have currently deployed Nextjs14 through Amplify. The backend is deployed in EC2 and is linked to the public zone of the custom vpc. They are using the same domain. api.example.com (backend), www.example.com (front)
The service deployed as apply ignores the inbound rules of the ec2 instance
I have currently deployed Nextjs14 through Amplify. The backend is deployed in EC2 and is linked to the public zone of the custom vpc. They are using the same domain. api.example.com (backend), www.example.com (front)
The service deployed as apply ignores the inbound rules of the ec2 instance
I have currently deployed Nextjs14 through Amplify. The backend is deployed in EC2 and is linked to the public zone of the custom vpc. They are using the same domain. api.example.com (backend), www.example.com (front)
The service deployed as apply ignores the inbound rules of the ec2 instance
I have currently deployed Nextjs14 through Amplify. The backend is deployed in EC2 and is linked to the public zone of the custom vpc. They are using the same domain. api.example.com (backend), www.example.com (front)
The service deployed as apply ignores the inbound rules of the ec2 instance
I have currently deployed Nextjs14 through Amplify. The backend is deployed in EC2 and is linked to the public zone of the custom vpc. They are using the same domain. api.example.com (backend), www.example.com (front)
The service deployed as apply ignores the inbound rules of the ec2 instance
I have currently deployed Nextjs14 through Amplify. The backend is deployed in EC2 and is linked to the public zone of the custom vpc. They are using the same domain. api.example.com (backend), www.example.com (front)
The service deployed as apply ignores the inbound rules of the ec2 instance
I have currently deployed Nextjs14 through Amplify. The backend is deployed in EC2 and is linked to the public zone of the custom vpc. They are using the same domain. api.example.com (backend), www.example.com (front)
The service deployed as apply ignores the inbound rules of the ec2 instance
I have currently deployed Nextjs14 through Amplify. The backend is deployed in EC2 and is linked to the public zone of the custom vpc. They are using the same domain. api.example.com (backend), www.example.com (front)
The service deployed as apply ignores the inbound rules of the ec2 instance
I have currently deployed Nextjs14 through Amplify. The backend is deployed in EC2 and is linked to the public zone of the custom vpc. They are using the same domain. api.example.com (backend), www.example.com (front)
The service deployed as apply ignores the inbound rules of the ec2 instance
I have currently deployed Nextjs14 through Amplify. The backend is deployed in EC2 and is linked to the public zone of the custom vpc. They are using the same domain. api.example.com (backend), www.example.com (front)