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.
Before anyone well actually’s me. Yes I know you can also route S3 via AWS internal network with VPC Endpoints between AWS services.