- Newest
- Most votes
- Most comments
For local development, you could use something as simple as an SSH tunnel to proxy requests to your local machine for development purposes. OpenSSH has this feature built in and there's some useful documentation at https://en.wikibooks.org/wiki/OpenSSH/Cookbook/Tunnels that explains how it works. If you don't want to expose SSH on your EC2 instance to the outside world, you could also use SSH with Session Manager to connect to your instance (see https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-getting-started-enable-ssh-connections.html for more information), or even the new EC2 Instance Connect endpoint feature (https://aws.amazon.com/blogs/compute/secure-connectivity-from-public-to-private-introducing-ec2-instance-connect-endpoint-june-13-2023/).
For a more permanent set up, you'll need to enable some kind of long-lived connectivity between your EC2 instance and then thing you want to proxy connections to. If it's an K8s/EKS instance running inside the same VPC, then it should be possible to create an Ingress in Kubernetes and then make requests to it. If it's not in the same VPC then you need to consider how you might build that connectivity. It could be public internet, it could be via a VPN/Direct Connect.
Relevant content
- asked 6 months ago
- asked a year ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago