Networking and Content Delivery

Official references for this objective

• Amazon Web Services — Target groups for your Network Load Balancers - Elastic Load Balancing

  Network Load Balancers do not support the lambda target type.

• Amazon Web Services — Choosing a routing policy - Amazon Route 53

  Latency routing policy – Use when you have resources in multiple AWS Regions and you want to route traffic to the Region that provides the

• Amazon Web Services — Enable internet access for a VPC using an internet gateway - Amazon Virtual Private Cloud

  If a subnet is associated with a route table that has a route to an internet gateway, it's known as a public subnet

• Amazon Web Services — Example: VPC with servers in private subnets and NAT - Amazon Virtual Private Cloud

  For VPC endpoints , if your instances must access an S3 bucket, keep the S3 Gateway default.

• Amazon Web Services — Health checks for Network Load Balancer target groups - Elastic Load Balancing

  initial The load balancer is in the process of registering the target or performing the initial health checks on the target.

• Amazon Web Services — How CloudFront delivers content - Amazon CloudFront

  If the object is not in the cache, the POP typically goes to the nearest regional edge cache to fetch it.

• Amazon Web Services — Private IP AWS Site-to-Site VPN with Direct Connect - AWS Site-to-Site VPN

  you can deploy IPsec VPN over Direct Connect, encrypting traffic between your on-premises network and AWS, without the use of public IP addresses or additional

• Amazon Web Services — Route table concepts - Amazon Virtual Private Cloud

  Edge association —A route table that you use to route inbound VPC traffic to an appliance. You associate a route table with the internet gateway

• Amazon Web Services — Working with hosted zones - Amazon Route 53

  Public hosted zones contain records that specify how you want to route traffic on the internet.