By using AWS re:Post, you agree to the Terms of Use

Low transfer rates


Hi, I run EC2 in Ireland region with GoAnyhwere Application that receives SFTP traffic on 922 port. Normally, on prem, I receive constant 5-10Mbps inbound, but in AWS instance I receive 1mbs and constant drops to 0mbps. The instance is c5.xlarge. Is there anyone who faces similar anomaly ? The same anomaly happens when I transfer to the attached S3

1 Answer

Hello valued AWS customer,

After reviewing your post I understand that you are experiencing abnormal performance issues on your EC2 instance while running the GoAnywhere application and making transfers.

First, I recommend that you look at the CPU/memory utilization of your instance; refer to this article: If the CPU or memory utilization is maxing out at any given time, it would be best to upgrade the instance type.

Given that you are running the GoAnywhere application that supports managed file transfers, your instance would be better optimized using a I/O centric instance type.

Storage optimized instance are designed for workloads that require high, sequential read and write access to very large data sets on local storage. They are optimized to deliver tens of thousands of low-latency, random I/O operations per second (IOPS) to applications. The following link will provide insight into the storage optimized instances:

Another issue that could be affecting the transfer performance is the network bandwidth. Each EC2 instance has a maximum bandwidth based on the instance type and size, so upgrading those features may help with performance. I recommend doing all necessary troubleshooting to boil the problem down to either the instance or the network. For network troubleshooting, you can run throughput test using iperf3 to get network throughput overview, refer to this article for using IPerf to discover issues that may be related to throughput and speed. This document has a list of iperf commands that you can run to check - On the instance side, it would be good to stop and start the instance. This would recover if this issue was caused by underlying hardware as stop/start would replace the underlying hardware. Lastly, you can check CloudWatch metrics for the instance to determine if the input/output is maxing out.

Please refer to the following links:

If the problem persists I recommend creating a support case with AWS to dive deeper into the problem. How to create a support case will me linked below:

Thank you for taking the time to reach out. Please respond for any further questions!

answered 3 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions