You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner. It is now read-only.
Apparently you can assign a public IP to EC2 instances in the "internal" (private) subnets. Nobody should do this, but it's technically possible.
This will allow sending data to private EC2 instances (e.g. via UDP), but the route back will not work (due to NAT).
We should configure ACLs appropriately to avoid this.
The text was updated successfully, but these errors were encountered:
Apparently you can assign a public IP to EC2 instances in the "internal" (private) subnets. Nobody should do this, but it's technically possible.
This will allow sending data to private EC2 instances (e.g. via UDP), but the route back will not work (due to NAT).
We should configure ACLs appropriately to avoid this.
The text was updated successfully, but these errors were encountered: