Something went wrong. Try again.
Infrastructure-as-code for running lance.blue
Something went wrong. Try again.
fix(scripts): check for working aws credentials, don't force a profile master
The previous commit made AWS_PROFILE default to lance-blue instead of the hardcoded jmm- name. Forcing any profile turned out to be the wrong layer: an operator may already have working credentials via SSO, an env var, an instance role, or a differently named profile. Drop the AWS_PROFILE export from all five scripts. Add a shared require_aws_credentials guard (scripts/lib/aws.sh) that runs a live sts get-caller-identity and fails with a clear message if it doesn't succeed, so an expired session is caught too, not just a missing one.
Author
permadeath.com Committer Tangled Date (Aug 11, 2026, 5:32 PM UTC) Commit 9036e3e5 9036e3e58ba751cd01d02662f0d4746ead2fc7fa Parent 86aa5d22 86aa5d2243bb69dccf6699e3bf3767f1eda9b67a