v2.2.0
Reorganize AWS Organization and account deployment steps Dan Miller (@milldr) (#843)
what
- Move AWS Organization creation, configuration, and account quota increase steps from Deploy Accounts to Prepare AWS Organization as ClickOps procedures
- Rename "Deploy the AWS Organization" step to "Import the AWS Organization" to clarify the step imports an existing organization into Terraform
- Add "Validate Prerequisites for Account Deployment" step to Deploy Accounts to ensure all prerequisites are met before starting deployment
- Simplify Deploy Accounts page by removing ClickOps configuration steps, focusing only on Terraform workflows
why
- Improves user experience by separating manual setup steps from infrastructure-as-code deployment
- Creates a clearer workflow: complete all manual AWS Organization setup first, then deploy accounts via Terraform
- Reduces confusion about what steps belong in which guide based on whether they're ClickOps or Terraform-based
references
- Updates documentation for AWS Organization and account deployment workflow
♻️ fix: remove unnecessary RunsOn-specific TGW routes and attachments Cloud Posse Bot (CI/CD) (@cloudpossebot) (#857)
[!IMPORTANT]
Do not merge this PR manually. It will be handled automatically by the cloudposse/refarch-scaffold repository.
Instead, please review the changes and merge https://github.com/cloudposse/refarch-scaffold/pull/837
What
This pull request was created by the 🚀 Generate Examples workflow in the cloudposse/refarch-scaffold repository. This PR updates this documentation repo with the latest configuration for the Cloud Posse reference architecture.
Why
This documentation repo is used for reference purposes and should have the latest configuration.
References
Internal PR: https://github.com/cloudposse/refarch-scaffold/pull/837
♻️ fix: use gbl region for iam-role/gitops in atmos-pro workflow Cloud Posse Bot (CI/CD) (@cloudpossebot) (#859)
[!IMPORTANT]
Do not merge this PR manually. It will be handled automatically by the cloudposse/refarch-scaffold repository.
Instead, please review the changes and merge https://github.com/cloudposse/refarch-scaffold/pull/846
What
This pull request was created by the 🚀 Generate Examples workflow in the cloudposse/refarch-scaffold repository. This PR updates this documentation repo with the latest configuration for the Cloud Posse reference architecture.
Why
This documentation repo is used for reference purposes and should have the latest configuration.
References
Internal PR: https://github.com/cloudposse/refarch-scaffold/pull/846
docs: Add setup guidance for SuperAdmin auth, account IDs, and placeholders Dan Miller (@milldr) (#852)
what
- Added SuperAdmin Atmos Auth configuration step during cold start setup
- Added account ID placeholder replacement step after deploying accounts
- Added info box explaining all placeholder values in reference architecture
why
These additions provide users with clear, step-by-step guidance on three critical parts of the cold start journey that were previously missing or unclear:
- SuperAdmin Authentication: Users can now configure Atmos Auth with SuperAdmin credentials to run deployment commands during cold start
- Account ID Updates: After accounts are created, users need to replace placeholder account IDs in their configuration with actual values
- Placeholder Awareness: A general info box helps users understand what placeholder values exist in the reference architecture and when to replace them
references
Addresses the need for comprehensive setup guidance in the reference architecture cold start process.
Add RunsOn license acquisition step to setup guide Dan Miller (@milldr) (#855)
what
- Added license acquisition as the first step in the RunsOn setup guide
- Included pricing table with Demo, Commercial, and Sponsorship license options
- Recommend Commercial License ($300/year) for production deployments
- Added guidance for Cloud Posse customers to share license via 1Password
- Updated quick start checklist to include license acquisition
why
- Users need a RunsOn license before they can deploy the infrastructure
- Documenting this upfront prevents wasted setup time and confusion
- Clear licensing recommendations help users choose the right option
