<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Using Amazon EC2 public IP address inside EC2 network</title>
	<atom:link href="http://www.cloudiquity.com/2009/02/using-amazon-ec2-public-ip-address-inside-ec2-network/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cloudiquity.com/2009/02/using-amazon-ec2-public-ip-address-inside-ec2-network/</link>
	<description>A blog about Cloud, Grid and HPC technologies</description>
	<lastBuildDate>Mon, 30 Jan 2012 02:46:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Dan Moore! &#187; Tips: Deploying a web application to the cloud</title>
		<link>http://www.cloudiquity.com/2009/02/using-amazon-ec2-public-ip-address-inside-ec2-network/comment-page-1/#comment-367</link>
		<dc:creator>Dan Moore! &#187; Tips: Deploying a web application to the cloud</dc:creator>
		<pubDate>Thu, 29 Oct 2009 20:29:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.cloudiquity.com/?p=137#comment-367</guid>
		<description>[...] files around, or a database connection), prefer the internal DNS. It looks like there are some performance benefits, but there are definitely pricing benefits. &#8220;Always use the internal address when you are [...]</description>
		<content:encoded><![CDATA[<p>[...] files around, or a database connection), prefer the internal DNS. It looks like there are some performance benefits, but there are definitely pricing benefits. &#8220;Always use the internal address when you are [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eli</title>
		<link>http://www.cloudiquity.com/2009/02/using-amazon-ec2-public-ip-address-inside-ec2-network/comment-page-1/#comment-227</link>
		<dc:creator>eli</dc:creator>
		<pubDate>Fri, 12 Jun 2009 21:15:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.cloudiquity.com/?p=137#comment-227</guid>
		<description>Take a look at this: http://alestic.com/2009/06/ec2-elastic-ip-internal</description>
		<content:encoded><![CDATA[<p>Take a look at this: <a href="http://alestic.com/2009/06/ec2-elastic-ip-internal" rel="nofollow">http://alestic.com/2009/06/ec2-elastic-ip-internal</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dmitriy</title>
		<link>http://www.cloudiquity.com/2009/02/using-amazon-ec2-public-ip-address-inside-ec2-network/comment-page-1/#comment-21</link>
		<dc:creator>Dmitriy</dc:creator>
		<pubDate>Fri, 13 Feb 2009 16:50:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.cloudiquity.com/?p=137#comment-21</guid>
		<description>Thanks for doing this research and thanks for publishing the results. I apparently had some misconceptions about how certain traffic was billed due to lack of RTFM, and your post helped me straighten it out.

Re 2 wishes from Jana that you expressed in the post, please note that my employer (&lt;a href=&quot;http://cohesiveft.com&quot; rel=&quot;nofollow&quot;&gt;CohesiveFT&lt;/a&gt;) offers a solution called VPN-Cubed that can give you static internal IPs and can allow you to essentially block absolutely all ports in a security group. In other words, it allows your EC2 instances to run with absolutely no ingress connectivity (egress is always allowed). You can read more about VPN-Cubed at &lt;a href=&quot;http://cohesiveft.com/vpncubed/&quot; rel=&quot;nofollow&quot;&gt;http://cohesiveft.com/vpncubed/&lt;/a&gt;.

Cheers,
Dmitriy</description>
		<content:encoded><![CDATA[<p>Thanks for doing this research and thanks for publishing the results. I apparently had some misconceptions about how certain traffic was billed due to lack of RTFM, and your post helped me straighten it out.</p>
<p>Re 2 wishes from Jana that you expressed in the post, please note that my employer (<a href="http://cohesiveft.com" rel="nofollow">CohesiveFT</a>) offers a solution called VPN-Cubed that can give you static internal IPs and can allow you to essentially block absolutely all ports in a security group. In other words, it allows your EC2 instances to run with absolutely no ingress connectivity (egress is always allowed). You can read more about VPN-Cubed at <a href="http://cohesiveft.com/vpncubed/" rel="nofollow">http://cohesiveft.com/vpncubed/</a>.</p>
<p>Cheers,<br />
Dmitriy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cloud Droplets #59 - Cloudveland &#124; IT Management and Cloud Blog</title>
		<link>http://www.cloudiquity.com/2009/02/using-amazon-ec2-public-ip-address-inside-ec2-network/comment-page-1/#comment-20</link>
		<dc:creator>Cloud Droplets #59 - Cloudveland &#124; IT Management and Cloud Blog</dc:creator>
		<pubDate>Fri, 13 Feb 2009 12:49:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.cloudiquity.com/?p=137#comment-20</guid>
		<description>[...] EC2 and IP addresses [...]</description>
		<content:encoded><![CDATA[<p>[...] EC2 and IP addresses [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

