infra-bootstrap: cannot complete a first-time bootstrap as documented #451
Labels
No labels
Compat/Breaking
Component/Enclave-Builder
Component/Infrastructure
Deploy/BYOC
Deploy/Full-managed
Deploy/Self-hosted
Interface/API
Interface/CLI
Interface/Git
Interface/Web
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Status/Abandoned
Status/Blocked
Status/Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
public/platform#451
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Following
infra-bootstrap/README.mdstep 2 on a fresh AWS account, the bootstrap fails.Please add support for the AWS CLI's
aws loginflow (login_sessionin~/.aws/config, token cache in~/.aws/login/) landed inaws-sdk-go-v2/configv1.32.0 (2025-11-19).This is confusing to diagnose because
entrypoint.sh's own precheck(
aws sts get-caller-identity) succeeds — the CLI resolves the session fine — andbecause OpenTofu's built-in S3 backend does support
login_session, so thebackend authenticates while the provider does not.
Further,
entrypoint.shpasses no-var, so it always uses default bucket name which are already taken globally and the README itself says to append the account ID. Plan succeeds fine, and this shows up at the apply phase.anton referenced this issue2026-10-15 20:10:24 +00:00