Upgrading Ops Manager Director on AWS

This topic describes how to upgrade Ops Manager Director for Pivotal Cloud Foundry (PCF) on Amazon Web Services (AWS). It corresponds to Step 2: Deploy Ops Manager in the Upgrading Pivotal Cloud Foundry topic.

In this procedure, you create a new Ops Manager VM instance that hosts the new version of Ops Manager. To upgrade, you export your existing Ops Manager installation into this new VM.

Retrieve the Ops Manager AMI ID

To retrieve the Amazon Machine Image (AMI) ID for Ops Manager, perform the following steps:

  1. Navigate to the Pivotal Cloud Foundry Operations Manager section of Pivotal Network.
  2. Select the version of PCF you want to install from the Releases dropdown.
  3. In the Release Download Files, click the file named Pivotal Cloud Foundry Ops Manager for AWS to download a PDF.
  4. Open the PDF and record the AMI ID for your region.

Launch the AMI

To launch the AMI ID for Ops Manager, perform the following steps:

  1. Navigate to your EC2 Dashboard.
  2. Click AMIs from the Images menu.
  3. Select Public images from the drop-down filter that says Owned by me.
  4. Paste the AMI ID for your region into the search bar and press enter.

    Note: There is a different AMI for each region. If you cannot locate the AMI for your region, verify that you have set your AWS Management Console to your desired region. If you still cannot locate the AMI, log in to the Pivotal Network and file a support ticket.

    Pcf aws ami

  5. (Optional) If you want to encrypt the VM that runs Ops Manager with AWS Key Management Service (KMS), perform the following additional steps:

    1. Right click the row that lists your AMI and click Copy AMI.
    2. Select your Destination region.
    3. Enable Encryption. For more information about AMI encryption, see Encryption and AMI Copy from the Copying an AMI topic in the AWS documentation.
    4. Select your Master Key. To create a new custom key, see Creating Keys in the AWS documentation.
    5. Click Copy AMI. You can use the new AMI you copied for the following steps.
  6. Select the row that lists your Ops Manager AMI and click Launch.

  7. Choose m5.large for your instance type and click Next: Configure Instance Details.

    Aws ami m5large

  8. Configure the following for your instance:

    • Network: Select the VPC that you created.
    • Subnet: Select pcf-public-subnet-az0.
    • Auto-assign for Public IP: Select Enable.
    • IAM role: Select the IAM role associated with your pcf-user profile. If you have not created one, click Create new IAM role and follow the Guidelines for Creating User Roles on AWS.
    • For all other fields, accept the default values.

    Pcf aws configure instance

  9. Click Next: Add Storage and adjust the Size (GiB) value. The default persistent disk value is 50 GB. Pivotal recommends increasing this value to a minimum of 100 GB.

    Pcf aws add storage

  10. Click Next: Tag Instance

  11. On the Add Tags page, add a tag with the key Name and value pcf-ops-manager.

  12. Click Next: Configure Security Group.

  13. Select the pcf-ops-manager-security-group that you created in Step 5: Configure a Security Group for Ops Manager.

  14. Click Review and Launch and confirm the instance launch details.

  15. Click Launch.

  16. Select the pcf-ops-manager-key key pair, confirm that you have access to the private key file, and click Launch Instances. You use this key pair to access the Ops Manager VM.

    Select pcfpem keypair

Edit the Ops Manager DNS A Record

  1. Click View Instances to access the Instances page on the EC2 Dashboard.

  2. Select the VM that you created in the previous section.

  3. Locate the IPv4 Public IP value in the instance Description tab, and record this value for use in the next step.

  4. In your DNS provider, edit the A record for pcf.YOUR-SYSTEM-DOMAIN to point to the IP address recorded in the previous step.

Continue Upgrading PCF

Continue to Step 3: Import Previous Ops Manager Installation in the Upgrading Pivotal Cloud Foundry topic.

Create a pull request or raise an issue on the source for this page in GitHub