Skip to content

Improve CloudFormation documentation:#686

Open
sbrossie wants to merge 1 commit into
v3from
cloudformation-improvements
Open

Improve CloudFormation documentation:#686
sbrossie wants to merge 1 commit into
v3from
cloudformation-improvements

Conversation

@sbrossie

@sbrossie sbrossie commented Jul 1, 2026

Copy link
Copy Markdown
Member
  • Overview — architecture diagram + what the stack creates, at-a-glance prerequisites table
  • Prerequisites (4 numbered, each independently completable) — account/region, VPC/subnets, TLS cert (with warnings about FQDN and empty ARN), key pair
  • Step 1: Subscribe — marketplace flow, noted as one-time-only
  • Step 2: Launch — parameters in 4 groups matching the template UI, with "what to enter" guidance not just a flat list
  • Step 3: Verify — fixed the wrong port (was :9090, now just /users/sign_in)
  • Step 4: DNS (optional) — clarified the difference between ACM validation CNAME and routing CNAME
  • Troubleshooting — four documented error scenarios including the two you hit yourself and the login-via-LB issue

Overview

Screenshot 2026-07-01 at 4 25 45 PM

What You Will Need

Screenshot 2026-07-01 at 4 25 54 PM

Prerequisites

Screenshot 2026-07-01 at 4 31 14 PM

And then the steps, with screenshot for each screen.

- Overview — architecture diagram + what the stack creates, at-a-glance prerequisites table
- Prerequisites (4 numbered, each independently completable) — account/region, VPC/subnets, TLS cert (with warnings about FQDN and empty ARN), key pair
- Step 1: Subscribe — marketplace flow, noted as one-time-only
- Step 2: Launch — parameters in 4 groups matching the template UI, with "what to enter" guidance not just a flat list
- Step 3: Verify — fixed the wrong port (was :9090, now just /users/sign_in)
- Step 4: DNS (optional) — clarified the difference between ACM validation CNAME and routing CNAME
- Troubleshooting — four documented error scenarios including the two you hit yourself and the login-via-LB issue
@sbrossie sbrossie requested a review from vnandwana July 1, 2026 23:32

Common causes: the RDS cluster was not reachable from the EC2 instances (check security groups and subnet routing), or an invalid parameter value was passed to the install script.

---
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants