Advanced users can also launch BlueCat AWS Virtual Appliances instances using the AWS command line interface.
In order to launch instances using the AWS CLI, you must install the AWS CLI and
configure it using the AWS Access Key ID and AWS Secret Access Key. For
detailed information about installing and configuring the AWS CLI, refer to the
following Amazon documentation: https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html
Before you launch the virtual appliance:
- Create the YAML license. See the
#cloud-config
example below for the format of the license file. - Locate the ID of the AMI. AMI IDs can be found by searching for BlueCat in the AWS Marketplace (AWS UI Console). In the Community AMIs tab, find the AMI that matches the purchased SKU and AWS Virtual Appliance version, and verify that the Owner ID is Amazon (679593333241). The ID for the AMI will be listed under the title (i.e. ami-02611a628fa59b375).
Note: Due to limitations with the cloud provider, you cannot change the IP
address of BlueCat AWS Virtual Appliances network interfaces
after installation. To change the IP address for BlueCat AWS Virtual Appliances, you must re-install
BlueCat AWS Virtual Appliances on a new instance with
the desired IP address changes and migrate your configuration to the new
instance.
To launch BlueCat AWS Virtual Appliances using the AWS CLI, run the following
command:
aws ec2 run-instances --image-id <ami-id> --count 1 --instance-type
<type.size> --key-name <aws key-pair> --security-group-ids <secure group
id> --subnet-id <subnet id> --private-ip-address <ip address> --user-data
file://path_to_your_license_file/license.txt
For
example:
aws ec2 run-instances --image-id ami-02611a628fa59b375 --count 1 --instance-type
t2.xlarge --key-name exampleName --security-group-ids sg-9bd625fd --subnetid
subnet-d2ca49b6 --private-ip-address 192.0.2.55 --user-data file://
path_to_your_license_file/license.txt
where license.txt has the
following content:
#cloud-config
bluecat_license:
key: "XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"
id: "XXXXXXXXXXXX"
Enter the license key you acquired from
https://care.bluecatnetworks.com in the
key
parameter and
your AWS account ID in the id
parameter.Note: #cloud-config must be
in a valid YAML format. Spaces are required before line 3 and 4 (Activation key
and AWS account ID).
Attention: Based on the Address
Manager or DNS/DHCP model that you would like to deploy, the
--instance-type
must be one of the following:BlueCat
Address Manager for AWS
BlueCat DNS and DHCP for AWS
Product SKU | Instance type | vCPUs | Memory (GB) |
---|---|---|---|
cBAM-1000 | t2.large | 2 | 8 |
cBAM-5000 | t2.xlarge | 4 | 16 |
cBAM-7000 | t2.2xlarge | 8 | 32 |
Product SKU | Instance type | vCPUs | Memory (GB) |
---|---|---|---|
cBDDS-25 | t2.large | 2 | 8 |
cBDDS-50 | t2.xlarge | 4 | 16 |
cBDDS-75 | t2.2xlarge | 8 | 32 |
cBDDS-125 | t2.2xlarge | 8 | 32 |
Note: C4.* instance types are no longer recommended due to KI-025622. C5.* instance types
cannot be used for Address Manager and DNS/DHCP Server v9.4.x due to lack of
ENA support. ENA is supported only for Address Manager and DNS/DHCP Server
v9.5.2 and greater.
For detailed information about AWS instance sizes, refer to https://aws.amazon.com/ec2/instance-types/.