> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/alibaba-cloud-cloud-onboarding/prerequisites-for-onboarding-alibaba-cloud.md). # Prerequisites for onboarding Alibaba Cloud Before you begin onboarding Alibaba Cloud, you must review the following prerequisites. ### Permissions Before you begin to onboard Alibaba Cloud to Cortex XDR, ensure that you have the necessary permissions: * In Cortex XDR, you must have a Cortex XDR role with **Data Sources - View & Edit** permissions (to add/configure cloud accounts in Cortex XDR). This role is included in the following built-in roles: Instance Administrator, Security Admin, and IT Admin. * In Alibaba Cloud, your credentials must have the necessary [RAM permissions](#required-ram-permissions-in-alibaba-cloud) to deploy templates, manage roles and policies, as well as perform create and update operations for OIDC. ### Additional prerequisites Before you begin onboarding Alibaba Cloud, ensure that: * You have [added an OIDC provider](#add-cortex-cloud-as-an-oidc-provider-in-alibaba-cloud) for Cortex XDR in Alibaba Cloud. * You have the Alibaba Cloud account ID of the account you want to onboard. * You are logged into the Alibaba Cloud account. * If you are onboarding your first Alibaba Cloud account, you must first request manual provisioning of the cloud scanning environment. Open a customer support ticket to have the cloud scan environment created and ensure that the environment is ready for you to start onboarding. (Attempting to onboard Alibaba Cloud without first having the cloud scanning environment created will result in the following UI error: "No valid outpost scan env ALIBABA\_CLOUD".) ### **Required RAM permissions in Alibaba Cloud** Before onboarding Alibaba Cloud to Cortex XDR, ensure the user or role performing the onboarding has the necessary RAM permissions. #### Required permissions for onboarding Alibaba Cloud account scope Use the following template to create a custom policy with the permissions required for onboarding an Alibaba Cloud account to Cortex XDR. The custom policy can be created in Alibaba Cloud RAM Console at **Permissions → Policies → Create Policy → Script** and attach the policy to the RAM user or role that will run the Terraform apply. ```json { "Version": "1", "Statement": [ { "Effect": "Allow", "Action": [ "ram:CreateRole", "ram:GetRole", "ram:UpdateRole", "ram:DeleteRole", "ram:ListRoles", "ram:CreatePolicy", "ram:GetPolicy", "ram:GetPolicyVersion", "ram:DeletePolicy", "ram:ListPolicies", "ram:ListPolicyVersions", "ram:CreatePolicyVersion", "ram:DeletePolicyVersion", "ram:SetDefaultPolicyVersion", "ram:AttachPolicyToRole", "ram:DetachPolicyFromRole", "ram:ListPoliciesForRole", "sts:GetCallerIdentity" ], "Resource": "*" } ] } ``` ### Add Cortex XDR as an OIDC provider in Alibaba Cloud In order to establish trust between Cortex XDR and Alibaba Cloud, you must add an OpenID Connect (OIDC) provider. If you already have an existing OIDC provider for `accounts.google.com`, you can add Cortex XDR as an audience to the existing provider. Otherwise, create a new OIDC provider. #### Add the audience to an existing OIDC provider 1. In Alibaba Cloud Console, navigate to **RAM → Integrations → SSO**. 2. In **SSO**, select the **OIDC** tab. 3. In the list of IdPs, identify the existing entry for GCP (`accounts.google.com`) and click it. 4. Under **Client ID**, click **Add**. 5. Enter `alibaba-cortex-wif-` as the audience value for the new client ID where `` corresponds to the Cortex XDR Project ID. Save the changes. #### Create a new OIDC provider Before you begin, obtain the Cortex XDR Project ID of your tenant by clicking on the User menu and then selecting About. 1. In Alibaba Cloud Console, navigate to **RAM → Integrations → SSO**. 2. In **SSO**, select the **OIDC** tab. 3. Click **Create IdP**. 4. In **Create IdP**, enter the **IdP Name**. For example, `CortexGCPProvider`. 5. In **Issuer URL**, enter the GCP IdP URL: `https://accounts.google.com`. 6. In **Client ID**, enter: `alibaba-cortex-wif-` where `` corresponds to the Cortex XDR Project ID. 7. In **Fingerprint**, click **Auto-add** to automatically retrieve and add the signing certificate fingerprint for `accounts.google.com`. 8. (**cn-hongkong** and **eu-central-1** accounts only) In **Fingerprint**, click **Add** and enter the following SHA1 fingerprint: `932bed339aa69212c89375b79304b475490b89a0`. 9. Click **Add Fingerprint**. 10. Save the changes. ####
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/alibaba-cloud-cloud-onboarding/prerequisites-for-onboarding-alibaba-cloud.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.