Provision Service Point v4 in AWS - BlueCat Edge - Service Point v4.x.x

BlueCat Edge Deployment Guide
Locale
English
Product name
BlueCat Edge
Version
Service Point v4.x.x

This section gives detailed instructions for provisioning Service Point v4 in AWS.

Before you begin:

  • You must have a valid AWS account with the correct permissions to deploy EC2 instances.
  • You must have the configuration file from when you created the Service Point v4 instance in the Edge CI. For more information, refer to Provision Service Point v4 on cloud environments.

DNS resolver configurations

When provisioning your service point in AWS, BlueCat recommends configuring the service point to use the default cloud DNS resolver. When the service point is provisioned in AWS, the default DNS resolver is the .2 IP address of the VNet that the service point is provisioned in. For example, if the VNet subnet is 192.168.1.0/24, the DNS resolver IP address is 192.168.1.2.

Provisioning the Service Point v4 VM on AWS:
Note: The following instructions are for the new EC2 UI. To enable the new EC2 UI within AWS, toggle the New EC2 Experience button.
  1. Log in to your AWS account.
  2. In the AWS console, navigate to your EC2 service Dashboard and click Launch Instance.
  3. Enter a name for the new EC2 instance. Optionally, you can add a tag to your EC2 instance by clicking Add additional tags and selecting the tag.
  4. Under Applications and OS Images, search for BlueCat DNS Edge Service Point v4, select the image and click Select.
  5. For Instance Type, select c5.xlarge, c5.2xlarge, or c5.4xlarge.
    Note: The minimum recommended instance type is c5.xlarge.
  6. For Key pair, select Proceed without a key pair.

    Your SSH key will be configured with the SSH Public Key that was provided when configuring the service point configuration details within the Edge Cloud.

  7. Under Network settings, configure your network settings.
    Select the security group that's created automatically, or create a new security group. If you create a new group, the following ports and protocols must be opened on the Service Point v4 VM in AWS:
    • Port 22 (TCP)—used for SSH connections.
    • Port 53 (TCP and UDP)—used for DNS service.
    • Port 2021 (TCP)—used for DNS resolver service diagnostics.
    • Port 8083 (TCP)—used for Service Point v4 telemetry APIs.
    Attention: Service Point v4 does not support changing IP addresses once the VM has been created.
  8. Configure the following storage requirements:
    • For Size, enter 100 GiB
    • For Volume Type, select General Purpose SSD (GP2).
  9. Click Advanced Details and for User Data, paste the contents of the configuration file that you downloaded from the Service points (v4) configuration page. Ensure that you select User data has already been base64 encoded.
    Note: If you selected the Copy configuration to clipboard button after creating the service point in the Edge Cloud Instance, paste the content from the clipboard into the User Data field and do not select the User data has already been base64 encoded option.
  10. Click Launch Instance.

Within your EC2 Instance dashboard, you can monitor the progress of the Service Point v4 provisioning. Once you see 2/2 checks passed, the service point is ready for use.

Once you have provisioned the Service Point v4 VM, you can deploy DNS resolver service. For more information, refer to DNS resolver services.

Attention: You can use the Service Point v4 telemetry APIs to verify that the Service Point v4 VM has successfully registered. The registrationStatus field within the Service Point v4 telemetry API response returns a value of REGISTERED when the Service Point v4 VM has successfully registered with the BlueCat Edge Cloud. If the value is not REGISTERED, this may indicate that there is an issue with the service point provisioning and the service point may not operate as intended.

For more information on the Service Point v4 telemetry APIs, refer to Service Point v4 Telemetry APIs.