Networking & Content Delivery

Tag: Amazon Route 53

Secure your Amazon VPC DNS resolution with Amazon Route 53 Resolver DNS Firewall

Introduction There are many services that help you configure network security within your Amazon Virtual Private Cloud (VPC), including security groups (SGs), network access control lists (network ACLs), and the AWS Network Firewall. These services inspect and filter network traffic, but they do not apply to DNS queries provided by Route 53 Resolver, potentially allowing […]

Read More

Optimizing performance for users in China with Amazon Route 53 and Amazon CloudFront

China is an important market for global companies. Both enterprises and startups conducting or expanding business globally are looking for ways to tap into the growing user market in China. To help accelerate the customer cloud journey and help them move quickly into the new markets, AWS China (Beijing) Region was launched in 2016, followed […]

Read More

Automating DNS infrastructure using Route 53 Resolver endpoints

Introduction DNS name resolution is a fundamental part of all on-premises and cloud networks. For customers with hybrid networks, additional infrastructure and configuration are needed for private DNS resolution to work seamlessly across environments. However, building this type of DNS infrastructure in a multi-account environment is complex. In this post, we show how to automate […]

Read More

Real-time communication at CrazyCall using AWS Global Accelerator

In the telecommunications industry, real-time communication (RTC) refers to live media sessions between two endpoints with minimum latency and jitter. These sessions could be for voice, instant messaging or live video. Each of these solutions consists of one or more signaling message exchanges that control the call (e.g., authentication, authorization and access control, transcoding, or […]

Read More

Performing Route 53 health checks on private resources in a VPC with AWS Lambda and Amazon CloudWatch

If you have ever used Amazon Route 53 health checks to monitor resources, you know that monitored resources must have public IP addresses. This is because Route 53 health checkers are public and they can only monitor hosts with IP addresses that are publicly routable on the internet. You may want to monitor your resources […]

Read More