1 Answer
- Newest
- Most votes
- Most comments
1
Hi, as far as the first question, you could try using the VPC Reachability Analyzer
to find out if there's a permissions or networking issue. You can search for that tool in the console, then click Create and analyze path
. In the form that follows choose Source type as Internet Gateways and choose your internet gateway, Destination type VPC Endpoints and choose your VPC Endpoint that corresponds to your AS2 server, and finally set the destination port as 5080.
Another place I would look at is the Security Group permissions of your VPC.
Finally for Transfer Id, this is an identifier that is associated with a file transfer. All requests that are part of a StartFileTransfer call share a transfer-id.
answered 2 years ago
Relevant content
- asked a year ago
- Accepted Answerasked 2 years ago
- Accepted Answerasked 3 years ago
- asked a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
Thank you. The VPC Reachability analyzer helped with figuring out my problem. I ended up figuring out that while the first server set up had the correct permissions for its subnets and components, the second one didn't. Fixing that and a few other things I found got the two servers up and running.
It also answered another question I had about two servers in different regions sending to each other. Yes, it works.