Integrating cloud services
Micetro provides native integration with cloud-based DNS and DHCP services, managing IP address data for Azure and AWS, including virtual networks and subnets within cloud accounts.
Using a cloud DNS service in Micetro is similar to working with other DNS services. The process of adding DNS zones, DNS records, or modifying them is identical to that of other DNS servers in Micetro.
Note
Currently, cloud DNS services only support the creation of primary zones.
Supported cloud services
Important
To use cloud services, the DNS and DHCP agents must be installed on the same machine as Micetro Central. For information about how to install DNS agents, refer to Installing Micetro DNS Agents on Windows or Installing Micetro DNS Agents on Linux.
Cloud service |
DNS |
IPAM |
|---|---|---|
Akamai |
Yes (Akamai Edge DNS) |
N/A |
Azure |
Yes (Azure DNS) |
Yes |
Amazon Web Services (AWS) |
Yes (Amazon Route 53) |
Yes |
NS1 |
Yes |
N/A |
Meraki |
N/A |
Yes |
Adding cloud services
Important
Before integrating cloud services, Micetro requires several prerequisites. Refer to Setting up cloud services on Windows or Setting up cloud services on Linux to make sure that these prerequisites are met.
You must have permission to administer DNS or DHCP to add a new service to Micetro.
To add a cloud service:
On the Admin page, select the Service Management tab.
Select Add Service in the task bar.
Select the cloud provider you want to use, enter the required information, and select Add.
Refer to the tabs below for details on each specific cloud provider.
Enter the information required to connect to Akamai Edge DNS:
Obtaining Access Credentials: For information about how to create API Access Credentials for Micetro, refer to Create EdgeGrid authentication credentials.
Warning
Akamai OPEN APIs are time-sensitive! It is crucial to synchronize the system your client operates on with a Stratum 2 or higher time source.
Danger
If the time on the server running the DNS Agent differs significantly from Coordinated Universal Time (UTC), authentication will fail, preventing access/updating of zones through Micetro.
Enter the information required to connect to Amazon Web Services (AWS):
Obtaining Access Credentials: For information about how to create API Access Credentials for use by Micetro, refer to AWS security credentials.
For information about how to add multiple AWS cloud accounts using single credentials, refer to Configuring AWS Multi-Account Setup.
For information about the minimum permissions required for adding AWS accounts, refer to Integrating Cloud Services with Micetro: Permissions Guide for AWS.
Enter the information required to connect to Azure:
For information about how to configure Azure DNS, refer to Configure Azure DNS.
To manage Meraki with Micetro, you must have an operational instance of the Micetro DHCP Agent. For additional details about the DHCP Agent, refer to Installing Micetro DHCP Agents on Windows or Installing Micetro DHCP Agents on Linux.
When connecting to Meraki, specify the location of the running DHCP Agent. You must also provide Micetro with a display name for the service and the API key to connect to Meraki.
Additionally, in the Ignore list field, enter the Meraki Organization or Network IDs that Micetro should exclude from synchronization. List one ID per line.
Obtaining Access Credentials: For information about how to create API Access Credentials for use by Micetro, refer to Cisco Meraki Dashboard API.
Synchronization parameters, e.g., network client synchronization interval, can be configured under Advanced System Settings.
Enter the information required to connect to NS1:
Obtaining Access Credentials: For information about how to create API Access Credentials for use by Micetro, refer to IBM NS1 Connect.
The service and any subnets defined will be displayed under DNS Services or DHCP Services and IP Ranges, respectively.
Editing cloud services
To edit the properties of a cloud service:
On the Service Management tab, locate the service you want to edit.
Double-click the service or select it, and then use the Action menu to select Edit service properties.
Make the necessary changes and select Save.
Removing cloud services
Warning
By removing a cloud service, the associated DNS service and the corresponding zones will be removed. Additionally, any subnets and cloud networks will also be removed.
To remove a cloud service:
On the Service Management tab, select the service you want to remove.
On the Action menu, select Remove DNS service.
Removing cloud networks
To remove a cloud network:
On the IPAM page, select the specific cloud network.
On the Action menu, select Delete network.
Related topics: