Repository navigation
Drain 5.60.96.10 and .11 from the prod NAT gateway - #279
Merged
Merged
Conversation
The two addresses move to the tb-prod Stalwart NAT gateways ahead of the prod migration (thunderbird/platform-infrastructure#1600). Prod keeps sending on .8 (primary) and .9. Co-Authored-By: Claude <noreply@anthropic.com>
flamingspaz
marked this pull request as ready for review
November 16, 2026 19:14
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.
The drain is already done in AWS and the stack state already matches. Merging only brings
mainin line; this change is a no-op for the NAT gateway.Removes
5.60.96.10and5.60.96.11fromnat_gateway_secondary_allocation_idsof the prod NAT gatewaynat-09d2add6f5ecd87e0. Prod now sends on.8(primary) and.9. The two addresses were released from the legacy account on 2026-11-16 and will be allocated in tb-prod as the primaries of its Stalwart NAT gateways (thunderbird/platform-infrastructure#1600).What was done
Pulumi previewed the removal as a NatGateway
replace(see below), so the drain was done with the AWS CLI and reconciled afterwards:aws ec2 disassociate-nat-gateway-addressfor both, 2026-11-16 17:35 UTC; both gone at 17:41 UTC.pulumi refresh --targeton onlymailstrom-prod-vpc-natinmzla-services/mailstrom/prod:secondaryAllocationIdsnow holds onlyeipalloc-037682d640024609a(.9), andsecondaryPrivateIpAddressCountdropped from state.Until this merges, an
upfrommainwould try to re-associate two allocation ids that no longer exist.Preview after the refresh
Preview of this branch: the NAT gateway and the route table are
same. What is left is the baseline thatmainalso shows,1 to create, 103 to delete, 214 unchanged:tb_pulumipreview artifact (monitoring andStackAccessPoliciesresources built after the others resolve). Per Ryan Jung, anupdoes not delete them.AmazonSSMManagedInstanceCoreattachment on the Stalwart node role from Add SSM Session Manager access to Stalwart nodes #253, not yet applied to prod. It is unrelated to this change.Open question
Before the drain, this change previewed as a
replaceof the protected NAT gateway, withsecondaryPrivateIpAddressCount: [unknown]. I have not confirmed the cause. Removing further secondaries through Pulumi would likely hit the same thing.Part of thunderbird/platform-infrastructure#1598 (PR 1) and thunderbird/platform-infrastructure#1600.
🤖 Generated with Claude Code