Updated on 2025-01-20 GMT+08:00

Permissions

If you need to grant your enterprise personnel permission to access your FlexusX resources, use Identity and Access Management (IAM). IAM provides identity authentication, fine-grained permissions management, and access control. IAM helps you securely access your cloud resources.

With IAM, you can create IAM users and grant them permissions to access only specific resources. For example, if you want some software developers in your enterprise to be able to use FlexusX resources but do not want them to be able to delete FlexusX or perform any other high-risk operations, you can create IAM users and grant permission to use FlexusX but not permission to delete them.

If your account does not require individual IAM users for permissions management, you can skip this section.

IAM can be used free of charge. You only pay for the resources in your account. For more information about IAM, see What Is IAM?

FlexusX Instance Permissions

New IAM users do not have any permissions assigned by default. You need to first add them to one or more groups and then attach policies or roles to these groups. The users then inherit permissions from the groups and can perform specified operations on cloud services based on the permissions they have been assigned.

FlexusX is a project-level service deployed for specific regions. When you set Scope to Region-specific projects and select the specified projects (for example, ap-southeast-2) in the specified regions (for example, AP-Bangkok), the users only have permissions for FlexusX in the selected projects. If you set Scope to All resources, the users have permissions for FlexusX in all region-specific projects. When accessing FlexusX, the users need to switch to the authorized region.

You can grant permissions by using roles and policies.
  • Roles: A coarse-grained authorization strategy that defines permissions by job responsibility. Only a limited number of service-level roles are available for authorization. Cloud services often depend on each other. When you grant permissions using roles, you also need to attach any existing role dependencies. Roles are not ideal for fine-grained authorization and least privilege access
  • Policies: A fine-grained authorization strategy that defines permissions required to perform operations on specific cloud resources under certain conditions. This type of authorization is more flexible and is ideal for least privilege access. For example, you can grant users only permission to manage a certain type of FlexusX cloud servers.

Permissions policies of a FlexusX instance are the same as those of an ECS. For details about the relationships between FlexusX system-defined policies and roles, and between FlexusX instance operations and system-defined policies, see ECS Permissions Management.

Helpful Links