[180457] in North American Network Operators' Group
Re: AWS Elastic IP architecture
daemon@ATHENA.MIT.EDU (Christopher Morrow)
Wed Jun 3 16:25:01 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <4316CE97-FC2E-4FDF-BB0D-B20E756AE64D@delong.com>
Date: Wed, 3 Jun 2015 16:24:59 -0400
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Owen DeLong <owen@delong.com>
Cc: nanog list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Wed, Jun 3, 2015 at 7:56 AM, Owen DeLong <owen@delong.com> wrote:
> For example, let=E2=80=99s say you have 20 machines for whom you want to =
allow inbound SSH access. In the IPv4 world, with NAT, you have to configur=
e an individual port mapping for each machine and you have to either config=
ure all of the SSH clients, or, specify the particular port for the machine=
you want to get to on the command line.
in the original case in question the fact that there's nat happeng
isn't material... so all of this discussion of NAT is a red herring,
right? the user of AWS services cares not that 'nat is happening',
because they can simply RESTful up a VM instance and ssh into it in
~30 seconds, no config required.
let's skip all NAT discussions on this topic from here on out, yes?