B2B Integration

Sterling B2B Integration

Come for answers, stay for best practices. All we're missing is you.

 View Only
Back to discussions
Expand all | Collapse all

SSH to EC2 instance (SSP) stopped working after port 21/22 forwarded to internal FTP/SFTP adapter on SSP

  • 1.  SSH to EC2 instance (SSP) stopped working after port 21/22 forwarded to internal FTP/SFTP adapter on SSP

    Posted Mon May 18, 2020 01:06 AM
    Edited by System Admin Wed March 22, 2023 11:51 AM
    Hello All-

    We got a situation when we are doing our AWS migration. 

    As per on-prem, trading partners connect to 21/22 on our firewall and that is natted to internal port 10221/10222 on SSP --> SEAS-->SFG.

    Similarly our cloud was setup expecting traffic on port 10221/10222. Initially when we were trying to reach our EC2 instance where SSP is hosted using default ssh command / key / url per AWS instuctions , we were able to access SSP server.

    But after the port natting on cloud for incoming traffic on 21/22 natted to 10221/10222, now we are not able to ssh to the SSP server as ssh default port is also 22 and its getting forwarded at firewall to 10222. 

    Hence now the trading partners are able to connect but we are not able to connect to SSP server. We did a temp solution to do ssh on port 222 instead of 22 and were able to connect.

    Wanted to check if there are some other solutions to resolve this from the folks who has migrated to AWS .

    Thanks

    ------------------------------
    Pranjit Biswas
    ------------------------------
    #SupplyChain
    #B2BIntegration


Related Content