360 Secure SkillHub
360 安全技能中心

Alibaba Cloud STS

该技能通过 oo CLI 调用 aliyun_sts 连接器，由 OOMOL 服务端注入凭证，用户无需处理原始 token。核心功能包括 assume_role（用 RAM AccessKey 调用 STS AssumeRole 获取临时凭证，属写操作）和 get_federated_credentials（基于 OIDC 联邦配置返回 STS 临时凭证）。典型场景：为应用或服务临时授予阿里云资源访问权限。使用时可先用 oo connector schema 查看输入输出结构，再用 oo connector run 传 JSON 执行，返回 data 与 meta.executionId。写操作执行前需与用户确认。

oomol
oomol
热度 55.11
最近更新 2026-09-23 18:55:25
分类：开发依赖：代码执行 / 第三方 API / 读写文件应用场景：API 集成 / DevOps / 自动化脚本

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add oo-aliyun-sts
Metadata
name
oo-aliyun-sts
description
Alibaba Cloud STS (alibabacloud.com). Use this skill for ANY Alibaba Cloud STS request — reading, creating, and updating data. Whenever a task involves Alibaba Cloud STS, use this skill instead of calling the API directly.
allowed-tools
["Bash(oo *)"]
metadata
{"title":"Alibaba Cloud STS","author":"OOMOL","version":"1.0.5","services":["aliyun_sts"],"icon":"https://static.oomol.com/logo/third-party/aliyun_sts.svg"}

Alibaba Cloud STS

Operate Alibaba Cloud STS through your OOMOL-connected account. This skill calls the aliyun_sts connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Alibaba Cloud STS. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "aliyun_sts" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "aliyun_sts" --action "<action_name>" --data '<json>' --json
  • --data takes a JSON object string or @path/to/file.json; omit it to send {}.
  • The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

  • assume_role — Use a connected Alibaba Cloud RAM AccessKey pair to call STS AssumeRole and return temporary credentials. [write]
  • get_federated_credentials — Return Alibaba Cloud STS temporary credentials from the connected OOMOL OIDC federation configuration.

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change Alibaba Cloud STS state — confirm the exact payload and effect with the user before running.
  • Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

  • oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

    curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux

    irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell

  • Not signed in / authentication error — sign in to your OOMOL account once:

    oo auth login

  • scope_missing / credential_expired / app_not_ready / app_not_found — Alibaba Cloud STS is not connected, or the connection expired or lacks a scope. Connect once (auth type: federated) at:

    https://console.oomol.com/app-connections?provider=aliyun_sts

  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources