


How to use instance RAM role through API after activating RAM service
This article introduces how to use the instance RAM role through the API after activating the RAM service, and focuses on the operation steps.
Using the instance RAM role through the API
Usage restrictions
##The use of the instance RAM role has the following restrictions:Only ECS instances of the private network (VPC) network type can use the instance RAM role. An ECS instance can only be granted the RAM role to one instance at a time. When you have granted the instance RAM role to an ECS instance and want to access the API of the cloud product in an application deployed within the ECS instance, you need to obtain the temporary authorization token of the instance RAM role through the instance metadata. . See 5. (Optional) Obtain temporary authorization token. If you use the RAM user sub-account to use the instance RAM role, you need to authorize the RAM user to use the instance RAM role through the cloud account 6. (Optional).Prerequisite
You have already activated the RAM service. Please refer to the RAM document for activation methods to activate the RAM service.1. Create an instance RAM role
Call the interface CreateRole to create an instance RAM role. Set the RoleName parameter, such as setting its value to EcsRamRoleDocumentTesting. Set the AssumeRolePolicyDocument according to the following policy:{ "Statement": [ { "Action": "sts:AssumeRole", "Effect": "Allow", "Principal": { "Service": [ "ecs.aliyuncs.com" ] } } ], "Version": "1" }
2. Authorize the instance RAM role
Call the interface CreatePolicy to create a new authorization policy. Set the RoleName parameter, such as setting its value to EcsRamRoleDocumentTestingPolicy. Set PolicyDocument according to the following policy:{ "Statement": [ { "Action": [ "oss:Get*", "oss:List*" ], "Effect": "Allow", "Resource": "*" } ], "Version": "1" }
3. Grant the RAM role to the instance
Call the interface AttachInstanceRamRole to grant the RAM role to the instance. Set the RegionId and InstanceIds parameters to specify an ECS instance. Set the RamRoleName parameter, such as EcsRamRoleDocumentTesting.4. (Optional) Reclaim the instance RAM role
Call the interface DetachInstanceRamRole to reclaim the instance RAM role. Set the RegionId and InstanceIds parameters to specify an ECS instance. Set the RamRoleName parameter, such as EcsRamRoleDocumentTesting.5. (Optional) Obtain a temporary authorization token
You can obtain a temporary authorization token for the instance RAM role. This temporary authorization token can Execute the permissions and resources of the instance RAM role, and the temporary authorization token is automatically updated periodically. Example: Retrieve the temporary authorization token of the instance RAM role named EcsRamRoleDocumentTesting: Linux instance: Execute the command curl http://100.100.100.200/latest/meta-data/Ram/security -credentials/EcsRamRoleDocumentTesting. Windows instances: See the documentation for instance metadata. Obtain temporary authorization Token. The returned example is as follows:{ "AccessKeyId" : "XXXXXXXXX", "AccessKeySecret" : "XXXXXXXXX", "Expiration" : "2017-11-01T05:20:01Z", "SecurityToken" : "XXXXXXXXX", "LastUpdated" : "2017-10-31T23:20:01Z", "Code" : "Success" }
6. (Optional) Authorize the RAM user to use the instance RAM role
DescriptionWhen When you authorize a RAM user to use an instance RAM role, you must grant the RAM user PassRole permissions for the instance RAM role. Among them, PassRole determines whether the RAM user can directly execute the permissions granted by the role policy. Log in to the RAM console and refer to the document to authorize the RAM user to complete the authorization as follows:{ "Version": "2016-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "ecs: [ECS RAM Action]", "ecs: CreateInstance", "ecs: AttachInstanceRamRole", "ecs: DetachInstanceRAMRole" ], "Resource": "*" }, { "Effect": "Allow", "Action": "ram:PassRole", "Resource": "*" } ] }
The above is the detailed content of How to use instance RAM role through API after activating RAM service. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



The key differences between CentOS and Ubuntu are: origin (CentOS originates from Red Hat, for enterprises; Ubuntu originates from Debian, for individuals), package management (CentOS uses yum, focusing on stability; Ubuntu uses apt, for high update frequency), support cycle (CentOS provides 10 years of support, Ubuntu provides 5 years of LTS support), community support (CentOS focuses on stability, Ubuntu provides a wide range of tutorials and documents), uses (CentOS is biased towards servers, Ubuntu is suitable for servers and desktops), other differences include installation simplicity (CentOS is thin)

How to use Docker Desktop? Docker Desktop is a tool for running Docker containers on local machines. The steps to use include: 1. Install Docker Desktop; 2. Start Docker Desktop; 3. Create Docker image (using Dockerfile); 4. Build Docker image (using docker build); 5. Run Docker container (using docker run).

CentOS installation steps: Download the ISO image and burn bootable media; boot and select the installation source; select the language and keyboard layout; configure the network; partition the hard disk; set the system clock; create the root user; select the software package; start the installation; restart and boot from the hard disk after the installation is completed.

CentOS has been discontinued, alternatives include: 1. Rocky Linux (best compatibility); 2. AlmaLinux (compatible with CentOS); 3. Ubuntu Server (configuration required); 4. Red Hat Enterprise Linux (commercial version, paid license); 5. Oracle Linux (compatible with CentOS and RHEL). When migrating, considerations are: compatibility, availability, support, cost, and community support.

Docker process viewing method: 1. Docker CLI command: docker ps; 2. Systemd CLI command: systemctl status docker; 3. Docker Compose CLI command: docker-compose ps; 4. Process Explorer (Windows); 5. /proc directory (Linux).

Troubleshooting steps for failed Docker image build: Check Dockerfile syntax and dependency version. Check if the build context contains the required source code and dependencies. View the build log for error details. Use the --target option to build a hierarchical phase to identify failure points. Make sure to use the latest version of Docker engine. Build the image with --t [image-name]:debug mode to debug the problem. Check disk space and make sure it is sufficient. Disable SELinux to prevent interference with the build process. Ask community platforms for help, provide Dockerfiles and build log descriptions for more specific suggestions.

Docker uses Linux kernel features to provide an efficient and isolated application running environment. Its working principle is as follows: 1. The mirror is used as a read-only template, which contains everything you need to run the application; 2. The Union File System (UnionFS) stacks multiple file systems, only storing the differences, saving space and speeding up; 3. The daemon manages the mirrors and containers, and the client uses them for interaction; 4. Namespaces and cgroups implement container isolation and resource limitations; 5. Multiple network modes support container interconnection. Only by understanding these core concepts can you better utilize Docker.

VS Code system requirements: Operating system: Windows 10 and above, macOS 10.12 and above, Linux distribution processor: minimum 1.6 GHz, recommended 2.0 GHz and above memory: minimum 512 MB, recommended 4 GB and above storage space: minimum 250 MB, recommended 1 GB and above other requirements: stable network connection, Xorg/Wayland (Linux)
