Before You Start
Before calling MaaS APIs, ensure that you have fully understood relevant concepts.
MaaS supports Representational State Transfer (REST) APIs, allowing you to call APIs using HTTPS. For details about API calling, see Calling APIs.
Endpoints
An endpoint is the request address for calling an API. Endpoints vary depending on services and regions. For the endpoints of all services, see Regions and Endpoints.
Constraints
For more constraints, see API description.
Terms and Definitions
- Account
An account is created upon successful registration with the cloud platform. The account has full access permissions for all of its cloud services and resources. It can be used to reset user passwords and grant user permissions. The account is a payment entity and should not be used directly to perform routine management. For security purposes, create IAM users and grant them permissions for routine management.
- IAM user
An IAM user is created by an account in IAM to use cloud services. Each IAM user has its own identity credentials (password and access keys).
An IAM user can view the account ID and IAM user ID on the My Credentials page of the console. The account, username, and password will be required for API authentication.
- Region
A region is a geographic area in which cloud resources are deployed. Availability zones (AZs) in the same region can communicate with each other over an intranet, while AZs in different regions are isolated from each other. By creating cloud resources in different regions, you can design your applications to better meet the needs of specific customers or comply with legal and other requirements in different regions.
- AZ
An AZ is a collection of one or more physical data centers with independent power, cooling, fire protection, and water supply systems. Within an AZ, compute, network, storage, and other resources are logically divided into multiple clusters. AZs within a region are interconnected using high-speed optical fibers to allow you to build cross-AZ, high-availability systems.
- Project
By default, each region corresponds to a project predefined by the system to isolate resources (compute, storage, and network resources) across physical regions. Permissions are granted at the default project level, allowing users to access all resources in that region under your account. For more granular access control, you can create subprojects within the region's default project and purchase resources in those subprojects. You can then grant permissions at the subproject level, allowing users to access only the resources within specific subprojects and enabling more fine-grained resource access control.
To view a project ID, go to the My Credentials page.
Figure 1 Project isolation model
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot