AWS EC2弹性IP的带宽使用量和收费 [英] AWS EC2 Elastic IPs bandwidth usage and charges

问题描述

我有一个关于弹性的IP和其充电的小问题。一些博客说，弹性IP将使用

带宽收取您

  

    

弹性IP地址负责通过带宽并有一个小时的价格     当它们不连接到一个正在运行的实例

  

     

从   <一href="http://things.zarate.org/scaling-a-single-ec2-instance-and-downsizing">http://things.zarate.org/scaling-a-single-ec2-instance-and-downsizing

从我的理解在阅读一些博客和文档，你将只收取如果您使用弹性IP地址的通信的实例和如果你有弹性的IP站在你的账户有闲置而不被关联到您的实例

  

    

如果您在使用公共或弹性IP实例之间进行通信     你付出区域的数据传输在同一区域甚至解决     率（每GB 0.01 $ /输出）。

  

     

从   <一href="http://www.cloudiquity.com/2009/02/using-amazon-ec2-public-ip-address-inside-ec2-network/">http://www.cloudiquity.com/2009/02/using-amazon-ec2-public-ip-address-inside-ec2-network/

请参阅AWS的计算器屏幕截图 - > <一个href="http://shareimage.org/images/lzjj3eull2ux0lo663fr.png">http://shareimage.org/images/lzjj3eull2ux0lo663fr.png

所以我的困惑是在零件AWS费任何种类的流量请求是否（用我的浏览器，SSH）使用弹性IP地址？

因此​​，如果例如：我SSH-ED，而不是像EC2-XXX-XXX-XXX-xxx.compute-1.amazonaws给出的公共DNS名称使用弹性IP地址（例如8.8.8.8）我的实例。 COM，将这个带宽登记为简单的带宽/出使用或公共/弹性IP带宽？

感谢

解决方案

您应该分离的弹性IP地址充一数据传输费用的问题，只要他们是完全相互独立的：

弹性IP地址

分配和使用一个<一href="http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/using-instance-addressing.html#using-instance-addressing-eips">Elastic 每个实例的IP地址基本上是免费的，除了如果在弹性IP地址的当前未使用的实例，见的弹性IP地址<关​​联/ EM>的网页。亚马逊EC2定价：

  

  
• $ 0.00包装与正在运行的实例相关联的一个弹性IP地址
  
• $为0.005元，每小时的运行实例上按比例相关的附加弹性IP地址
  
• $为0.005元按比例基础上，每小时的运行实例不关联的弹性IP地址
  
• $ 0.00包装每个弹性IP地址重映射的第100每个月重新映射
  

• $ 0.10元弹性IP地址重映射了100元不等的附加重映射

       

  [重点煤矿] 的

  

这种方法的基本原理在各自的常见问题进行说明<一href="http://aws.amazon.com/ec2/faqs/#Why_am_I_charged_when_my_Elastic_IP_address_is_not_associated_with_an_instance">Why我在充电时，我的弹性IP地址与实例相关联的：

  

为了帮助确保我们的客户有效地使用弹性IP地址，我们施加一个小的每小时收费为每一个地址时，它没有关联到一个正在运行的实例。

数据传输

再次在关键方面是在网页。亚马逊EC2定价数据传输的解释>（以及一些常见问题进行详细说明）：

您主要是支付的互联网数据传输的，即中的传输的数据和走出去亚马逊EC2 的，具体不包括以下内容：

  

目前亚马逊EC2和其他Amazon之间没有数据传输费用   亚马逊EC2美西之间的同一区域（即在Web服务   和Amazon S3在美国西部）。亚马逊EC2之间的数据传输   位于不同的可用区域，在同一区域的实例   将收取区域数据传输。 AWS之间传输数据   不同地区的服务将被指控为互联网数据   转移在转印的两侧。

买者

重要警告要注意的确实遵循下面这句话虽然：

  

公共及弹性IP和弹性负载均衡数据传输

     

  
• $ 0.01元GB /输出 - 如果您选择使用您的公共或弹性IP地址或亚马逊的内部弹性负载均衡沟通   EC2网络中，你会付出区域的数据传输速率，即使   实例在同一个可用区。对于内部的数据传输   同样的可用性区域，就可以轻松避免这种收费（并获得   更好的网络性能），通过使用专用IP时   可能的。
  

解决方法

没有提到在上述段落是AWS的DNS基础设施的重要和非常有用的功能，虽然，看到<一href="http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html#concepts-public-addresses">Public IP地址和外部DNS主机名：

  

我们提供具有与外部公网IP地址，每个实例   DNS主机名。我们决心外部DNS主机名的公网IP   实例的地址实例的网络之外，并   实例从的网络内的专用IP地址   实例。

