Skip to content

don't use Elastic IP for standalone adhoc servers#7895

Merged
wjordan merged 1 commit into
stagingfrom
adhoc-instance-no-eip
Apr 15, 2016
Merged

don't use Elastic IP for standalone adhoc servers#7895
wjordan merged 1 commit into
stagingfrom
adhoc-instance-no-eip

Conversation

@wjordan

@wjordan wjordan commented Apr 15, 2016

Copy link
Copy Markdown
Contributor

I learned that Elastic IP Address allocations are a scarce resource on AWS - the default limit is only 5 per region(!). According to the documentation, here's the reasoning behind this small limit:

By default, all AWS accounts are limited to 5 EIPs, because public (IPv4) Internet addresses are a scarce public resource. We strongly encourage you to use an Elastic IP address primarily for the ability to remap the address to another instance in the case of instance failure, and to use DNS hostnames for all other inter-node communication.

We can submit a limit increase if needed, but for now since failover isn't necessary for standalone adhoc instances, this PR removes the Elastic IP resource for this server type.

@wjordan wjordan merged commit 72560b2 into staging Apr 15, 2016
@wjordan

wjordan commented Apr 15, 2016

Copy link
Copy Markdown
Contributor Author

(@Hamms just FYI)

@wjordan wjordan deleted the adhoc-instance-no-eip branch November 1, 2016 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants