News for hackers. Stuff that matters.
Re:Down the rabbit hole: Implementing SSH port forwarding ov... by nicornk on Wednesday February 12, 2025 @06:21AM (#43024240)
If you just want to enable ssh to ec2 instances (through SSM) using ssh i-… you can add the following lines to your ssh config

https://gist.github.com/nicornk/5d2c0cd02179f9b46cc7df459af0...

host i-* IdentityFile ~/.ssh/id_rsa TCPKeepAlive yes ServerAliveInterval 120 User ec2-user ProxyCommand sh -c "aws ec2 start-instances --instance-ids %h ; aws ec2 wait instance-running --instance-ids %h ; aws ec2-instance-connect send-ssh-public-key --instance-id %h --instance-os-user %r --ssh-public-key 'file://~/.ssh/id_rsa.pub' --availability-zone $(aws ec2 describe-instances --instance-ids %h --query 'Reservations[0].Instances[0].Placement.AvailabilityZone') ; aws ssm start-session --target %h --document-name AWS-StartSSHSession --parameters 'portNumber=%p'"

This will also allow VSCode remote development.

Re:Down the rabbit hole: Implementing SSH port forwarding ov... by Galanwe on Wednesday February 12, 2025 @10:08AM (#43026111)
My variation is to use a custom script as `ProxyCommand` that resolves private route53 DNS names to instance ids, because remembering instance IDs is insane.
Re:Down the rabbit hole: Implementing SSH port forwarding ov... by smackeyacky on Wednesday February 12, 2025 @10:37AM (#43026398)
Mine is to run a Tailscale node on a tiny ec2 instance. Not only enabling ssh but direct access to database instances, s3 buckets that are blocked from public access etc
Re:Down the rabbit hole: Implementing SSH port forwarding ov... by scarface_74 on Wednesday February 12, 2025 @11:30AM (#43026919)
How are S3 buckets blocked from public access? I mean I know there is literally a “Block public access” feature that keeps S3 buckets from being read or written by unauthenticated users. But as far as I know without some really weird bucket ACLs you can still access S3 buckets if you have the IAM credentials.

Before anyone well actually’s me. Yes I know you can also route S3 via AWS internal network with VPC Endpoints between AWS services.

Re:Down the rabbit hole: Implementing SSH port forwarding ov... by Galanwe on Wednesday February 12, 2025 @02:07PM (#43028581)
You essentially add a policy that limits the access to only come from your VPC endpoint.
Re:Down the rabbit hole: Implementing SSH port forwarding ov... by nijave on Wednesday February 12, 2025 @04:20PM (#43029893)
In general, condition keys

https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_p...

And https://docs.aws.amazon.com/service-authorization/latest/ref...

Specifically the vpce one as the other poster mentioned but there's other like IP limits

Another way is an IdP that supports network or device rules. For instance, Cloudflare Access and Okta you can add policies where they'll only let you auth if you meet device or network requirements which achieved the same thing

Re:Down the rabbit hole: Implementing SSH port forwarding ov... by Galanwe on Thursday February 13, 2025 @02:04AM (#43033426)
> Specifically the vpce one as the other poster mentioned but there's other like IP limits

IPs don't cut it to prevent public access. I can create my own personal AWS account, with the private IP I want, and use the credentials from there. There's really just VPC endpoints AFAIK.

Re:Down the rabbit hole: Implementing SSH port forwarding ov... by icedchai on Wednesday February 12, 2025 @06:56PM (#43031129)
I run an EC2 instance with SSM enabled. I then use the AWS CLI to port forward into the 'private' database instance or whatever from my desktop. The nice thing about this is it's all native AWS stuff, no need for 3rd party packages, etc.