Created
September 7, 2013 12:54
-
-
Save fbettag/6475338 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Dear Mickey, | |
so i tried the support case link at the bottom, but all i get after authentication is 400 Bad Request on everything i do..... So here it goes. | |
So it was the last week before my vacation, and absolutely nothing worked as normally expected. | |
I must admit that my brain did not really think about having Servers with NAT'ed IPs, which is absolutely great for the manangement perspective of a cloud environments, but it actually "shits" (excuse my french) on the real need for a server. If we wanted NAT, we'd find a way to make it work with DSL or Cable lines.. | |
To be fair, i am against any kind of cloud environment since this trend started a few years back, and i've been nothing short with my assumption that it's all just crap for people who should not operate servers in the first place. So from my professional standpoint, having worked with EC2 for the first time, i can only recommend anyone not using it for anything more than a personal blog. | |
Sorry if that sounds blunt, but i ran a real housing operation for half of a decade, and none of our customers would've paid for NAT'ed IPs or any of the issues that comes from it. | |
To explain the NAT issue, the System we use (http://akka.io) which Game companies, Banks and other Financial institutions use, is designed for real servers. This also means, that the software does some basic "security" and validity checking, thus not allowing for NAT'ed IPs which will have 54.something translated to 172.something. I also tried to bind the external IP on the loopback interface, but the software is just too smart as the inbound socket will always be 172.something. | |
In short, i advised my customer to invest in real Hardware and completely get rid of their amazon account, also because of the US and UK govt's position on Spying on the people of the world. We simply cannot consider EC2 or any services that Amazon provides as privacy policy compliant or simply good enough to be used by us. Sorry. | |
Franz | |
---- | |
Black Belt DevOp, Lift Committer and Director of R&D. | |
Twitter: http://twitter.com/fbettag | |
GitHub: http://github.com/fbettag | |
Personal: http://www.uberblo.gs | |
Business: http://www.wasted.io | |
On Sep 2, 2013, at 10:29 PM, [email protected] wrote: | |
Hi Franz, | |
Since Twitter only allows 140 characters or less I wanted to take a moment to reach out to you briefly regarding your recent tweet about the issues creating an akka cluster: | |
"thanks to #ec2's "superior" design, we cannot create an #akka cluster usable from inside #ec2 to outside. #NAT is so great for servers!" | |
I apologize for any frustration the issues you're experiencing may have caused, but I wanted to let you know that we're here to help. Please reply back to this case at your earliest convenience the details of your use case so that we can assist you. You can do so by clicking the link below my signature. | |
I hope this helps, and we look forward to hearing back from you. | |
Best regards, | |
Mickey N. | |
Amazon Web Services | |
======================================= | |
To contact us again about this case, please return to the AWS Support Center using the following URL: | |
https://aws.amazon.com/support/case?caseId=110887421 | |
*Please note: this e-mail was sent from an address that cannot accept incoming e-mail. Please use the link above if you need to contact us again about this same issue. | |
Amazon Web Services LLC is a subsidiary of Amazon.com, Inc. Amazon.com is a registered trademark of Amazon.com, Inc. | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment