aws / aws/session-manager-plugin

Accessing forwarded port from Docker container

Open
#14 14 comments 14 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
320
Forks
97
PR merge metrics
No merged PRs in 30d

Description

Hello,

I am using the `PortForwardingSession` to access some services in our AWS account. When using it locally everything works fine and I have access via `localhost:`. However, inside a docker container I'm not able to access the same port. At the same time I am able to access a different port with a local web server without any issues. So the problem only seems to exist in combination of SSM and Docker.
When using `nmap` from inside the container it also shows the port used for the forwarding session as closed.

```
docker --version -> 20.10.8
session-manager-plugin --version -> 1.2.245.0
```
running on Ubuntu 20.04.3 LTS

Do you know any reason why the SSM port behaves differently in comparison to e.g. a webserver.

Many Thanks!

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.