Skip to content

feat: FAQ for dns-delegated gbl deployment #710

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
merged 4 commits into from
Oct 18, 2024
Merged

feat: FAQ for dns-delegated gbl deployment #710

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
5b304c7
Deploy `dns-delegated` globally for AWS account consistency
milldr Oct 18, 2024
13c17c5
Add link to global region definition in FAQ network layer
milldr Oct 18, 2024
c69972e
Update link to global region definition in FAQ
milldr Oct 18, 2024
930b329
Update link to global region definition in FAQ
milldr Oct 18, 2024
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
10 changes: 10 additions & 0 deletions docs/layers/network/faq.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,6 +95,16 @@ domains are configured with CNAME (or apex alias) records to point to service do

The architecture does not support other configurations, or non-standard component names.

## Why should the `dns-delegated` component be deployed globally rather than regionally?

The `dns-delegated` component is designed to manage resources across all regions within an AWS account, such as with Route 53 DNS records. Deploying it at the regional level can lead to conflicts because it implies multiple deployments per account, which would cause Terraform to fight for control over the same resources.

Although the `gbl` (“global”) region is not a real AWS region, it is used as a placeholder to signify that resources are meant to be managed globally, not regionally. Deploying `dns-delegated` globally ensures there is a single source of truth for these DNS records within the account.

Deploying this component regionally can cause issues, especially if multiple regional stacks try to manage the same DNS records. This creates an anti-pattern where resources meant to be global are unintentionally duplicated, leading to configuration drift and unexpected behavior.

Please see the [global (default) region](/learn/conventions/#global-default-region) definition for more on `gbl` as a convention.

## How is the EKS network configured?

EKS network is designed with this network and DNS architecture in mind, but is another complex topic. For more, see the
Expand Down
Loading