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
I started a session with something like this:
aws ssm start-session \ --target instance-id \ --document-name AWS-StartPortForwardingSessionToRemoteHost \ --parameters '{"host":["mydb.example.us-east-2.rds.amazonaws.com"],"portNumber":["3306"], "localPortNumber":["3306"]}'
And the tcp connection only binds to 127.0.0.1 instead of 0.0.0.0.
127.0.0.1
0.0.0.0
sh-4.2# netstat -nltp | grep session tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 10/session-manager-
What I'm trying to achieve is to connect this session from another docker container.
The text was updated successfully, but these errors were encountered:
oh, already an issue here.
Sorry, something went wrong.
No branches or pull requests
I started a session with something like this:
aws ssm start-session \ --target instance-id \ --document-name AWS-StartPortForwardingSessionToRemoteHost \ --parameters '{"host":["mydb.example.us-east-2.rds.amazonaws.com"],"portNumber":["3306"], "localPortNumber":["3306"]}'
And the tcp connection only binds to
127.0.0.1
instead of0.0.0.0
.What I'm trying to achieve is to connect this session from another docker container.
The text was updated successfully, but these errors were encountered: