fix(ci): update EC2 deploy host to current instance IP (3.73.121.74)#43
Merged
Conversation
The aipromo EC2 instance (i-0954843ea04ae47b6) public IP changed to 3.73.121.74; the workflow still pointed at the stale 63.180.21.221, so deploys failed with SSH connection timeout. DNS already resolves to the current IP. Port 22 is open in aipromo-sg and the self-hosted runner holds the deploy key, so this one-line fix restores deploys. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Deploy job was failing with
ssh: connect to host 63.180.21.221 port 22: Connection timed out.Root cause (confirmed via AWS API): the
aipromoinstancei-0954843ea04ae47b6is running but its public IP is now 3.73.121.74 (no Elastic IP → IP changed on a stop/start). The workflowEC2_HOSTwas hardcoded to the stale63.180.21.221. DNS for the site already resolves to the current IP, port 22 is open inaipromo-sg(0.0.0.0/0), and the self-hosted runner holds the deploy key — so only the IP needed updating.Follow-up recommendation: allocate an Elastic IP to stop this recurring (needs a coordinated DNS update).
🤖 Generated with Claude Code