RSS
 

This topic describes how to configure BOSH Director to deploy VMware Tanzu Operations Manager (Ops Manager) on Amazon Web Services (AWS).

Before beginning this procedure, ensure that you have completed all of the steps in Deploying Ops Manager on AWS.

Step 1: Log Into Ops Manager

  1. In a web browser, navigate to the fully qualified domain you created in the Configure DNS Records step of Deploying Ops Manager on AWS.

  2. Log in to Ops Manager. To log in, see Log In to Ops Manager For the First Time.

Step 2: AWS Config page

  1. Click the BOSH Director tile.

  2. Click AWS Config. The AWS Management Console Config page is shown.

    alt-text=""

  3. Select Use AWS Keys or Use AWS Instance Profile.

  4. Complete the rest of the AWS Management Console Config page:

    • Security Group ID: Enter the Group ID of the pcf-vms-security-group you created for your Ops Manager VMs in the Step 6: Configure a Security Group for Ops Manager VMs in Preparing to Deploy Ops Manager on AWS. Locate the Group ID in the Security Groups tab of your EC2 Dashboard.
    • Key Pair Name: Enter pcf-ops-manager-key.
    • SSH Private Key: Open the AWS key pair pcf-ops-manager-keys.pem file you generated in Step 3: Create an IAM User for Ops Manager in Preparing to Deploy Ops Manager on AWS. Copy the contents of the .pem file and paste it into the SSH Private Key text box.
    • Region: Select the region where you deployed Ops Manager.
    • VM Type Catalog Select the VM catalog that you want to use for your BOSH-deployed VMs.

    • AWS EBS disk type: Select the type of EBS volume for BOSH-deployed VMs to use.

      Caution: If you change this value, BOSH re-creates all VMs when you apply changes.

    • Encrypt Linux EBS Volumes: Select this checkbox to enable full encryption on persistent disks of all BOSH-deployed VMs except the Ops Manager VM and BOSH Director VM. For more information about using EBS encryption, see Configuring Amazon EBS Encryption for Ops Manager on AWS.

      Note: Enabling EBS encryption only encrypts Linux VMs. The Windows VMs deployed with VMware Tanzu Application Service for VMs [Windows] (TAS for VMs [Windows]) or TAS for VMs [Windows] 2012 R2 are not encrypted.

  5. Click Save.

Step 3: Director Config page

