We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
We are setting up ssh tunnel via ssm agent in bastion host to connect resource in private subnet. With ssh tunnel, from browser we configure socks5 to access private resource, however we could also access to unexpected page. We would like to control from browser only some whitelist domains are allowed via squid proxy similar this one for whole server by configure proxy in /etc/environment https://aws.amazon.com/blogs/networking-and-content-delivery/providing-controlled-internet-access-through-centralised-proxy-servers-using-aws-fargate-and-privatelink/.
We follow the guide https://docs.aws.amazon.com/systems-manager/latest/userguide/configure-proxy-ssm-agent.html to configure proxy for ssm however from browser, we still access unexpected pages.
Any suggestion to resolve this issue would be very much appreciated!
Thanks!
The text was updated successfully, but these errors were encountered:
Can you elaborate to the nature of the "unexpected pages", are these resources within the private subnet that you own or is it in the public internet?
Sorry, something went wrong.
No branches or pull requests
Hi,
We are setting up ssh tunnel via ssm agent in bastion host to connect resource in private subnet. With ssh tunnel, from browser we configure socks5 to access private resource, however we could also access to unexpected page. We would like to control from browser only some whitelist domains are allowed via squid proxy similar this one for whole server by configure proxy in /etc/environment https://aws.amazon.com/blogs/networking-and-content-delivery/providing-controlled-internet-access-through-centralised-proxy-servers-using-aws-fargate-and-privatelink/.
We follow the guide https://docs.aws.amazon.com/systems-manager/latest/userguide/configure-proxy-ssm-agent.html to configure proxy for ssm however from browser, we still access unexpected pages.
Any suggestion to resolve this issue would be very much appreciated!
Thanks!
The text was updated successfully, but these errors were encountered: