Alibaba Cloud
Visualize Alibaba Cloud resources and monitor changes through queries and alerts.
- Installation guide
- Alibaba Cloud data model
Installation
To install this integration, you will need to configure settings both within Alibaba Cloud and on JupiterOne. Before enabling in JupiterOne, ensure that you complete the setup within your Alibaba account.
Configuration on Alibaba Cloud
An AccessKey
and Secret Key
are required for the JupiterOne integration to
interact with Alibaba Cloud's API.
In order to obtain an Access Key ID/Secret
combination for the integration, an administrator of the Alibaba Cloud account will need to create a new RAM user the integration can use. Additionally, the user will need to have Read Only
access to the account.
To do so, the administrator can:
- Navigate to the RAM page in the Alibaba Cloud console.
- Select Create User. We suggest the name of the user include
JupiterOne
. - Check the Open API Access option while creating the new user.
- Obtain the Access Key ID/Secret combination that is generated.
- Grant the new user the
ReadOnlyAccess
permission.
For more information, refer to Alibaba Cloud's documentation for creating a RAM user or for generating the AccessKey ID and Secret Key.
Configuration in JupiterOne
To install the Alibaba Cloud integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Alibaba Cloud. Click New Instance to begin configuring the integration.
Creating an Alibaba Cloud instance requires the following:
The Account Name used to identify the Alibaba Cloud account in JupiterOne. Ingested entities will have this value stored in
tag.AccountName
when theAccountName
toggle is enabled.Description to assist in identifying the integration instance, if desired.
Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLED
and manually execute the integration.Enter the Alibaba Cloud AccessKey ID and Secret Key generated for use by JupiterOne.
Click Create once all values are provided to finalize the integration.
Next steps
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
Data Model
Entities
The following entities are created:
Resources | Entity _type | Entity _class |
---|---|---|
ALB Load Balancer | alibaba_cloud_alb_load_balancer | Gateway |
Account | alibaba_cloud_account | Account |
Autoscaling Group | alibaba_cloud_autoscaling_group | Deployment, Group |
ECS Instance | alibaba_cloud_ecs_instance | Host |
NAT Gateway | alibaba_cloud_nat_gateway | Gateway |
OSS Bucket | alibaba_cloud_oss_bucket | DataStore |
RAM Group | alibaba_cloud_ram_group | UserGroup |
RAM Policy | alibaba_cloud_ram_policy | Policy |
RAM Role | alibaba_cloud_ram_role | AccessRole |
RAM User | alibaba_cloud_ram_user | User |
VPC | alibaba_cloud_vpc | Network |
VPN Gateway | alibaba_cloud_vpn_gateway | Gateway |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
---|---|---|
alibaba_cloud_autoscaling_group | USES | alibaba_cloud_vpc |
alibaba_cloud_ram_group | HAS | alibaba_cloud_ram_user |
alibaba_cloud_ram_policy | ASSIGNED | alibaba_cloud_ram_group |
alibaba_cloud_ram_policy | ASSIGNED | alibaba_cloud_ram_role |
alibaba_cloud_ram_policy | ASSIGNED | alibaba_cloud_ram_user |
alibaba_cloud_vpc | HAS | alibaba_cloud_alb_load_balancer |
alibaba_cloud_vpc | HAS | alibaba_cloud_ecs_instance |
alibaba_cloud_vpc | HAS | alibaba_cloud_nat_gateway |
alibaba_cloud_vpc | HAS | alibaba_cloud_vpn_gateway |