docs: use CNAME for Connect DNS configuration#4750
Open
Conversation
CNAME works universally regardless of AWS account boundaries, unlike Route 53 alias A records which are account-specific. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #4750 +/- ##
=======================================
Coverage 44.32% 44.32%
=======================================
Files 813 813
Lines 32734 32734
Branches 5722 5722
=======================================
Hits 14509 14509
Misses 16221 16221
Partials 2004 2004
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
sir-sigurd
reviewed
Mar 4, 2026
Member
sir-sigurd
left a comment
There was a problem hiding this comment.
- I think alias is preferred when you use Route53, check that claim with AI if so let's mention both
- maybe we should cross-reference with https://docs.quilt.bio/quilt-platform-administrator/installation#cnames?
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
CNAMEpointing toConnectLoadBalancerDNSNameTest plan
🤖 Generated with Claude Code
Greptile Summary
This PR simplifies the DNS configuration documentation for Quilt Connect Server by replacing the Route 53-specific alias A record setup (which required both
ConnectLoadBalancerDNSNameandConnectLoadBalancerCanonicalHostedZoneID) with a single, universally compatibleCNAMErecord pointing toConnectLoadBalancerDNSName.Key changes:
A/alias, alias target, hosted zone ID fields)CNAMEpointing toConnectLoadBalancerDNSNameConnectHostoutput reference is preservedConfidence Score: 5/5
<stack-name>-connect.<your-domain>) is always a subdomain, so the CNAME restriction on zone-apex records is not a concern here.Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A["Deploy Quilt Stack\nwith ConnectAllowedHosts set"] --> B["CloudFormation Outputs Available:\n• ConnectLoadBalancerDNSName\n• ConnectHost"] B --> C["Create DNS CNAME Record\n(any DNS provider / any AWS account)"] C --> D["CNAME: <stack>-connect.<domain>\n→ ConnectLoadBalancerDNSName"] D --> E["Connect Server reachable at\nConnectHost URL"] E --> F["AI clients (Claude.ai, etc.)\ncan integrate via MCP"]Last reviewed commit: c3d6b50