Multicloud Data Management with AWS

Ditch the extra expense of compute resources in the cloud by using the most performant native DDI services along with centralized operations.

Jul 14th, 2022

Last week we talked about why you might use multicloud DDI, and this week we'll go a step deeper to talk about how you can achieve this with a proper DDI overlay solution.

Relevant AWS Technologies

If you're new to AWS, there are a couple of technologies we'll discuss for the sake of this blog and in general connecting Micetro, our DDI overlay solution, to AWS for IPAM and DNS management.

  • Route 53 -  A DNS service which is highly available and scalable.
  • VPC - Virtual Private Cloud - a virtual network located on AWS in which you can launch applications and services, such as you would in an on-premises data center

Being able to use the native technologies, such as Route 53 on AWS and Azure DNS allows admins to use the more performant DNS technologies without requiring costly extra resources to house non-native DNS appliances in the cloud. Using an overlay allows you to centralize control, minimize the learning curve, and still apply the same access control and workflows as you would use in other clouds or on-premises.

What you need to get started

If you're already running Micetro in your environment you will have all the components necessary for connecting and integrating Micetro with AWS. These components are:

  1. Central performs roles such as Identity and Access Management, database, and API access, among others…
  2. Web Application is the primary UI (User Interface).
  3. Console is currently required for the initial Micetro setup, some system administration, and certain features. All functionality is currently being integrated into the Web Application.
  4. Server Controller is required to broker the connection to AWS.

Once integrated, Micetro will import objects from Route 53. If additionally configured for AWS VPC integration, Micetro will also learn about subnets assigned to VPCs, their usage, and their characteristics. It will also populate the Micetro IPAM grid with this data.

Making the connection

After setting up the proper access/identity information in AWS and Micetro, which you can learn more about in this white paper, you'll need to set up the connection to AWS through the Management Console, sometimes referred to as the thick client. Simply do this under the Cloud Services tab as shown below.

Setting Up Route 53 Service in Micetro

Next you select the cloud of your choice, in this case AWS. Name the connection and specify the appropriate information as shown below.

Micetro imports the data from AWS, saves the account info, and configures the services. Now you'll be ready to use Micetro to run your daily DNS workflows as well as easily find troubleshooting information in the same place you would find your on-premises or other cloud information.

Automating Workflows and Self-Service

While using the same UI for your entire DDI environment simplifies operations, this can be taken a step further when we bring automation into the mix. By using an overlay with open APIs, such as Micetro, to run your DDI environment you essentially get a standardized API for your on-prem or cloud DNS, DHCP, and IP workflows. Meaning, you can create one automation workflow no matter where your application, service, or workload may reside.

To see how you can get started check out this video below or watch the whole automation playlist here.

For more detailed information

Looking for even more information on how and why to setup multicloud DNS and IPAM with AWS? Check out this technical white paper. Just want to get started with your own installation of Micetro? No problem, we have a free trial available. The wonderful thing about trying Micetro out is that you can have it deployed in less than an hour and you don't have to change where your devices point to. Micetro is an overlay and orchestration solution, and it's non-authoritative. We simply import IP information and then connect to your DNS and DHCP services. The thousands of devices you've already configured to connect to those services can stay as they are!