mirror of
https://gitea.com/mcereda/oam.git
synced 2026-02-09 05:44:23 +00:00
chore(aws): start knowledge about route 53
This commit is contained in:
@@ -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
|
||||
|
||||
|
||||
@@ -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 '.[].[]' -
|
||||
|
||||
80
knowledge base/cloud computing/aws/route53.md
Normal file
80
knowledge base/cloud computing/aws/route53.md
Normal file
@@ -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
|
||||
|
||||
<!-- Uncomment if used
|
||||
<details>
|
||||
<summary>Setup</summary>
|
||||
|
||||
```sh
|
||||
```
|
||||
|
||||
</details>
|
||||
-->
|
||||
|
||||
<details>
|
||||
<summary>Usage</summary>
|
||||
|
||||
```sh
|
||||
# List hosted zones.
|
||||
aws route53 list-hosted-zones
|
||||
```
|
||||
|
||||
</details>
|
||||
|
||||
<!-- Uncomment if used
|
||||
<details>
|
||||
<summary>Real world use cases</summary>
|
||||
|
||||
```sh
|
||||
```
|
||||
|
||||
</details>
|
||||
-->
|
||||
|
||||
## 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.<br/>
|
||||
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.<br/>
|
||||
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.<br/>
|
||||
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]
|
||||
|
||||
<!--
|
||||
Reference
|
||||
═╬═Time══
|
||||
-->
|
||||
|
||||
<!-- In-article sections -->
|
||||
<!-- Knowledge base -->
|
||||
<!-- Files -->
|
||||
<!-- Upstream -->
|
||||
[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
|
||||
|
||||
<!-- Others -->
|
||||
Reference in New Issue
Block a user