Provisioning Amazon Web Services DocumentDB

You can provision an Amazon Web Services DocumentDB instance after you install and deploy Maximo® Application Suite from Amazon Web Services.

Procedure

  1. Open the Amazon Web Services console where the Maximo Application Suite is deployed and ensure that a DocumentDB instance is not provisioned.
  2. Create a subnet group.
    1. Select a Virtual Private Cloud (VPC) that contains a Maximo Application Suite unique string.
      For example, select masocp-bneluv-vpc from the list.
    2. Add all the subnets that are related to this VPC.
  3. Create a cluster parameter group.
    1. Type a new cluster parameter group name.
    2. Select a document database family.
      For example, select docdb4.0 from the list.
  4. Create a security group.
    1. Select the unique string that was created for the VPC.
    2. For inbound rules, select Custom TCP for the rule type and Custom for the source.
    3. For outbound rules, select All traffic for the rule type and Anywhere-PIV4 as the destination.
  5. On the Amazon Web Services Key Management Service (KMS) console, create a key.
    1. Configure the key type, usage, and advanced options, such as key material origin and region.
    2. Add labels, such as the alias, description, and tags.
    3. Configure the key usage details, such as key administrators and permissions.
    4. Review your key policy and click finish.
  6. Create a DocumentDB cluster.
    1. Select 5.0.0 for the engine version to create the cluster.
      Note: Maximo Application Suite supports only DocumentDB 5.0.0.
    2. Set Show Advanced settings to on.
    3. In Network Setting section, select the VPC that contains the unique string for Maximo Application Suite.
      The subnet group is selected automatically when you select the VPC.
    4. Select the security group that was created earlier. Remove any security group that is selected by default.
    5. Under cluster options, select the parameter group that was created earlier.
    6. Under encryption options, enable encryption and choose the KMS key that was created earlier.
    7. Create the DocumentDB cluster with other default options, such as maintenance, tags, and deletion protection.
    The cluster is deployed in some time, for example, in 15 minutes.
  7. Optional: Verify the DocumentDB connection by using a DB client.
    For example you can use Studio 3T to verify the connection. For more information, see Connecting to an Amazon DocumentDB cluster from Studio 3T.

What to do next

Configure a Maximo Application Suite instance to connect with the Amazon Web Services DocumentDB instance, update the MongoCfg CRD and LicenseService CRD with the Amazon Web Services DocumentDB connection details.

For more information, see Configuring Maximo Application Suite with Amazon Web Services DocumentDB