Skip to main content
Version: NG-2.14

AWS Route53

Introduction

Amazon Route 53 is a scalable and highly available Domain Name System (DNS) web service designed to route end-user requests to internet applications. With Amazon Route 53, developers can effortlessly register domain names, manage DNS settings, and perform health checks to ensure reliable application performance. The service integrates seamlessly with other AWS offerings, providing a unified experience for traffic management and routing at any scale. Whether used for simple websites or complex, global applications, Amazon Route 53 delivers low-latency, high-availability DNS solutions to meet diverse needs.

Getting Started

Compatibility

vuSmartMaps support monitoring of your Cloud DNS that uses AWS Route53, the metrics are fetched using AWS Cloudwatch API interface.

Data Collection Method

vuSmartmaps collects health and performance data for given DNS service using Telegraf Agent. This agent collects data based on the source's configuration which carry the region of Route53 deployment and AWS Credentials with the required AWS IAM permissions.

Prerequisites

Dependent Configuration

To configure this O11ySource, create a 'credential' of type 'aws' under the 'Definition' tab.

Inputs for Configuring Data Source

  • Data Source Name: Data source name to uniquely identify the source.
  • AWS Credential: AWS credential that provides Access key and Secret key to access Cloudwatch.
  • Polling Frequency: Specifies the interval in minutes at which data is collected. Data collection occurs once every specified period.

Firewall Requirement

To collect data from this O11ySource, ensure the following ports are opened:

Source IPDestination IPDestination PortProtocolDirection
IP address(es) of the vuSmartmaps ServerAWS CloudWatch Endpoint443TCPOutbound

*Before providing the firewall requirements, please update the port based on the customer environment.

Configuring the Target

Health and Performance metrics of Route53 DNS is collected through AWS CloudWatch service. So AWS CloudWatch services must be enabled in your AWS account. AWS Route53 should have APIs configured for which monitoring is enabled. Please enabled detailed metrics if you want to see resource and method level metrics for HTTP APIs.

An IAM role or user with the following permissions to access CloudWatch metrics.

  • cloudwatch:GetMetricData
  • cloudwatch:ListMetrics
  • cloudwatch:GetMetricStatistics
  • sts:GetCallerIdentity
  • tag:GetResources
  • tag:GetTagKeys
  • ec2:DescribeAvailabilityZones

Configuration Steps

  • Enable the O11ySource.
  • Select the Sources tab and press the + button to add a new Apache host to be monitored.
  • Populate all the configurations.
  • Click on Save to create the instance.

Metrics Collected

NameDescriptionData Type
TimestampTimestamp of telegraf agent collecting the metricsDateTime64
RegionAWS RegionLowCardinality(String)
HostHost details where telegraf is runningLowCardinality(String)
Health Check IDHealth Check ID of the health check which is monitoring the DNSLowCardinality(String)
Hosted Zone IDHosted Zone ID of the hosted zone created for the DNSLowCardinality(String)
Tenant IdTenant IdLowCardinality(String)
BU IdBusiness Unit IDLowCardinality(String)
Doc TypeDoc type for filtering various type of metrics collected in single table.LowCardinality(String)
Average Health Check StatusAverage Health Check Status for health check created for DNSFloat64
Maximum Health Check StatusMaximum value for Health Check Status for health check created for DNSUInt64
Avereage Percent Health CheckAverage Health Check Percentage for health check created for DNSFloat64
Maximum Percent Health CheckMaximum Health Check Percentage for health check created for DNSUInt64
Average Connection TimeAverage Connection Time for DNSFloat64
Maximum Connection TimeMaximum Connection Time for DNSUInt64
Average Count of Healthy ChildsAverage Count of Healthy Child in health checkFloat64
Maximum Count of Healthy ChildsMaximum Count of Healthy Child in health checkUInt64
Average SSL Handshake TimeAverage SSL Handshake Time taken for connecting to DNSFloat64
Maximum SSL Handshake TimeMaximum SSL Handshake Time taken for connecting to DNSUInt64
Average Time Taken for First ByteAverage Time taken to get first byte while connecting to DNSFloat64
Maxumum Time Taken for First ByteMaximum Time taken to get first byte while connecting to DNSUInt64
DNS Queries SumSum of all DNS queries received in given periodUInt64
DNSSec Internal FailuresSum of all the DNS Sec Internal FailuresUInt64
DNSSec Signing Key AgeMax age of the DNSSec singing key createdUInt64
DNSSec Signing Key Action NeededSum of all the DNSSec keys that needs actionUInt64
DNSSec Signing Key Age Needing ActionMax age of the DNSSec singing key which needs some actionUInt64