Configuring instance details - BlueCat Address Manager - 9.1.0

BlueCat AWS Virtual Appliances

prodname
BlueCat Address Manager
version_custom
9.1.0

Configure the instance based on your needs and requirements.

In this task you will configure the eth0 interface for your Address Manager instance and the eth0 and eth1 interfaces for your BlueCat DNS for AWS instance. BlueCat recommends that all customers configure two interfaces on their BlueCat DNS for AWS instance regardless of their need for Dedicated Management in their environment.
  • For clean installations of BlueCat DNS for AWS, the eth1 interface of your AWS instance will be mapped to the Management interface (eth2) on your DNS/DHCP Server.
  • Customers upgrading to BlueCat DNS for AWS v8.3.0 or greater who previously configured eth0, eth1, and eth2 interfaces to enable Dedicated Management will not have any of their network interfaces modified by the upgrade.

To configure instance details:

  1. Set the following options to suit your requirements:
    • Number of instances—Enter 1.
      Note: The Launch into Auto Scaling Group option is currently not supported.
    • Purchasing option—Configure this option as needed.
    • Network—Select or create a VPC.
      Note: BlueCat strongly recommends connecting to your VPC using a VPN connection when working in a mixed environment where part of your DNS, DHCP and IPAM (DDI) infrastructure is on the premises and part of it's on the AWS cloud. For more details about AWS VPN connections, refer to http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Introduction.html.
    • Subnet—Select or create a subnet.
    • Auto-assign Public IP—Leave this option as Disable.
    • IAM role—Leave it as None.
    • Shutdown behavior—BlueCat recommends to select Stop.
    • Enable termination protection—Select the check box to enable this option.
    • Monitoring—Select the check box to enable this option.
    • Tenancy—Configure this option as needed.
    Note: For details information about AWS configuration and options, refer to AWS documentation.
  2. Under Network interfaces, enter an IP address for eth0 under the Primary IP column.
  3. Click Add Device to add the eth1 interface (BlueCat DNS for AWS only).
    Note:
    • Add the eth1 interface at this step if the subnet is attached to the same VPC. If you have the public and private subnets on different VPCs, you must create the AWS instance with only eth0 configured. You must then add the eth1 interface after the instance has been configured and assign it to the second subnet attached to the other VPC.
    • The subnet associated to eth0 and eth1 must be in the same availability zone.
  4. Select the subnet and enter an IP address for eth1 under the Primary IP column. Make sure that eth1 is on a different subnet than eth0.
    Note: BlueCat recommends that all customers add the eth1 interface even if they don't wish to enable Dedicated Management.
    Note: You can allow AWS to auto-assign any available IP addresses within your subnet to your instance. However, as a best practice, BlueCat recommends that you assign a specific IP addresses for eth0 and eth1.

    For detailed instructions on creating a VPC and adding a subnet on AWS, refer to http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Subnets.html#Create-VPC.

The eth0 interface has been added to your Address Manager instance and the eth0 and eth1 interfaces have been added to your BlueCat DNS for AWS instance. Proceed to the Advanced Details section to add your BlueCat license.