don't use Elastic IP for standalone adhoc servers#7895
Merged
Conversation
Contributor
Author
|
(@Hamms just FYI) |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
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.