Drop EIP #96
Merged
Drop EIP #96
Conversation
This file contains 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
mathcolo
requested review from
idreyn,
vickymmcd,
austinjpaul and
nathan-weinberg
as code owners
|
Should we just leave it if it isn't eliminating any costs? Not sure about the pros/cons here forgive me 😅 |
|
That's fine I can help :) This PR removes the static IP from the instance, so rebuilds would result in a new public IP. (NTT is already configured this way) Ultimately we can eliminate the upcoming IPv4 address cost by eliminating public IPv4 addresses with an Instance Endpoint. It would require a bit of work to get that hooked up to the GitHub action and what not, so getting rid of the static EIP is a step in that direction that at least prevents us from getting accustomed to sshing in directly via the static IP. |
nathan-weinberg
approved these changes
Oct 24, 2023
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.
We ended up not having to provide MBTA with an IP last year, so revert #64
Note that this does not eliminate costs from https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/