Enabling dedicated management on BlueCat DNS for AWS - BlueCat Address Manager

To enable and use the dedicated management interface on BlueCat DNS for AWS, you must have two interfaces (Service and a Management) already configured on your instance.

BlueCat DNS for AWS virtual appliances already in production must be removed from Address Manager control before enabling dedicated management.

To remove BlueCat DNS for AWS from BAM control:

From the BAM user interface, disable the server: Servers > server-name > Disable.
From the BlueCat DNS for AWS Administration Console, remove the server from BAM control:
```
Adonis> configure system
Adonis:configure:system>set state no-proteus-control
```

To enable dedicated management:

Connect to your instance as the admin user via an SSH connection to the Services interface.
```
ssh -i <key_pair_file_name> admin@<service_interface_ip>
```
From Main Session mode, run the following commands to enable dedicated management:
```
Adonis> configure interfaces
Adonis:configure:interfaces>set dedicated-management enable
```
CAUTION:
Enabling dedicated management will disconnect your SSH connectivity to the Services interface. Once you enable dedicated management, you must re-establish the SSH connection to the Management interface.

This completes enabling the dedicated management interface on BlueCat DNS for AWS

If you needed to remove your BlueCat DNS for AWS virtual appliance from BAM control prior to enabling dedicated management, replace the server in Address Manager to resume BAM control and management of the appliance (Servers > server-name > Replace).

Enabling dedicated management on BlueCat DNS for AWS - BlueCat Address Manager - 8.3.1

BlueCat AWS Virtual Appliances