diff --git a/knowledge base/cloud computing/aws/README.md b/knowledge base/cloud computing/aws/README.md index 14918fc..dbc8d1b 100644 --- a/knowledge base/cloud computing/aws/README.md +++ b/knowledge base/cloud computing/aws/README.md @@ -67,6 +67,7 @@ One can can rapidly remapping addresses to other instances in one's account and | [KMS] | Key management | | [OpenSearch] | ELK, logging | | [RDS] | Databases | +| [Route53] | DNS | | [S3] | Storage | | [Sagemaker] | Machine learning | | [Security Hub] | Aggregator for security findings | @@ -363,6 +364,7 @@ creation of non-compliant resources. [iam]: iam.md [opensearch]: opensearch.md [rds]: rds.md +[route53]: route53.md [s3]: s3.md [sagemaker]: sagemaker.md diff --git a/knowledge base/cloud computing/aws/cli.md b/knowledge base/cloud computing/aws/cli.md index 9469c23..9cb37fa 100644 --- a/knowledge base/cloud computing/aws/cli.md +++ b/knowledge base/cloud computing/aws/cli.md @@ -151,10 +151,6 @@ aws kms decrypt --ciphertext-blob 'fileb://ciphertext.dat' --query 'Plaintext' - | base64 --decode -# List hosted zones. -aws route53 list-hosted-zones - - # List all SageMaker EndpointConfigurations' names. aws sagemaker list-endpoint-configs --output 'yaml-stream' | yq -r '.[].EndpointConfigs[].EndpointConfigName' - aws sagemaker list-endpoint-configs --output 'yaml-stream' --query 'EndpointConfigs[].EndpointConfigName' | yq -r '.[].[]' - diff --git a/knowledge base/cloud computing/aws/route53.md b/knowledge base/cloud computing/aws/route53.md new file mode 100644 index 0000000..4b91a69 --- /dev/null +++ b/knowledge base/cloud computing/aws/route53.md @@ -0,0 +1,80 @@ +# Route 53 + +AWS DNS service offering. + +1. [TL;DR](#tldr) +1. [Split-view](#split-view) +1. [Further readings](#further-readings) + 1. [Sources](#sources) + +## TL;DR + + + +
+ Usage + +```sh +# List hosted zones. +aws route53 list-hosted-zones +``` + +
+ + + +## Split-view + +A.K.A _split-horizon_ DNS. + +Allows to use the same domain name for both **internal** _and_ **external** uses. + +Procedure: + +1. Create public **and** private hosted zones with the same name.
+ Split-view DNS will still work if using an external DNS service for the public hosted zone. +1. Associate one or more VPCs with the private hosted zone.
+ Route 53 Resolver will use the private hosted zone to route DNS queries in the associated VPCs. +1. Create records in each hosted zone. + + Records in the _public_ hosted zone will control how **internet** traffic is routed.
+ Records in the _private_ hosted zone will control how traffic is routed **inside the associated VPCs**. + +1. Use Route 53 Resolver to perform name resolution of **both** the associated VPC **and** on-premises workloads. + +## Further readings + +### Sources + +- [What is Amazon Route 53?] +- [Split-view DNS] + + + + + + + +[split-view dns]: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zone-private-considerations.html +[what is amazon route 53?]: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/Welcome.html + +