You can configure BOSH Director to deploy VMware Tanzu Operations Manager on Amazon Web Services (AWS).

Before you begin this procedure, ensure that you have followed all of the steps in Deploying Tanzu Operations Manager on AWS.

Step 1: Log in to Tanzu Operations Manager

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

  2. Log in to Tanzu Operations Manager. To log in, see Log In to Tanzu Operations Manager for the First Time.

Step 2: Configure AWS

  1. Click the BOSH Director tile.

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

    AWS Management Console Config

  3. Click 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 Tanzu Operations Manager VMs in the Step 6: Configure a Security Group for Tanzu Operations Manager VMs in Preparing to Deploy Tanzu Operations 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 Tanzu Operations Manager in Preparing to Deploy Tanzu Operations Manager on AWS. Copy the contents of the .pem file and paste it into the SSH Private Key text box.
    • Region: Click the region in which you deployed Tanzu Operations Manager.
    • VM Type Catalog Click the VM catalog that you want to use for your BOSH-deployed VMs.
    • AWS EBS disk type: Click the type of EBS volume for BOSH deployed VMs to use.

    Caution If you change this value, BOSH recreates all VMs when you Apply Changes.

    • Encrypt Linux EBS Volumes: Click this check box to enable full encryption on persistent disks of all BOSH deployed VMs except the Tanzu Operations Manager VM and BOSH Director VM.

      For more information about using EBS encryption, see Configuring Amazon EBS Encryption for Tanzu Operations Manager on AWS.

      Important Enabling EBS encryption only encrypts Linux VMs. The Windows VMs deployed with TAS for VMs [Windows] or TAS for VMs [Windows] 2012 R2 are not encrypted.

  5. Click Save.

Step 3: Complete the Director Config page

