Skip to content

Fix CloudShell VPC bootstrap instructions #57

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jaydreyer merged 1 commit into from
Aug 14, 2026
Merged

Fix CloudShell VPC bootstrap instructions #57

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 12 additions & 5 deletions docs/aws-deployment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,11 +36,18 @@ RDS-managed administrator credential out of ECS:
1. Create an AWS CloudShell VPC environment in one Terraform output `public_subnet_ids` subnet and
attach the Terraform output `task_security_group_id`. Delete that CloudShell VPC environment
after bootstrap. This gives the short-lived operator shell the same database network path as
the application without making RDS public. After entering that VPC environment, use the
CloudShell **Actions → Upload file** control to upload the reviewed
`scripts/bootstrap_database_roles.sql`; do not depend on internet access or persistent storage.
Compare `sha256sum scripts/bootstrap_database_roles.sql` there with the checksum from the
reviewed `main` checkout before executing it.
the application without making RDS public. CloudShell does not provide its upload/download
controls inside VPC environments, and this public-subnet shell has no public IP or NAT path.
Create the reviewed file interactively instead:

```bash
mkdir -p scripts
nano scripts/bootstrap_database_roles.sql
```

Paste the exact contents from the reviewed `main` checkout, save, and exit. Do not depend on
internet access or persistent storage. Compare `sha256sum scripts/bootstrap_database_roles.sql`
there with the checksum from the reviewed `main` checkout before executing it.
2. In CloudShell, confirm the account and retrieve the non-secret outputs:

```bash
Expand Down
Loading