scripts: one-time AWS access wizard + first-deploy bootstrap - #63
Merged
Conversation
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.
The gap between "everything LocalStack-side is proven" and a real deploy is AWS admin credentials — which live only in the console. Two scripts close the loop:
scripts/aws/one-time-aws-admin.sh(wizard, run in a terminal): walks the console to create a throwawaytemp-bootstrapadmin user, captures its keys into anawsprofile[profile bootstrap], verifies the account matches772889137569, captures the budget alarm email intosecrets.ALERT_EMAIL(the last unfed value referenced by cd.yml), and leaves a delete-me reminder.scripts/aws/first-deploy.sh(agent-driven, uses the profile): CDK bootstrap both regions →webdev-network+webdev-oidc(mints the GitHub OIDC provider +webdev-deploy-build/productionroles that CI probes proved missing) → ACM cert forwebdevstudio.resonance.io.vnwith Route53 DNS validation (waits for ISSUED) →webdev-waf→ writes/webdev/cloudfront/cert-arn+/webdev/cloudfront/waf-arnSSM params the prod stack reads → stops before the release tag, which stays a human decision.Idempotent; re-run after any failure. After it finishes:
gh workflow run aws-probe.ymlshould go green, thenv0.1.1deploys for real. Keys deleted afterwards. No secrets in the repo; nothing in CI changes.