Provision Service Point v4 on cloud environments - BlueCat Edge - Service Point v4.x.x

This section gives instructions for creating the Service Point v4 instance in the Edge CI. Once you have created the service point in the Edge CI, you can provision the service point on cloud environments.

Configuring Service Point v4 configuration details:

1. Log in to the Edge Cloud Instance.
2. In the top navigation bar, click and select Service point (v4).
3. To add a new service point, click New on the Service point (v4) page.
4. Under Setup, enter the following information:
   • Name: enter the name of the new service point.
   • Description: add a description. This is optional.
5. Under Platform, select one of the following cloud platforms from the drop-down menu:
   • AWS
   • Azure
   • GCP
   • Equinix
6. Under Network, enter the following information:
   • Enter the hostname of the service point.
   • (Optional) Enter the IP address or FQDN of any NTP servers that the Service Point v4 VM will use. If you do not configure any NTP servers, the service point will use the following default Debian NTP servers:
     • 0.debian.pool.ntp.org
     • 1.debian.pool.ntp.org
     • 2.debian.pool.ntp.org
     • 3.debian.pool.ntp.org
     Note: BlueCat recommends testing the connection between the service point and NTP servers for reachability, as some networks do not allow NTP traffic by default.
7. Under Access, enter the following information:
   Note:

   • The SSH Public Key and VM Console Password fields are mandatory and must be filled out to provision the Service Point v4 VM.
   • The SSH Public Key and VM Console Password are applied to the operations user account.
   • SSH Public Key: Enter the SSH public key of the service point. You can use an existing key pair by entering the content of the public key in the field, or generate a new key pair and enter the content of the newly created public key in the field.

     This adds the public key to the .ssh directory of the Service Point v4 VM and allows you to SSH into the service point. Once you have provisioned the service point, you can access the service point using SSH and the associated private key to log into the operations user account.

   • VM Console Password: Enter the console password for the service point. The password must meet the following requirements:
     • It must contain lowercase characters.
     • It must contain uppercase characters.
     • It must contain numbers.
     • It must contain symbols.
     • It must not contain spaces.
     • It must contain at least 12 characters.
   • Confirm Password: Confirm the console password for the service point entered in the VM Console Password field.
8. (Optional) Under HTTP Proxy, enter the following information:
   • Enter the hostname of the proxy that the Service Point v4 VM will use.
   • (Optional) Add the port number used to connect to the proxy server. By default, the value is 443.
   • (Optional) Enter the username and password that will be used to authenticate against the proxy server.
   Note:

   • Currently, HTTP is the only supported proxy type.
   • SOCKS proxy servers are not supported.
   • Basic authentication is supported.
   • The proxy server must be configured to allow HTTP POST traffic.
   • The proxy server must be able to resolve all BlueCat Edge Cloud addresses.
   • For proxy servers and firewalls that do SSL interception:
     • mTLS must exclude/except *.bluec.at.
     • You can't install certificates as a workaround.
   • The only tested and supported authorization is Basic authorization with username and password provided.
9. Click Save and download. A window appears where you can download the configuration file.
10. Click Download configuration to download the configuration file or click Copy configuration to clipboard to copy the configuration content to your clipboard.
    Note: If you select the Copy configuration to clipboard button, the configuration content is copied as decoded content. You can paste the configuration content directly into the required user data fields without manually decoding the base64 encoded configuration content.