To configure the Director Config pane:

  1. Select Director Config.

    alt-text=""

  2. In the NTP Servers (comma delimited) field, enter at least three reachable NTP servers separated by a comma. For example: 0.amazon.pool.ntp.org,1.amazon.pool.ntp.org,2.amazon.pool.ntp.org,3.amazon.pool.ntp.org

    If your AWS environment is air gapped, consider using Amazon’s Time Sync Service which has a dedicated IP that does not require access to the internet or configuration changes to your security group or network ACL rules to access.

    1. The NTP server configuration only updates after VM recreation. If you modify the value of this field, select the Recreate VMs deployed by the BOSH Director checkbox to re-create your BOSH Director-deployed VMs and update the NTP server configuration. If you have any service tiles installed, ensure that the Recreate All Service Instances errand runs for each service tile.

  3. Leave the Bosh HM Forwarder IP Address field blank.

    Note: Starting in Pivotal Application Service (PAS) v2.0, BOSH-reported component metrics are available in Loggregator Firehose by default. If you continue to use the BOSH HM Forwarder to consume these component metrics, you might receive duplicate data. To prevent this, leave the Bosh HM Forwarder IP Address field blank.

  4. Select the Enable VM Resurrector Plugin checkbox to enable the BOSH Resurrector functionality and increase your runtime availability.

  5. The Enable BOSH System Metrics Server checkbox is deprecated, only keep it selected if your metrics system relies upon the format used. It is recommended that you switch away from this format as soon as possible, as this option is going away in future releases.

  6. Keep the Enable System Metrics checkbox selected to collect system metrics, including load, CPU, memory, swap, and disk metrics, and make them available for scraping from agents on each VM. This is recommended if you are using TAS, as it will scrape the agents automatically and insert the metrics into the regular logging and metrics egress stream. For a list of metrics collected, see System Metrics Agent in GitHub.

  7. Select Enable Post Deploy Scripts to run a post-deploy script after deployment. This script allows the job to execute additional commands against a deployment.

    Note: If you intend to install VMware Tanzu Kubernetes Grid Integrated Edition (TKGI), you must enable post-deploy scripts.

  8. Select Recreate VMs deployed by the BOSH Director to force BOSH to re-create BOSH-deployed VMs on the next deploy. This process does not re-create the BOSH Director VM or destroy any persistent disk data. This checkbox is cleared automatically after a successful re-deployment.

  9. Select Recreate BOSH Director VMs to force the BOSH Director VM to be re-created on the next deploy. This process does not destroy any persistent disk data. This checkbox is cleared automatically after a successful re-deployment.

  10. Select Recreate All Persistent Disks to force BOSH to migrate and re-create persistent disks for the BOSH Director and all tiles. This process does not destroy any persistent disk data. This checkbox is cleared automatically after a successful re-deployment.

  11. Select Enable bosh deploy retries to instruct Ops Manager to retry failed BOSH operations up to five times.

  12. Select Skip Director Drain Lifecycle to prevent drain scripts from running when the BOSH Director is re-created.

  13. Select Store BOSH Job Credentials on tmpfs (beta) to store credentials for BOSH jobs on temporary file storage (tmpfs) memory, rather than on disk. You must re-create all BOSH-deployed VMs for this setting to take effect.

  14. Select Keep Unreachable Director VMs to preserve BOSH Director VMs after a failed deployment for troubleshooting purposes.

  15. (Optional) Modify the Director Workers value, which sets the number of workers available to execute BOSH Director tasks. This field defaults to 5.

  16. (Optional) Max Threads sets the maximum number of threads that the BOSH Director can run simultaneously. VMware recommends that you leave the field blank to use the default value, unless doing so results in rate limiting or errors on your IaaS.

  17. (Optional) To add a custom URL for your BOSH Director, enter a valid hostname in Director Hostname. You can also use this field to configure a load balancer in front of your BOSH Director. For more information, see How to Set Up a Load Balancer in Front of Operations Manager Director in the VMware Tanzu Support knowledge base.

    alt-text=There are three text fields, Director Workers, Max Threads, and Director Hostname.

  18. (Optional) To set a custom banner that users see when logging in to the BOSH Director using SSH, enter text in the Custom SSH Banner field.

  19. (Optional) Enter your comma-separated custom Identification Tags. For example, iaas:foundation1, hello:world. You can use the tags to identify your foundation when viewing VMs or disks from your IaaS.

  20. For Certificate Duration Overrides, you can choose whether certificates generated within Ops Manager and CredHub use the default duration specified for the certificate or a custom duration value that you specify.

    alt-text=Three fields: the On-Off option for the feature, CA Certificate Duration (days) text field, Leaf Certificate Duration (days), and a link to the documentation for the feature.

    • Off: Select this option to use default duration for certificates created by all products.

    • On: Select this option to set a value to override the duration for certificates created by all products. If a product creates a certificate with a longer duration than the value you set, then the longer duration is used.

      1. CA Certificate Duration (days): Enter the number of days for which CA certificates are valid.
      2. Leaf Certificate Duration (days): Enter the number of days for which leaf certificates are valid. This value must be less than or equal to the CA certificate duration.

      Note: After you set a certificate duration override, you must take additional steps to apply the setting to all certificates. For more information, see Overriding Duration for Certificates.

  21. Select HM Pager Duty Plugin to enable Health Monitor integration with PagerDuty.

    alt-text=There is a selected check box, HM Pager Duty Plugin, and two text fields, Service Key and HTTP Proxy.

    • Service Key: Enter your API service key from PagerDuty.
    • HTTP Proxy: Enter an HTTP proxy for use with PagerDuty.

  22. Select HM Email Plugin to enable Health Monitor integration with email.

    alt-text=There is a selected check box, HM Email Plugin, and seven text fields: Host, Port, Domain, From, Recipients, Username, and Password.

    • Host: Enter your email hostname.
    • Port: Enter your email port number.
    • Domain: Enter your domain.
    • From: Enter the address for the sender.
    • Recipients: Enter comma-separated addresses of intended recipients.
    • Username: Enter the username for your email server.
    • Password: Enter the password for your email server.
    • Enable TLS: Select this checkbox to enable Transport Layer Security to the email host.

  23. For CredHub Encryption Provider, you can choose whether BOSH CredHub stores its encryption key internally on the BOSH Director and CredHub VM, or in an external hardware security module (HSM). The HSM option is more secure.

    Before configuring an HSM encryption provider in the Director Config pane, you must follow the procedures and collect information described in Preparing CredHub HSMs for Configuration.

    Note: After you deploy Ops Manager with an HSM encryption provider, you cannot change BOSH CredHub to store encryption keys internally.

    alt-text=""

    • Internal: Select this option for internal CredHub key storage. This option is selected by default and requires no additional configuration.

    • Luna HSM: Select this option to use a SafeNet Luna HSM as your permanent CredHub encryption provider, and fill in the following fields:

      Note: If you use multiple HSM hosts, you must use the Ops Manager API to set or update the HSM configuration. For more information, see Updating director and Iaas properties (Experimental) in the Ops Manager API documentation.

      1. Encryption Key Name: Any name to identify the key that the HSM uses to encrypt and decrypt the CredHub data. Changing this key name after you deploy Ops Manager can cause service downtime.
      2. Provider Partition: The partition that stores your encryption key. Changing this partition after you deploy Ops Manager could cause service downtime. For this value and the ones below, use values gathered in Preparing CredHub HSMs for Configuration.
      3. Provider Partition Password
      4. Partition Serial Number
      5. Provider Client Certificate: The certificate that validates the identity of the HSM when CredHub connects as a client.
      6. Provider Client Certificate Private Key
      7. HSM Host Address
      8. HSM Port Address: If you do not know your port address, enter 1792.
      9. HSM Certificate: The certificate that the HSM presents to CredHub to establish a two-way mTLS connection.

  24. Select a Blobstore Location to either configure the blobstore as an internal server or an external endpoint. Because the internal server is unscalable and less secure, VMware recommends that you configure an external blobstore.

    Note: After you deploy the BOSH Director, only Ops Manager users in Advanced Mode can change the blobstore location. For more information, see Ops Manager Fields That Lock On Deploy.

    • Internal: Select this option to use an internal blobstore. Ops Manager creates a new VM for blob storage. No additional configuration is required.

    • S3 Compatible Blobstore: Select this option to use an external S3-compatible endpoint. When you have created an S3 bucket, configure the following fields:

      1. S3 Endpoint:

        1. If you are using a public S3 endpoint:
          1. Locate the endpoint for your region. To find the endpoint, see the Amazon Simple Storage Service (S3) table in Regions and Endpoints in the AWS documentation.
          2. Construct a URL using your region’s endpoint. For example, if you are using the us-west-2 region, the URL you create would be https://s3.us-west-2.amazonaws.com. Enter this URL into the S3 Endpoint field.

        2. If you are using a non-public S3-compatible endpoint (Ops Manager v2.10.19 or earlier):

          1. Enter the URL for the non-public endpoint.

          2. SSH into the Ops Manager VM by running:

            ssh ubuntu@OPS-MANAGER-FQDN

            Where OPS-MANAGER-FQDN is the fully-qualified domain name (FQDN) of your Ops Manager deployment.

          3. Copy the custom public CA certificate you used to sign the S3 endpoint into the /etc/ssl/certs directory on the Ops Manager VM.

          4. On the Ops Manager VM, import the custom CA certificate into the Ops Manager VM truststore by running:

            sudo update-ca-certificates -f -v

          5. Add this custom CA certificate into the Trusted Certificates field in the Security page. For instructions, see Security Page.

        3. If you are using a non-public S3-compatible endpoint (Ops Manager v2.10.20 or later:
          1. Enter the URL for the non-public endpoint.
          2. Add the custom public CA certificate you used to sign the S3 endpoint to the Trusted Certificates field on the Director Config page.

      2. Bucket Name: Enter the name of the S3 bucket.

      3. URL Style: Select either path-style or domain-style to specify the URL style for the S3-compatible blobstore. By default, the blobstore uses domain-style URLs.

        Important: AWS ends support for path-style URLs for all S3 buckets created after September 30, 2020. For more information, see Support for Virtual-Hosted-Style URLs for AWS S3 Blobstores.

      4. Credentials Source: Input your credentials from the following sources.
        • Static Credentials: In Access Key and Secret Key, enter the keys you generated when creating your S3 bucket.
        • IAM Profile: Use the IAM profile associated with the BOSH Director.
          You must select the Enable Signed URLs checkbox to use IAM Profile credentials to access blobstores.
      5. Enable signed URLs: Select this checkbox to configure BOSH VMs to generate short-lived, pre-signed URLs for communication between the BOSH Agent and blobstore. If you enable this feature, BOSH Agents do not use credentials to communicate with the blobstore, and VM disks do not store blobstore credentials.

        Note: This feature is only available for BOSH VMs that use Xenial stemcell line 621 or later.

      6. Select V2 Signature or V4 Signature. If you select V4 Signature, enter your Region.

        Note: AWS recommends using Signature Version 4. For more information about AWS S3 Signatures, see Authenticating Requests in the AWS documentation.

      7. S3 Backup Strategy: To configure whether and how to back up the BOSH Director’s S3 blobstore, select one of the following options:
        • No backups
        • Use a versioned bucket: This option uses blobstore bucket versioning to save backups. It requires an S3 blobstore that supports versioning.
        • Copy into an additional bucket: This option saves blobstore backups to a separate bucket, which is useful with blobstores that do not support versioning. This option requires you to configure the Backup Bucket Region and Backup Bucket Name fields.

    • GCS Blobstore: Select this option to use an external Google Cloud Storage (GCS) endpoint.

      alt-text=""

      To create a GCS bucket, follow the procedures in Creating Storage Buckets in the GCS documentation. To create a GCS bucket, you must have a GCS account. When you have created a GCS bucket, configure the following fields:

      1. Bucket Name: Enter the name of your GCS bucket.
      2. Storage Class: Select the storage class for your GCS bucket. For more information, see Storage Classes in the GCP documentation.
      3. Service Account Key: Follow the steps in Set up IAM Service Accounts in Preparing to Deploy Ops Manager on GCP to download a JSON file with a private key. Enter the contents of the JSON file into the field.
      4. GCS Backup Strategy: To configure whether and how to back up the BOSH Director’s GCS blobstore, select one of the following options:
        • No backups
        • Copy into an additional bucket: This option saves blobstore backups to a bucket separate from the blobstore itself, and requires you to configure the Backup Bucket Region and Backup Bucket Name fields.

  25. For Database Location, select External MySQL Database and complete the following steps:

    Note: Use of an External MySQL Database only applies to the BOSH Director. UAA and CredHub will not use these settings and will continue to use the Postgres database colocated with the BOSH Director.

    Caution: After you deploy the BOSH Director, you cannot change the Database Location from an External MySQL Database to an Internal database or from an Internal database to an External MySQL Database.

    alt-text=There are two radio buttons: Internal, and External MySQL Database. There are five text fields, Host, Port, Username, Password, and Database. All fields are required when External MySQL Database is selected.

    • From the AWS Console, navigate to the RDS Dashboard.
    • Click Databases, then click the instance to display the Connectivity & security information.

    • Refer to the following table to retrieve the values for the Director Config page:

      RDS Instance Field BOSH Director Field
      Endpoint Host
      Port Port, which is 3306.

    • For Username, enter the username that you defined for your MySQL database when you created in the Create a MySQL Database using AWS RDS in Deploying Ops Manager on AWS.

    • For Password, enter the password that you defined for your MySQL database when you created in the Create a MySQL Database using AWS RDS in Deploying Ops Manager on AWS.
    • For Database, enter bosh.

    In addition, if you selected the Enable TLS for Director Database checkbox, you can fill out the following optional fields:

    • Enable TLS: Selecting this checkbox enables TLS communication between the BOSH Director and the database.
    • TLS CA: Enter the Certificate Authority for the TLS Certificate.
    • TLS Certificate: Enter the client certificate for mutual TLS connections to the database.
    • TLS Private Key: Enter the client private key for mutual TLS connections to the database.
    • Advanced DB Connection Options: This field accepts a JSON-formatted options string. It should be left blank unless directed by VMware Support.

  26. Click Save.

Step 4: Create Availability Zones page

Note: VMware recommends at least three availability zones (AZs) for a highly available installation of VMware Tanzu Application Service for VMs (TAS for VMs). The procedures in Preparing to Deploy Ops Manager on AWS use 3 AZs.

  1. Select Create Availability Zones.

    alt-text=The Create Availability Zones page in Ops Manager. See the following steps for information about each field.

  2. To add the three AZs you specified in the Create a VPC section of Preparing to Deploy Ops Manager on AWS:

    1. Click Add.
    2. For Amazon Availability Zone, enter the name of the AZ.
    3. Repeat until you have entered all three AZs, in the format REGION-#a, REGION-#b, and REGION-#c. For example, us-west-2a, us-west-2b, and us-west-2c.

  3. Click Save.

Step 5: Create Networks Page

  1. Select Create Networks.

    alt-text=The Create Networks page in Ops Manager. For more information, see the following steps for information about each field.

  2. (Optional) Select Enable ICMP checks to enable ICMP on your networks. Ops Manager uses ICMP checks to confirm that components within your network are reachable.

  3. Perform the following steps to add the network configuration that you created for your VPC in the Create a VPC in Preparing to Deploy Ops Manager on AWS. Record your VPC CIDR if you set a CIDR other than the recommendation.

    1. Click Add Network.
    2. For Name, enter management.

    3. Create a subnet for each availability zone by clicking Add Subnet. Refer to the table below for the information required to create all three subnets. When entering the VPC Subnet ID for each subnet, you must enter the corresponding Subnet ID associated with that subnet in the AWS VPC dashboard:

      First
      Subnet
      VPC Subnet ID Subnet ID for pcf-management-subnet-az0
      CIDR 10.0.16.0/28
      Reserved IP Ranges 10.0.16.0-10.0.16.4
      DNS 10.0.0.2*
      Gateway 10.0.16.1
      Availability Zones REGION-#a. Example: us-west-2a
      Second
      Subnet
      VPC Subnet ID Subnet ID for pcf-management-subnet-az1
      CIDR 10.0.16.16/28
      Reserved IP Ranges 10.0.16.16-10.0.16.20
      DNS 10.0.0.2*
      Gateway 10.0.16.17
      Availability Zones REGION-#b. Example: us-west-2b
      Third
      Subnet
      VPC Subnet ID Subnet ID for pcf-management-subnet-az2
      CIDR 10.0.16.32/28
      Reserved IP Ranges 10.0.16.32-10.0.16.36
      DNS 10.0.0.2*
      Gateway 10.0.16.33
      Availability Zones REGION-#c. Example: us-west-2c

      * If you set a VPC CIDR other than recommended, enter the second IP in your VPC CIDR. For example, for a 10.0.0.0/24 VPC CIDR, enter 10.0.0.2 in each subnet.

    4. Click Add Network.

    5. For Name, enter the name of your runtime. For example, tas or pks.

    6. Create a subnet for each availability zone by clicking Add Subnet. See the table below for the information required to create all three subnets:

      First
      Subnet
      VPC Subnet ID Subnet ID for pcf-tas-subnet-az0 or pcf-pks-subnet-az0
      CIDR 10.0.4.0/24
      Reserved IP Ranges 10.0.4.0-10.0.4.4
      DNS 10.0.0.2*
      Gateway 10.0.4.1
      Availability Zones REGION-#a. Example: us-west-2a
      Second
      Subnet
      VPC Subnet ID Subnet ID for pcf-tas-subnet-az1 or pcf-pks-subnet-az1
      CIDR 10.0.5.0/24
      Reserved IP Ranges 10.0.5.0-10.0.5.4
      DNS 10.0.0.2*
      Gateway 10.0.5.1
      Availability Zones REGION-#b. Example: us-west-2b
      Third
      Subnet
      VPC Subnet ID Subnet ID for pcf-tas-subnet-az2 or pcf-pks-subnet-az2
      CIDR 10.0.6.0/24
      Reserved IP Ranges 10.0.6.0-10.0.6.4
      DNS 10.0.0.2*
      Gateway 10.0.6.1
      Availability Zones REGION-#c. Example: us-west-2c

      * If you set a VPC CIDR other than recommended, enter the second IP in your VPC CIDR. For example, for a 10.0.0.0/24 VPC CIDR, enter 10.0.0.2 in each subnet.

    7. Click Add Network.

    8. For Name, enter services.

    9. Create a subnet for each availability zone by clicking Add Subnet. Refer to the table below for the information required to create all three subnets:

      First
      Subnet
      VPC Subnet ID Subnet ID for pcf-services-subnet-az0
      CIDR 10.0.8.0/24
      Reserved IP Ranges 10.0.8.0-10.0.8.3
      DNS 10.0.0.2*
      Gateway 10.0.8.1
      Availability Zones REGION-#a. Example: us-west-2a
      Second
      Subnet
      VPC Subnet ID Subnet ID for pcf-services-subnet-az1
      CIDR 10.0.9.0/24
      Reserved IP Ranges 10.0.9.0-10.0.9.3
      DNS 10.0.0.2*
      Gateway 10.0.9.1
      Availability Zones REGION-#b. Example: us-west-2b
      Third
      Subnet
      VPC Subnet ID Subnet ID for pcf-services-subnet-az2
      CIDR 10.0.10.0/24
      Reserved IP Ranges 10.0.10.0-10.0.10.3
      DNS 10.0.0.2*
      Gateway 10.0.10.1
      Availability Zones REGION-#c. Example: us-west-2c

      * If you set a VPC CIDR other than recommended, enter the second IP in your VPC CIDR. For example, for a 10.0.0.0/24 VPC CIDR, enter 10.0.0.2 in each subnet.

  4. Click Save.

    Note: If you are deploying VMware Tanzu Kubernetes Grid Integrated Edition (TKGI) with a TKGI workload load balancer, you must tag each AWS subnet with your TKGI Kubernetes cluster unique identifier before you create the load balancer. For more information about tagging subnets with a TKGI cluster unique identifier, see AWS Prerequisites.

    Note: After you deploy Ops Manager, you add subnets with overlapping Availability Zones to expand your network. For more information about configuring additional subnets, see Expanding Your Network with Additional Subnets.

Step 6: Assign AZs and Networks

  1. Click Assign AZs and Networks.

    alt-text=The Assign AZs and Networks page in Ops Manager. For more information, see the following steps for information about each field.

  2. Use the drop-down menu to select a Singleton Availability Zone. The BOSH Director is deployed into this AZ.

  3. Use the drop-down menu to select management under Network. The BOSH Director is deployed into this network.

  4. Click Save.

Step 7: Security Page

  1. Select Security. alt-text=""

  2. In Trusted Certificates, enter your custom certificate authority (CA) certificates to insert into your organization’s certificate trust chain. This feature enables all BOSH-deployed components in your deployment to trust custom root certificates.

    To enter multiple certificates, paste your certificates one after the other. For example, format your certificates like the example below:

    -----BEGIN CERTIFICATE-----
ABCDEFGH12345678ABCDEFGH12345678ABCDEFGH12345678AB
EFGH12345678ABCDEFGH12345678ABCDEFGH12345678ABCDEF
GH12345678ABCDEFGH12345678ABCDEFGH12345678...
------END CERTIFICATE------
-----BEGIN CERTIFICATE-----
BCDEFGH12345678ABCDEFGH12345678ABCDEFGH12345678ABB
EFGH12345678ABCDEFGH12345678ABCDEFGH12345678ABCDEF
GH12345678ABCDEFGH12345678ABCDEFGH12345678...
------END CERTIFICATE------
-----BEGIN CERTIFICATE-----
CDEFGH12345678ABCDEFGH12345678ABCDEFGH12345678ABBB
EFGH12345678ABCDEFGH12345678ABCDEFGH12345678ABCDEF
GH12345678ABCDEFGH12345678ABCDEFGH12345678...
------END CERTIFICATE------

    Note: If you want to use Docker registries to run TAS for VMs app instances in Docker containers, enter the certificate for your private Docker registry in this field. For more information about running app instances in TAS for VMs using Docker registries, see Using Docker Registries.

  3. To include the Ops Manager root CA in the Trusted Certificates field, select the Include OpsManager Root CA in Trusted Certs checkbox. BOSH Director includes this CA in the trust store of every VM that it deploys.

    Important: If you are using Ops Manager to generate certificates for either a load balancer or router, then you must select this checkbox.

  4. To clear the default trusted certificates from all BOSH-deployed Linux VMs, select the Clear the Default Trusted Certificates Store checkbox. You must provide your own trusted certificates when selecting this checkbox as all TLS communication fails without trusted certificates available.

    Note: This option is available in Ops Manager v2.10.21 and later.

  5. Choose Generate passwords or Use default BOSH password. VMware recommends that you use the Generate passwords option for greater security.

  6. Click Save. To view your saved BOSH Director password, click the Credentials tab.

Step 8: BOSH DNS Config page

The BOSH DNS Config pane allows you to configure DNS for BOSH Director by adding excluded recursors, a recursor timeout, and handlers.

The fields in the BOSH DNS Config pane are:

  • Excluded Recursors: Exclude recursor addresses, which are URL redirects, so that they are not contacted by the BOSH DNS server. For more information about how the BOSH DNS release selects recursors, see Recursors in Native DNS Support in the BOSH documentation.

  • Recursor Timeout: Specify a timeout for the BOSH DNS server to contact any connected recursor addresses. The time limit includes dialing, writing, and reading from the recursor. If any of these actions exceeds the time limit, the action fails.

  • Handlers: Specify recursor addresses that apply to specific domains. For example, you can use handlers to forward all requests to a domain to a private DNS for resolution. For more information about using handlers, see Additional Handlers in Native DNS Support in the BOSH documentation.

To add excluded recursors, a recursor timeout, or handlers to the BOSH DNS release:

  1. Select BOSH DNS Config.

    alt-text=""

  2. (Optional) In Excluded Recursors, enter a list of prohibited recursor addresses.

  3. (Optional) In Recursor Timeout, enter a time limit for contacting the connected recursors.

    Note: This time limit must include one of the Go parse duration time units. For example, entering 5s sets the timeout limit to five seconds. For more information about supported time units, see func ParseDuration in the Go Programming Language documentation.

  4. (Optional) In Handlers, enter an array of custom domain handlers in JSON format. For example:

    [
  {
    "cache": {
      "enabled": true
    },
    "domain": "example.com",
    "source": {
      "type": "http",
      "url": "http://example.endpoint.local"
    }
  }
]

  5. Click Save.

Step 9: Syslog Page

  1. Select Syslog.

  2. (Optional) Select Yes to send BOSH Director system logs to a remote server.

  3. Enter the IP address or DNS name for the remote server in Address.

  4. Enter the port number that the remote server listens on in Port.

  5. Select TCP or UDP from the Transport Protocol dropdown. This selection determines which transport protocol is used to send the logs to the remote server.

  6. (Optional) Select the Enable TLS checkbox to send encrypted logs to remote server with TLS. After you select the checkbox:

    1. Enter either the name or SHA1 fingerprint of the remote peer in Permitted Peer.
    2. Enter the SSL certificate for the remote server in SSL Certificate.

    Note: VMware strongly recommends that you enable TLS encryption when you are forwarding logs. Logs can contain sensitive information, such as cloud provider credentials.

  7. (Optional) Enter an integer in Queue Size. This value specifies the number of log messages held in the buffer. The default value is 100,000.

  8. (Optional) Select the checkbox to Forward Debug Logs to an external source. This option is deselected by default. If you select it, you may generate a large amount of log data.

  9. (Optional) Enter configuration details for rsyslog in the Custom rsyslog Configuration field. This field requires the rainerscript syntax.

  10. Click Save.

Step 10: Resource Config page

  1. Select Resource Config.

    alt-text=The Resource Config page in Ops Manager. For more information, see the following steps for information about each field.

  2. Adjust any values as necessary for your deployment. Under the Instances, VM Type, and Persistent Disk Type fields, select Automatic from the drop-down menu to allocate the recommended resources for the job. If the Persistent Disk Type field reads None, the job does not require persistent disk space.

    Note: For the BOSH Director job, select a VM type with at least 8 GB memory.

    Note: If you set a field to Automatic and the recommended resource allocation changes in a future version, Ops Manager automatically uses the new recommended allocation.

    Note: If you install VMware Tanzu Application Service for VMs [Windows] (TAS for VMs [Windows]), provision your Main Compilation Job with at least 100 GB of disk space.

  3. (Optional) To configure an Application Load Balancer (ALB) for your BOSH Director, click the icon next to the BOSH Director job name to see more fields. Enter your AWS target group name in the Load Balancers field for the BOSH Director job. Prepend the name with alb:. For example, enter alb:target-group-name.

    To create an ALB and target group, follow the procedures in Getting Started with Application Load Balancers in the AWS documentation. Then navigate to Target Groups in the EC2 Dashboard menu to find your target group Name.

    Note: To configure an ALB, you must have the following AWS IAM permissions.

      "elasticloadbalancing:DescribeLoadBalancers",
  "elasticloadbalancing:DeregisterInstancesFromLoadBalancer",
  "elasticloadbalancing:RegisterInstancesWithLoadBalancer",
  "elasticloadbalancing:DescribeTargetGroups",
  "elasticloadbalancing:RegisterTargets"

  4. Click Save.

Step 11: Complete the BOSH Director Installation

  1. Return to the Ops Manager Installation Dashboard.

  2. Click Review Pending Changes, then Apply Changes.

  3. BOSH Director begins to install. The Changes Applied window displays when installation is complete.

    alt-text=""

Next Steps

After completing the procedures in this topic, you must configure a runtime for Ops Manager. You can install Ops Manager on AWS with the TAS for VMs runtime.

To configure TAS for VMs, see Configuring TAS for VMs.

check-circle-line exclamation-circle-line close-line
Scroll to top icon