AWS Networking & Content Delivery
AWS Route 53
AWS re:Invent 2019: AWS PrivateLink deployments: DNS mechanisms for routing & resiliency (NET321)

AWS re:Invent 2019: AWS PrivateLink deployments: DNS mechanisms for routing & resiliency (NET321)

Published on Dec 09, 2019

Looking to consume AWS PrivateLink–enabled services from on premises? In this session, we provide you with guidance on how DNS mechanisms can be used to route traffic as well as build resiliency for your connections into PrivateLink-enabled services in the Amazon Virtual Private Cloud (Amazon VPC) infrastructure.

2:27
Video preview
Why is the Route 53 Alias record for an Elastic Load Balancer not working or resolving?
2:27
57:42
Video preview
AWS re:Invent 2019: AWS PrivateLink deployments: DNS mechanisms for routing & resiliency (NET321)
57:42
55:00
Video preview
AWS re:Invent 2019: Deep dive on DNS in the hybrid cloud (NET410)
55:00

2020

4:35
How do I use a Route 53 Resolver inbound endpoint to resolve DNS records in a private hosted zone?

How do I use a Route 53 Resolver inbound endpoint to resolve DNS records in a private hosted zone?

4:35
4:50
Why can't I select my preferred alias target when creating a Route 53 alias resource record set?

Why can't I select my preferred alias target when creating a Route 53 alias resource record set?

4:50
2:27
Why is the Route 53 Alias record for an Elastic Load Balancer not working or resolving?

Why is the Route 53 Alias record for an Elastic Load Balancer not working or resolving?

2:27
Est. 2016, Copr. 0x4447™ LLC.
|
Terms of Service
Privacy Policy