Alibaba Cloud FAQ and Troubleshooting
This article contains:
- A list of frequently asked questions related to connecting Alibaba Cloud to Tenable One Cloud Exposure.
- Account status and troubleshooting information.
- Steps to update an existing integration.
Exclude a Folder or Account from an Organization
To modify your organization's scope and remove specific entities:
- In the Cloud Exposure Console, navigate to Settings > Integrations.
- Click the three dots menu next to the organization, and click Edit.
- Click Next to navigate to the last step in the wizard (Scopes).
- Select Exclude specific folders and accounts and then select the relevant folder or account.
- Click Finish. The excluded entities will be removed from the Console after the next data sync.
Enable All Capabilities during Setup
The deployment script grants permissions only for the capabilities that you select when you deploy it. If you enable Data Resources Scanning (Data Protection) or Workload Protection later, you need to update the integration to grant the new permissions. Enabling all capabilities during initial setup avoids that extra step. For more information, see Update an Existing Integration.
Deployment Environments
For accounts created via the international website, you should select International as the environment. This will provide coverage for all regions, including Aliyun.
RAM User and RAM Role Architecture
The RAM user and RAM role serve different purposes. tenable-user holds the access key that Tenable uses to authenticate. tenable-role holds the permissions that define what Tenable can access. When Cloud Exposure needs to access your environment, it uses the access key to call Alibaba Cloud STS and assume tenable-role, which issues temporary credentials scoped to the role's policies.
This separation provides two benefits. First, permissions can be updated by modifying the role's policies without rotating the access key. Second, for organization connections, a single set of credentials in the management account can assume roles across all member accounts, so you do not need to provision separate credentials for each account.
When you integrate at the org level using the ROS script, the script automatically creates the role for you on every account. However, if you select manual deployment you need to create the role for every account.
Account Status and Troubleshooting
Cloud Exposure displays a Status for each account on the Accounts > Alibaba page, indicating whether Tenable can connect to the account and helping you troubleshoot potential issues.
| Status | Issue | Description |
|---|---|---|
| Connected | N/A | Cloud Exposure successfully connected to the account, and the account is up and running. |
| Connected with Issues | The account is connected, but there are specific issues that need to be addressed. | |
| Connected with Issues | Missing permissions for ECS scanning (Workload Protection) | The RAM role is missing permissions that Cloud Exposure needs to scan ECS instances. This issue appears for integrations deployed before encrypted disk scanning was released, because they do not include the ecs:CopySnapshot permission. To resolve the issue, update the integration. |
| Connected with Issues | Missing encryption permissions for ECS scanning (Workload Protection) | Cloud Exposure cannot scan ECS instances with encrypted disks. The AliyunECSDiskEncryptDefaultRole or AliyunECSShareEncryptSnapshotDefaultRole role is missing, its trust policy does not include the required principals, or it does not have the required KMS permissions. This issue appears only after the Missing permissions for ECS scanning (Workload Protection) issue is resolved. To resolve the issue, update the integration. If you use a role that already existed in your account, see If a Role Already Exists. |
| Failed | Access denied | Cloud Exposure was not able to synchronize one or more resource types. This is likely because the RAM role is missing required read permissions. Review the policies attached to the RAM role created during account onboarding and ensure they include all required permissions. See Alibaba Cloud Required Permissions. |
| Failed | Missing permissions | There is an issue with the RAM role created during account onboarding. The role cannot perform the required operations. Ensure the role exists, the trust policy is configured correctly, and the required policies are attached. See Alibaba Cloud Required Permissions. |
| Failed | Not found, pending deletion | The Alibaba Cloud account no longer exists in the Resource Directory. It may have been deleted or closed. The account will be removed from Cloud Exposure. |
| Failed | Organization is not connected | The Resource Directory organization has a connectivity issue that is preventing Cloud Exposure from connecting to member accounts. Resolve the issue at the organization level first — verify the management account's RAM user credentials and role configuration. |
| Failed | Role AssumeRolePolicy missing user permissions | The RAM role's trust policy does not allow the configured RAM user to assume it. Update the role's trust policy in the Alibaba Cloud RAM console to grant the RAM user permission to assume the role. |
| Failed | Role not found | The RAM role created during account onboarding does not exist. It may have been deleted. Re-create the role, or verify the Role ARN configured in Cloud Exposure. |
| Failed | User access key not found | The RAM user AccessKey ID configured during onboarding does not exist. It may have been deleted or rotated. Verify the AccessKey ID in the Alibaba Cloud RAM console and update it in Cloud Exposure. |
| Failed | User credentials are not valid | The RAM user AccessKey secret configured during onboarding is incorrect or has been rotated. Re-enter the correct AccessKey secret in Cloud Exposure. |
| Failed | User missing assume role permissions | The RAM user does not have permission to assume the configured RAM role. Attach the AliyunSTSAssumeRoleAccess policy to the RAM user in the Alibaba Cloud RAM console. |
| Excluded | N/A | The account was excluded from synchronization based on your organization's scope configuration. To modify scope settings, see Connect an Alibaba Cloud Organization. |
| Deleted | N/A | The account is no longer a member of the Resource Directory organization. It may have been removed or transferred. Resources and findings associated with deleted accounts are hidden in Cloud Exposure. |
Organization Status and Troubleshooting
Cloud Exposure displays a Status for each organization in Settings > Integrations, indicating whether Tenable can connect to the management account and helping you troubleshoot potential issues.
| Status | Issue | Description |
|---|---|---|
| Connected | N/A | Cloud Exposure successfully connected to the organization, and the organization is up and running. |
| Connected with Issues | N/A | The organization is connected, but there are specific issues that need to be addressed. |
| Failed | Missing permissions | There is an issue with the RAM role configured for the management account. The role cannot perform the required operations. Ensure the trust policy is configured correctly and the required policies are attached. See Alibaba Cloud Required Permissions. |
| Failed | Role AssumeRolePolicy missing user permissions | The RAM role's trust policy does not allow the configured RAM user to assume it. Update the role's trust policy in the Alibaba Cloud RAM console to grant the RAM user permission to assume the role. |
| Failed | Role not found | The RAM role configured for the management account does not exist. It may have been deleted. Re-create the role, or verify the Role ARN configured in Cloud Exposure. |
| Failed | User access key not found | The RAM user AccessKey ID configured during onboarding does not exist. It may have been deleted or rotated. Verify the AccessKey ID in the Alibaba Cloud RAM console and update it in Cloud Exposure. |
| Failed | User credentials are not valid | The RAM user AccessKey secret configured during onboarding is incorrect or has been rotated. Re-enter the correct AccessKey secret in Cloud Exposure. |
| Failed | User missing assume role permissions | The RAM user does not have permission to assume the configured RAM role. Attach the AliyunSTSAssumeRoleAccess policy to the RAM user in the Alibaba Cloud RAM console. |
Update an Existing Integration
When Tenable adds permissions to the Alibaba Cloud integration, you need to update existing integrations to grant them. For example, encrypted disk scanning requires new permissions and two new RAM roles. Until you update the integration, the account shows the Missing permissions for ECS scanning (Workload Protection) issue, and Cloud Exposure does not scan encrypted disks.
To update an existing integration:
-
In the Cloud Exposure Console, open the integration in edit mode. Do one of the following:
- To update an account, navigate to Settings > Organization > Accounts > Alibaba Cloud, select the account, click the three dots menu, and click Edit.
- To update an organization, navigate to Settings > Integrations, click the three dots menu next to the organization, and click Edit.
-
Under Deployment, do one of the following:
- ROS — Copy the script and run it. The script updates your existing ROS stack.
- Terraform — Replace your module call with the module call shown in the wizard, and then run terraform apply.
- Manual — Update your policies and roles to match Alibaba Cloud Required Permissions.
- Click Finish.