Skip to content

Latest commit

 

History

History
62 lines (47 loc) · 4.65 KB

deploy.md

File metadata and controls

62 lines (47 loc) · 4.65 KB
copyright lastupdated keywords subcollection
years
2024
2024-05-09
watsonx-ai-saas-automation

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

Deploying Watsonx.ai SaaS with Assistant and Governance deployable architecture

{: #deploy}

You can deploy a deployable architecture from the {{site.data.keyword.cloud_notm}} catalog. You can choose from different deployment options, including an option to deploy with {{site.data.keyword.cloud_notm}} projects. For more information, see Learn about IaC deployments with projects.

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

{: #deploy-cloud}

To deploy the Watsonx.ai SaaS with Assistant and Governance deployable architecture through the {{site.data.keyword.cloud_notm}} catalog, complete the following steps:

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

  2. From the {{site.data.keyword.cloud_notm}} catalog{: external}, search for Watsonx.ai SaaS with Assistant and Governance, and click the tile for the deployable architecture.

  3. Select the latest product version from the Architecture section.

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

  5. Click Add to project.

    1. Name your project, enter a description, and specify a configuration name. Then, click Create.
    2. Select the region and the resource group where project artifacts must be stored.

  6. Edit and validate the configuration:

    1. Select your authentication method. You can use a trusted profile or an existing secret in {{site.data.keyword.secrets-manager_short}}. Alternatively, you can add your API key directly, which is not recommended. For more information, see Using an API key or secret to authorize projects.

    2. Enter the name of the target resource group from the Required tab.

    3. From the Optional tab, select a value or keep the default for the following options:

      1. The target location for the servies being deployed.
      2. The service plan for the required services.
      3. The service plan for the optional services. The default is "do not install".
      4. The existing service CRN if you don't want to install a service, but using an existing one. The default is to deploy a new instance or do not deploy the service at all, depending on the value you selected for the service plan.
      5. Whether the target resource group exists already, or it must be created.

    4. From the Optional tab, enter a value or accept the default for the following options:

      1. The resource prefix for uniquely naming the services that are being provisioned.
      2. The {{site.data.keyword.IBM_notm}} watsonx admin api key. It is recommended to store the api key in advance in Secrets Manager that's integrated with the {{site.data.keyword.cloud_notm}} projects and reference it from there.
      3. The name of the {{site.data.keyword.IBM_notm}} Watsonx starter project.

    5. From the Optional tab, if you want to enable storage delegation for the Cloud Object Storage instance using a {{site.data.keyword.IBM_notm}} Key Protect encryption key, then set at least the CRN of the {{site.data.keyword.IBM_notm}} Key Protect instance to use. You can provide the CRN of the encryption key as well, or let the automation creating one for you.

    6. Save the configuration.

    7. Click Validate. Validation takes a few minutes.

      {{site.data.keyword.cloud_notm}} projects runs an SCC scan against the {{site.data.keyword.cloud_notm}} for Financal Services profile. 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. {: important}

  7. 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 a few minutes. You are notified when the deployment is successful.

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