Amazon Web Services

EC2 Instances

As with all aspects of AWS, performance will vary depending on the resources you allocate.  AWS bandwidth is a shared resource.  Larger instance sizes will more often receive a larger share of AWS bandwidth.  c5n instances, where available, will provide faster network speeds than c5 even for smaller sizes.  Below are typical network speeds, assuming your local bandwidth is sufficient.

Instance Type Speed
c5n.large 100 to 400 megabits per second
c5n.xlarge 200 to 600 megabits per second
c5n.2xlarge 400 to 1000 megabits per second
c5n.4xlarge 700 to 2000 megabits per second
c5n.9xlarge 1000+ megabits per second

c5n.2xlarge will provide good performance most of the time.

The c5n.9xlarge instance type will provide the fastest and most consistent speeds, possibly well above 2 gigabits per second, if you have a fast enough network connection.

Regions which lack support for c5n instances can use c5 instead.  If you have a slower internet connection or do not require as much consistency, you may choose c5.large for reduced cost.


Folders do not exist in S3 buckets.

For the purpose of listing remote files, pseudo-folders are displayed by grouping together objects sharing common name prefixes ending in "/".

While pseudo-folders allow you to browse the contents of a bucket as though it were organized into folders, some folder related functions will not work with S3.

  • The "Rename" function cannot be applied to S3 pseudo-folders.
  • The "New Folder" function is silently ignored.

To use ExpeDat Desktop to upload objects into a pseudo-path that does not yet exist, type the path in the "Remote Prefix" field prior to clicking "Send".

Listing a bucket containing many objects may take a long time, even if they are grouped into pseudo-folders.


Data cannot move faster than your underlying network and storage hardware.

The EC2 instance hosting CloudDat must be in the same availability region as the S3 bucket.  Accessing a bucket in a different region than the gateway instance would severely limit performance.

Because each transaction must establish communication between the EC2 instance and S3, it may take several seconds for each action to start.  If you are storing large numbers of files in S3, consider packaging related files as a ZIP or TAR archive, rather than storing each file as a separate object.  Remember that S3 objects are not files and you must plan your workflow around S3's limitations.


Clients display the progress of uploading data to the CloudDat instance.  It may take several seconds more for the data to then finish being written into S3.  There may be times when S3 takes up to a minute to confirm receipt of the data.

Next: Support >

Free Trial

Try before you buy

We're so confident in our technology that all of our end-user products are available to try - no strings attached.

Request Trial