---
name: secure-infrastructure-vpc-deploying
title: Deploying a landing zone deployable architecture
description: You can deploy a deployable architecture from the IBM Cloud catalog. You can choose one of several deployment options, including with IBM Cloud projects. Learn about IaC deployments with projects.
last-updated: 2025-09-03
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/secure-infrastructure-vpc?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Deploying a landing zone deployable architecture
{: #deploy}

You can deploy a deployable architecture from the IBM Cloud catalog. You can choose one of several deployment options, including with IBM Cloud projects. [Learn about IaC deployments with projects](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-understanding-projects&format=markdown).

## Deploying with IBM Cloud projects
{: #vpc-deploy-cloud}

To deploy a landing zone deployable architecture through the IBM Cloud catalog, follow these steps:

1.  Make sure that you comply with the prerequisites in the [planning](https://cloud.ibm.com/docs/secure-infrastructure-vpc?topic=secure-infrastructure-vpc-plan&format=markdown) topic:
    - Have an IBM Cloud API key.
    - Verify access roles.
    - Create an SSH key.
1.  Go to the IBM Cloud [catalog](https://cloud.ibm.com/catalog#reference_architecture){: external} and search for the architecture that you're interested in deploying:
    - Cloud foundation for VPC
    - VSI on VPC landing zone
    - Red Hat OpenShift Container Platform on VPC
1.  Click the tile for the deployable architecture to open the details.
1.  Select the latest product version in the Architecture section.
1.  Select a variation, if more than one is available.
1.  Click **Review deployment options**.
1.  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**.
1.  Edit and validate the configuration:
    1.  Select your authentication method. You can use an existing secret in Secrets Manager or add your API key directly. For more information, see [Using an API key or secret to authorize projects](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-authorize-project&format=markdown).
    1.  Enter values for other required fields from the Required tab.
    1.  Optional: Specify other values from the Optional tab.
    1.  Save the configuration.
    1.  Click **Validate**. Validation takes a few minutes

        IBM Cloud projects runs a Code Risk Analyzer scan that includes a [supported set of Compliance Manager rules](https://cloud.ibm.com/docs/code-risk-analyzer-cli-plugin?topic=code-risk-analyzer-cli-plugin-cra-cli-plugin&format=markdown#terraform-scc-rules). Controls that are part of the deployable architecture and that are also supported by IBM Cloud projects are checked. Any extra controls that are not included in the list of supported Compliance Manager 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](https://cloud.ibm.com/docs/secure-infrastructure-vpc?topic=secure-infrastructure-vpc-ts-na-failures&format=markdown).
1.  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.
    1.  Click **Deploy**.

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

1.  Review the outputs from the deployable architecture.

During the validation and deployment process, monitor the [needs attention items](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-needs-attention-projects&format=markdown). The widget reflects any issue that occurs in your configurations.
{: remember}