Skip to content

Latest commit

 

History

History
61 lines (44 loc) · 3.59 KB

deploying.md

File metadata and controls

61 lines (44 loc) · 3.59 KB
copyright lastupdated keywords subcollection
years
2023
2023-08-02
secure-infrastructure-vpc

{{site.data.keyword.attribute-definition-list}}

Deploying a landing zone deployable architecture

{: #deploy}

You can deploy a deployable architecture from the {{site.data.keyword.cloud_notm}} catalog. You can choose one of several deployment options, including with {{site.data.keyword.cloud_notm}} projects. Learn about IaC deployments with projects.

Deploying with {{site.data.keyword.cloud_notm}} projects

{: #vpc-deploy-cloud}

To deploy a landing zone deployable architecture through the {{site.data.keyword.cloud_notm}} catalog, follow these steps:

  1. Make sure that you comply with the prerequisites in the planning topic:

    • Have an {{site.data.keyword.cloud_notm}} API key.
    • Verify access roles.
    • Create an SSH key.

  2. Go to the {{site.data.keyword.cloud_notm}} catalog{: external} and search for the architecture that you're interested in deploying:

    • VPC landing zone
    • VSI on VPC landing zone
    • Red Hat OpenShift Container Platform on VPC

  3. Click the tile for the deployable architecture to open the details.

  4. Select the latest product version in the Architecture section.

  5. Select a variation, if more than one is available.

  6. Click Review deployment options.

  7. Select the Add to project deployment type in Deployment options, and then click Add to project.

    1. Name your project, enter a description, and specify a configuration name. Click Create.

  8. Edit and validate the configuration:

    1. Select your authentication method. You can use an existing secret in {{site.data.keyword.secrets-manager_short}} or add your API key directly. For more information, see Using an API key or secret to authorize projects.

    2. Enter values for other required fields from the Required tab.

    3. Optional: Specify other values from the Optional tab.

    4. Save the configuration.

    5. Click Validate. Validation takes a few minutes

      {{site.data.keyword.cloud_notm}} projects runs a Code Risk Analyzer scan that includes a supported set of {{site.data.keyword.compliance_short}} rules. Controls that are part of the deployable architecture and that are also supported by {{site.data.keyword.cloud_notm}} projects are checked. Any extra controls that are not included in the list of supported {{site.data.keyword.compliance_short}} rules are not checked when you validate the configuration.

      If the validation fails because of the Code Risk Analyzer scan, you can troubleshoot the failure.

  9. Deploy the configuration:

    After you validate your configuration, you can deploy it to your target account.

    1. Review the input values and make any necessary changes.

    2. Click Deploy.

      Deploying the deployable architecture can take more than an hour. You are notified when the deployment is successful.

  10. Review the outputs from the deployable architecture.

During the validation and deployment process, monitor the needs attention items. The widget reflects any issue that occurs in your configurations. {: remember}