Amazon EC2 – Bandwidth Limits for Amazon EC2

amazon ec2bandwidth

I have a micro instance on Amazon EC2 cloud.

Also the instance is small and it has vary low CPU and EAM usage but it
generates a lot of content, so it can be considered like a web server
serving small amount of static files (not of a big size) to many clients.

From the technical point of view there is no problems for such instance to handle the load
serving many MBs per seconds.

What I'm considered is if there are limitation of bandwidth by Amazon itself. Many VPS service providers limit the bandwidths to lets say 10MB/s, are there such limits at Amazon and if they are what are they?

I couldn't find any reference.

Best Answer

Remembered that I had bookmarked a similar post a while back, and Cyberx86 posted an excellent answer with benchmark tests :)

Serverfault answer

Edit

From what I've been able to find on the AWS forums - It doesn't seem like the support people from Amazon want to answer that question. Their advice is to test it with an external source: AWS forum post from 2012

Older posts (post1, post2 refer to transfer speeds in coalition to instance size. The 2nd one mentions that the data was a part of the AWS documentation but later it was replaced with stuff about I/O.

small 250 mbps

large 500 mbps

xlarge 1000 mbps

These numbers seem to fit with the benchmarks you can find on google.

So sadly - I don't think you can find transfer speeds on their site anymore.

Related Solutions

Python CGI on Amazon AWS EC2 micro-instance — a how-to!

(Strange post, so hopefully this won't be as strange a reply).

On the subject of security flaws: it is considered general bad practice to store cgi-bin scripts within the document root of the web server. Even the W3C eludes to it under "Are compiled languages such as C safer ..." in their World Wide Web Security FAQ:

Consider the following scenario. For convenience's sake, you've decided to identify CGI scripts to the server using the .cgi extension. Later on, you need to make a small change to an interpreted CGI script. You open it up with the Emacs text editor and modify the script. Unfortunately the edit leaves a backup copy of the script source code lying around in the document tree. Although the remote user can't obtain the source code by fetching the script itself, he can now obtain the backup copy by blindly requesting the URL:
    http://your-site/a/path/your_script.cgi~
(This is another good reason to limit CGI scripts to cgi-bin and to make sure that cgi-bin is separate from the document root.)

This is not as significant a threat as the ability to write a file within the document root. However, an attacker could obtain the source code of the cgi, devise a directed attack against it, and use it as a stepping stone into the server.

To mitigate this, you can add the following lines to the lighttpd.conf (or some variation therein) to direct cgi-bin to a directory separate from the /var/www/lighttpd document root.

$HTTP["url"] =~ "/cgi-bin/" { cgi.assign = ( "" => "" ) }
alias.url = ( "/cgi-bin/" => "/usr/lib/cgi-bin/" )

This requires both the cgi and alias modules for lighttpd.

Amazon ec2 Public DNS not working

If you are using the instance as a public DNS server then you will need to have UDP port 53 open in the instance firewall (if it has one) and in the Security Group that the instance is in.

Go to your AWS management console and Select EC2. Then Under navigation click on Network & Security -> Security Groups

Security Groups

In the Security Groups Pane select the group your instance is in (most likely default)

Select Group

Then In the lower pane click Create new Rule and select DNS

Select DNS

Then click Add Rule followed by `Apply Rule Changes. The EC2 security group will now allow DNS queries to your instance.

Best Answer

Related Solutions

Python CGI on Amazon AWS EC2 micro-instance — a how-to!

Amazon ec2 Public DNS not working

Related Topic