To configure the Director Config pane:

  1. Click Director Config.

    Director Config page

  2. In the NTP Servers (comma delimited) text box, 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. It has a dedicated IP address that does not require access to the internet or configuration changes to your security group or network ACL rules for access.

    • The NTP server configuration updates only after VM recreation. If you modify the value of this field, select the Recreate VMs deployed by the BOSH Director check box 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 text box blank. 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.

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

  5. If you want to collect detailed metrics from BOSH-managed VMs, select the Enable System Metrics check box. For a list of metrics that the System Metrics Agent collects from BOSH-managed VMs, see System Metrics Agent on GitHub. When you select this check box, ensure that the System Metrics Scraper is able to connect on port 53035 to all BOSH-managed VMs.

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

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

  1. Click Recreate VMs deployed by the BOSH Director to force BOSH to recreate BOSH-deployed VMs on the next deployment. This process does not recreate the BOSH Director VM or destroy any persistent disk data. This check box is cleared automatically after a successful redeployment.

  2. Select Recreate BOSH Director VMs to force the BOSH Director VM to be recreated on the next deploy. This process does not destroy any persistent disk data. This check box is cleared automatically after a successful redeployment.

  3. Select Recreate All Persistent Disks to force BOSH to migrate and recreate persistent disks for the BOSH Director and all tiles. This process does not destroy any persistent disk data. This check box is cleared automatically after a successful redeployment.

  4. Select Enable bosh deploy retries to instruct Tanzu Operations Manager to retry failed BOSH operations up to five times.

  5. Select Skip Director Drain Lifecycle to prevent drain scripts from running when the BOSH Director is recreated.

  6. 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.

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

  8. (Optional) Modify the Director Workers value, which sets the number of workers available to run BOSH Director tasks. The value in this text box defaults to 5.

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

  10. (Optional) To add a custom URL for your BOSH Director, enter a valid hostname in the Director Hostname text box. You can also use this text box 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 Tanzu Operations Manager Director.

    There are three text boxes, Director Workers, Max Threads, and Director Hostname.

  11. (Optional) To set a custom banner that users see when you log in to the BOSH Director using SSH, enter text in the Custom SSH Banner text box.

  12. (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.

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

    Three fields: the On-Off option for the feature, CA Certificate Duration (days) text field, and Leaf Certificate Duration (days).

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

    • On: Use 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, 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.

      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.

    Three fields: the Off-On option for the feature, CA Certificate Duration (days) text field, and Leaf Certificate Duration (days).

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

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

    There is a selected check box, HM Pager Duty Plugin, and two text boxes, Service Key and HTTP Proxy.

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

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

    There is a selected check box, HM Email Plug-in, and seven text boxes: Host, Port, Domain, From, Recipients, Username, and Password.

  16. 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.

    After you deploy Tanzu Operations Manager with an HSM encryption provider, you cannot change BOSH CredHub to store encryption keys internally.

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

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

      If you use multiple HSM hosts, you must use the Tanzu Operations Manager API to set or update the HSM configuration. For more information, see Updating a staged director's properties in the Tanzu Operations 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 Tanzu Operations Manager can cause service downtime.
      2. Provider Partition: The partition that stores your encryption key. Changing this partition after you deploy Tanzu Operations Manager could cause service downtime. For this value and the ones that follow, 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.

    CredHub Encryption Provider page

  17. Click Blobstore Location to configure the blobstore as either an internal server or an external endpoint.

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

    • Internal: Use this option for an internal blobstore. No additional configuration is required.

    • S3 Compatible Blobstore: Use this option for 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 (Tanzu Operations Manager v2.10.19 or earlier):

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

          2. SSH into the Tanzu Operations Manager VM by running:

            ssh ubuntu@OPS-MANAGER-FQDN

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

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

          4. On the Tanzu Operations Manager VM, import the custom CA certificate into the Tanzu Operations 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 (Tanzu Operations 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: Click either path-style or domain-style to specify the URL style for the S3-compatible blobstore. By default, the blobstore uses domain-style URLs.

        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: Type in 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 check box to use IAM Profile credentials to access blobstores.
      5. Enable signed URLs: Select this check box 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. 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. AWS recommends using Signature Version 4 (V4). 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: Use this option for an external Google Cloud Storage (GCS) endpoint.

      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: Use this 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 Tanzu Operations Manager on GCP to download a JSON file with a private key. Enter the contents of the JSON file into the text box.
      4. GCS Backup Strategy: To configure whether and how to back up the BOSH Director’s GCS blobstore, click 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 text boxes.

      On the Blobstore Location page, select "GCS Blobstore.

  18. For Database Location, click External MySQL Database and complete the following steps:

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

    Important 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. ![There are two radio buttons: Internal, and External MySQL Database. There are five text boxes, Host, Port, Username, Password, and Database.](../common/images/director_database.png) * From the AWS Console, go 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 Tanzu Operations 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 Tanzu Operations Manager on AWS.
    • For Database, enter bosh.

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

    • Enable TLS: Selecting this check box 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 Broadcom Support.

  19. Click Save.

Step 4: Create Availability Zones

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 Tanzu Operations Manager on AWS use 3 AZs.

  1. Click Create Availability Zones.

  2. To add the three AZs you specified in the Create a VPC section of Preparing to Deploy Tanzu Operations 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.

    The Create Availability Zones page in Tanzu Operations Manager. See the following steps for information about each field.

Step 5: Create Networks

  1. Click Create Networks.

    The Create Networks page in Tanzu Operations Manager. For more information, see the following steps for information about each field.

  2. (Optional) Click Enable ICMP checks to enable ICMP on your networks. Tanzu Operations 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 Tanzu Operations Manager on AWS. Record your VPC CIDR if you set a CIDR other than the recommended one.

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

    3. Create a subnet for each availability zone by clicking Add Subnet. See the following table 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

      Important 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. For more information, see the following table 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

      Important 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. See the following table 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

      Important 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.

Important 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.

After you deploy Tanzu Operations 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.

  2. Click a Singleton Availability Zone from the drop-down menu. The BOSH Director is deployed into this AZ.

  3. Click management under NetworkUse from the drop-down menu. The BOSH Director is deployed into this network.

  4. Click Save.

    The Assign AZs and Networks page in Tanzu Operations Manager. For more information, see the following steps for information about each field.

Step 7: Configure Security

  1. Click Security. Trusted certificates

  2. In Trusted Certificates, paste in 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. 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 text box. For more information about running app instances in TAS for VMs using Docker registries, see Using Docker Registries.

    To enter multiple certificates, paste in your certificates one after the other. For example, format your certificates as shown in the following example:

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

    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 text box. For more information about running app instances in TAS for VMs using Docker registries, see Using Docker Registries.

  3. To include the Tanzu Operations Manager root CA in the Trusted Certificates text box, select the Include Tanzu Ops Manager Root CA in Trusted Certs check box. BOSH Director includes this CA in the trust store of every VM that it deploys.
    If you are using Tanzu Operations Manager to generate certificates for either a load balancer or router, then you must select this check box.

  4. To clear the default trusted certificates from all BOSH-deployed Linux VMs, select the Clear the Default Trusted Certificates Store check box. You must provide your own trusted certificates when selecting this check box because all TLS communication fails if trusted certificates are not available.

    This option is available in Ops Manager v2.10.21 and higher.

  5. Select 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: Configure DNS for BOSH

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

The text boxes 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. Click BOSH DNS Config.

    BOSH DNS Config page

  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.

    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: Configure Syslog

  1. Select Syslog.

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

  3. In Address, enter the IP address or DNS name for the remote server.

  4. In Port, enter the port number that the remote server listens on.

  5. From the Transport Protocol drop-down menu, select TCP or UDP. This selection determines which transport protocol is used to send the logs to the remote server.

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

    1. In Permitted Peer, enter either the name or SHA1 fingerprint of the remote peer.

    2. In SSL Certificate, enter the SSL certificate for the remote server.

      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 a string in Environment identifier. This is a human-readable identifier that is included in each log entry.

  8. (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.

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

  10. (Optional) In the Custom rsyslog Configuration field, enter configuration details for rsyslog. This field requires the rainerscript syntax.

  11. Click Save.

Step 10: Configure Resources for BOSH Director

  1. Click Resource Config.

    The Resource Config page in Tanzu Operations 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, and 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.

    • For the BOSH Director job, click a VM type with at least 8 GB memory.

    • If you set a field to Automatic and the recommended resource allocation changes in a future version, Tanzu Operations Manager automatically uses the new recommended allocation.

    • 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. In the Load Balancers field for the BOSH Director job, enter your AWS target group name. 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.

    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 Tanzu Operations Manager Installation Dashboard.

  2. Click Review Pending Changes.

  3. Click Apply Changes.

  4. BOSH Director begins to install. The Changes Applied dialog box appears when installation is complete.

    Changes Applied dialog box, with 2 buttons: Close and Return to Installation Dashboard.

Next steps

After you follow the procedures in this topic, you must configure a runtime for Tanzu Operations Manager.

You can install Tanzu Operations 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