也就是说，它是解决公共DNS（如 ec2-xxx-xxx-xxx-xxx.compute-1.amazonaws.com ）的专用IP地址的，当你在Amazon EC2网络中使用它，并给的公共或弹性IP地址时，亚马逊EC2网络之外使用它的。像这样，你得到免费的可用性区数据传输的和减免费用的区域数据传输的自动，如他们正在积极地运用他们的奉劝的始终使用，当你的Amazon EC2实例之间进行通信[这]确保您的网络流量遵循最高的带宽，最低的成本，并通过我们的网络延迟最低的路径的内部地址。

这显然是行不通的，如果你直接使用IP地址（即没有DNS），它是这样，通常最好避免了这样那样的原因在EC2的情况下。

I have a little questions regarding Elastic IPs and its charge. Some blogs says that Elastic IP will charge you by the bandwidth you use

Elastic IP addresses charge by bandwidth and have an hourly price when they are not attached to a running instance

From http://things.zarate.org/scaling-a-single-ec2-instance-and-downsizing

From my understanding after reading some blogs and the documentation, you will only be charged if you use the elastic IPs in communicating between instances and if you have elastic IPs standing there idle on your account without being associated to your instance

If you communicate between instances using public or elastic IP address even in the same region you pay regional data transfer rates(0.01$ per GB in/out).

From http://www.cloudiquity.com/2009/02/using-amazon-ec2-public-ip-address-inside-ec2-network/

See AWS calculator screenshot -> http://shareimage.org/images/lzjj3eull2ux0lo663fr.png

So my confusion is on the part whether AWS charge for any kinds of traffic requests (using my browser, SSH) using the elastic IPs?

So if for example: I ssh-ed to my instances using the elastic IPs (For example 8.8.8.8) instead of the public dns name given like ec2-xxx-xxx-xxx-xxx.compute-1.amazonaws.com, will this bandwidth registered as simple bandwidth in/out usage or the public/elastic IP bandwidth?

Thanks

解决方案

You should decouple the data transfer charge question from the Elastic IP address charge one, insofar they are completely independent from each other:

Elastic IP addresses

Allocating and using one Elastic IP addresses per instance is basically free, except if the Elastic IP address is not currently associated with an instance, see section Elastic IP Addresses on page Amazon EC2 Pricing:

• $0.00 for one Elastic IP address associated with a running instance
• $0.005 per additional Elastic IP address associated with a running instance per hour on a pro rata basis
• $0.005 per Elastic IP address not associated with a running instance per hour on a pro rata basis
• $0.00 per Elastic IP address remap for the first 100 remaps per month

• $0.10 per Elastic IP address remap for additional remaps over 100 per month

  [emphasis mine]

The rationale behind this approach is explained in the respective FAQ Why am I charged when my Elastic IP address is not associated with an instance?:

In order to help ensure our customers are efficiently using the Elastic IP addresses, we impose a small hourly charge for each address when it is not associated to a running instance.

Data Transfer

Again, the key aspect is explained in section Data Transfer on page Amazon EC2 Pricing (and detailed by some FAQs):

You primarily pay for Internet Data Transfer, i.e. data transferred "in" and "out" of Amazon EC2, which specifically excludes the following:

There is no Data Transfer charge between Amazon EC2 and other Amazon Web Services within the same region (i.e. between Amazon EC2 US West and Amazon S3 in US West). Data transferred between Amazon EC2 instances located in different Availability Zones in the same Region will be charged Regional Data Transfer. Data transferred between AWS services in different regions will be charged as Internet Data Transfer on both sides of the transfer.

Caveat

The important caveat to be aware of indeed follows below that statement though:

Public and Elastic IP and Elastic Load Balancing Data Transfer

• $0.01 per GB in/out – If you choose to communicate using your Public or Elastic IP address or Elastic Load Balancer inside of the Amazon EC2 network, you’ll pay Regional Data Transfer rates even if the instances are in the same Availability Zone. For data transfer within the same Availability Zone, you can easily avoid this charge (and get better network performance) by using your private IP whenever possible.

Remedy

Not mentioned in the aforementioned paragraph is an important and quite helpful feature of the AWS DNS infrastructure though, see Public IP Addresses and External DNS Hostnames:

We provide each instance that has a public IP address with an external DNS hostname. We resolve an external DNS hostname to the public IP address of the instance outside the network of the instance, and to the private IP address of the instance from within the network of the instance.

That is, it's resolving the public DNS (e.g. ec2-xxx-xxx-xxx-xxx.compute-1.amazonaws.com) to the Private IP address when you are using it inside the Amazon EC2 network, and to the Public or Elastic IP address when using it outside the Amazon EC2 network. Like so you get the free Availability Zone Data Transfer and reduced charge Regional Data Transfer automatically, e.g. they are actively applying their advise to Always use the internal address when you are communicating between Amazon EC2 instances [which] ensures that your network traffic follows the highest bandwidth, lowest cost, and lowest latency path through our network.

This obviously doesn't work, if you are using the IP addresses directly (i.e. without DNS), which is thus usually best avoided for this and other reasons in the context of EC2.

这篇关于AWS EC2弹性IP的带宽使用量和收费的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！