[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

AWS Elastic IP architecture

Subject: AWS Elastic IP architecture
From: morrowc.lists at gmail.com (Christopher Morrow)
Date: Mon, 1 Jun 2015 13:20:57 -0400
In-reply-to: <[email protected]>
References: <[email protected]> <CAA5Ek4c-FRfqgysaenU0_JB9y-Y0_4ZGsX22g3NgcR18nTv89A@mail.gmail.com> <[email protected]> <D190F68B.52B0E%[email protected]> <[email protected]> <CAL9jLaYKwBt8XqjU9ikci1iXYeK-CkUpFx3dSiZtX=d7zKnm0Q@mail.gmail.com> <[email protected]> <CAL9jLabepzMeci=FM4-d8g72eH5QACqJ3Reu_TWGx6yTSyLAwg@mail.gmail.com> <[email protected]> <CAL9jLaZz7XuiWF0X+d_AYCJW1JU4U4A=TM8Qt31RhFXD2u7SNg@mail.gmail.com> <[email protected]>

On Mon, Jun 1, 2015 at 12:21 PM, Hugo Slabbert <hugo at slabnet.com> wrote:
> 2.  Just do it properly the first time around.
>
> I would opt for #2.

sure, so would everyone... but they didn't so... what gets you enough
there to help customers and also doesn't required a forklift of your
running operation?

Follow-Ups:
- AWS Elastic IP architecture
  - From: hugo at slabnet.com (Hugo Slabbert)

References:
- AWS Elastic IP architecture
  - From: owen at delong.com (Owen DeLong)
- AWS Elastic IP architecture
  - From: morrowc.lists at gmail.com (Christopher Morrow)
- AWS Elastic IP architecture
  - From: mpalmer at hezmatt.org (Matt Palmer)
- AWS Elastic IP architecture
  - From: morrowc.lists at gmail.com (Christopher Morrow)
- AWS Elastic IP architecture
  - From: alh-ietf at tndh.net (Tony Hain)
- AWS Elastic IP architecture
  - From: morrowc.lists at gmail.com (Christopher Morrow)
- AWS Elastic IP architecture
  - From: hugo at slabnet.com (Hugo Slabbert)

Prev by Date: AWS Elastic IP architecture
Next by Date: WiFi courses/vendors recommendation
Previous by thread: AWS Elastic IP architecture
Next by thread: AWS Elastic IP architecture
Index(es):
- Date
- Thread