update Route53 docs to include ELB and s3-websites integration #426
Conversation
HarshCasper
requested review from
giograno and
quetzalliwrites
as code owners
Deploying localstack-docs with
|
| Latest commit: |
50a3738
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://6af60216.localstack-docs.pages.dev |
| Branch Preview URL: | https://harshmishra-doc-41.localstack-docs.pages.dev |
remotesynth
left a comment
remotesynth
left a comment
There was a problem hiding this comment.
One comment on maybe reconsidering how we structure this to eliminate the need for H4 headings but otherwise looks good.
|
|
||
| You can route traffic from a Route53 domain to an S3 bucket configured for static website hosting using alias records. This is useful when you want to serve a static website with a custom domain name. | ||
|
|
||
| #### Create an S3 bucket with website hosting |
There was a problem hiding this comment.
Not really an issue with your doc per se, but we may want to fix styling of H4 elements, because they are currently the same as H3. However, maybe there is a way to restructure this doc so that it only goes to H3? The reason is that H4 elements do not appear in the right hand page nav.
There was a problem hiding this comment.
Took a look at this, the only way he can restructure this doc is if he removed this h2 section:
## Routing traffic to AWS resources
LocalStack Route53 supports routing traffic to various AWS resources using alias records. This allows you to point your domain names directly to AWS services without managing IP addresses.
Then, he could turn both Routing to S3 static websites and Routing to Elastic Load Balancers into h2.
I am also ok with this doc as is, I do not consider the h4 styling problem a blocker for this content. (We could log a ticket to address the h4 styling issue.) But I also get Brian's point, there's always the argument about whether content can be improved/rewritten so that it's not necessary to go 4 levels. 😸
3 participants
Fixes DOC-41