https://github.com/ekgf/terraform-aws-dns
Configure AWS Route53 for running an EKG (or Digital Twin so you will) supporting multiple environments
https://github.com/ekgf/terraform-aws-dns
Last synced: 3 months ago
JSON representation
Configure AWS Route53 for running an EKG (or Digital Twin so you will) supporting multiple environments
- Host: GitHub
- URL: https://github.com/ekgf/terraform-aws-dns
- Owner: EKGF
- License: mit
- Created: 2023-11-12T12:48:10.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2026-01-16T01:40:00.000Z (5 months ago)
- Last Synced: 2026-02-08T01:52:54.395Z (4 months ago)
- Language: HCL
- Size: 5.86 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
- Codeowners: .github/CODEOWNERS
Awesome Lists containing this project
README
# Terraform AWS DNS
Deal with all AWS Route53 (DNS) related issues in order to run an Enterprise Knowledge Graph (EKG) (or a
semantic Digital Twin (DT), in AWS.
The main production DNS zone (called `main-domain` in the code) would be something
like `.` (e.g. `ekg.ekgf.org` or `digital-twin.ekgf.org`).
For each other environment, not being `prod`, such as `dev`, `staging`, `test` etc., a subdomain is created such
as `dev.ekg.ekgf.org` or `staging.digital-twin.ekgf.org`.