Access Control for ECS

IAM Identity Authentication

IAM provides fine-grained permissions management, user identity authentication, and resource access control.

You can use your account to create IAM users, and assign permissions to the IAM users to control their access to specific resources. IAM permissions define which actions on your cloud resources are allowed or denied.

• For details about permissions management, see Permissions Management.
• For details about how to grant ECS permissions, see Creating a User and Granting ECS Permissions.
• For details about custom policies, see ECS Custom Policies.
• For details about policies and supported actions, see Permissions Policies and Supported Actions.

Project and Enterprise Project

You can group, manage, and isolate resources by project or enterprise project to control resource access and manage permissions by organization like enterprise, department, or project team.

• Project

  Projects in IAM are used to group and isolate OpenStack resources (computing resources, storage resources, and network resources). Resources in your account must be mounted under projects. A project can be a department or a project team. Multiple projects can be created for one account.

• Enterprise Project

  Enterprise projects are used to categorize and manage multiple resources. Resources in different regions can belong to one enterprise project. An enterprise can classify resources based on department or project group and put relevant resources into one enterprise project for management. Resources can be migrated between enterprise projects.

• Differences Between Projects and Enterprise Projects
  • IAM project

    Projects are used to categorize and physically isolate resources in a region. Resources in an IAM project cannot be transferred. They can only be deleted and then rebuilt.

    

  • Enterprise project

    Enterprise projects provide advanced functions than IAM projects and can be used to group and manage resources of different IAM projects of an enterprise. An enterprise project can contain resources across multiple regions, and resources can be added to or removed from enterprise projects. If you have enabled enterprise management, you cannot create IAM projects anymore and can only manage existing projects. In the future, enterprise projects will replace IAM projects.

    

  Both projects and enterprise projects can be managed by one or more user groups. Users who manage enterprise projects are in user groups. By attaching a policy to a user group, users in the group can obtain the permissions defined in the policy in the project or enterprise project.

  For details about how to create a project, create an enterprise project, and assign permissions, see Project and Enterprise Project.

Access Control

• VPC

  Virtual Private Cloud (VPC) allows you to create customized virtual networks in your logically isolated AZ. Such networks are dedicated zones that are logically isolated, providing secure network environments for your ECSs. You can define security groups, virtual private networks (VPNs), IP address segments, and bandwidth for a VPC. This facilitates internal network configuration and management and allows you to change your network in a secure and convenient network manner. You can also customize the ECS access rules within a security group and between security groups to improve ECS security.

• Security Group

  A security group is a collection of access control rules for ECSs that have the same security protection requirements and that are mutually trusted. By adding an ECS to a security group, you apply all the rules defined for this security group to this ECS.

For details about how to set a VPC and security group, see Purchasing a Custom ECS.

Mission-Critical Operation Protection

ECS protects against mission-critical operations. If you want to perform a mission-critical operation on the management console, you must enter a credential for identity verification. You can perform the operation only after your identity is verified. For account security, it is a good practice to enable operation protection. The setting will take effect for both the account and IAM users under the account.

For details about mission-critical operation protection, see Protection for Mission-Critical Operations.