VitalQIP Integrations

VitalQIP | Amazon Route 53

Amazon Route 53 is a highly available and scalable cloud Domain Name System (DNS) web service. It is designed to give an extremely reliable and effective way to route end users to applications on the Internet, infrastructure within internal and external networks, and to specific AWS infrastructure. Amazon Route 53 provides a very robust Web User Interface as well as API to help define and maintain the DNS infrastructure, and it supports DNS resolution over IPv4 and IPv6. VitalQIP customers who currently use Amazon Route 53 want the ability to see their Route 53 DNS data within VitalQIP. They have requested a “Single Pane of Glass” perspective, allowing the Route 53 data to be displayed within VitalQIP, along with their current DDI configuration data, thus providing them with an overall perspective of their organization’s networks.


VitalQIP Integrations | AWS Route 53

VitalQIP will display read-only Route 53 data retrieved from AWS at a configurable interval.  The display of the data will look similar to existing DNS Zone Profiles, and include Amazon-specific zone attributes, like VPC associations, as well as the zone’s name servers as Delegation Sets, and the zone’s resource records, excluding the Amazon-specific Alias resource record.  A new VitalQIP Route 53 Service, utilizing the AWS SDK, will be used to retrieve the Route 53 data from Amazon Route 53 service instances.  This VitalQIP Route 53 service will require new qip.pcy configuration parameters, an AWS service account configured to access Amazon Route 53 data and must run on the VitalQIP Enterprise server.  Auditing will be performed on all Route 53 data stored in the VitalQIP database.  Once the Route 53 data is loaded into VitalQIP, Route 53 hosted zones may be associated to DNS servers that are marked for management of Route 53 data.  VitalQIP will then allow DNS generations on these designated Route 53 DNS servers.  In addition, DNS dynamic updates of Route 53 zones in DNS can be configured and individual zone resource record publishing flags can be set by default and adjusted individually.