360 Secure SkillHub
360 安全技能中心

AWS STS

该 Skill 借助 OOMOL 的 oo CLI 调用 aws_sts 连接器，先用 oo connector schema 查询动作的输入/输出契约，再用 oo connector run 传入 JSON 载荷执行。提供 assume_role（写入）与 get_federated_credentials 两个动作，凭证由 OOMOL 服务端注入，用户不直接处理原始令牌。首次使用需安装 oo…

oomol
oomol
热度 53.04
最近更新 2026-09-20 11:25:39
分类：安全依赖：第三方 API / 代码执行应用场景：API 集成 / 工作流

安装技能

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

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

AWS STS

Operate AWS STS through your OOMOL-connected account. This skill calls the aws_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 AWS 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 "aws_sts" --action "<action_name>"

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

oo connector run "aws_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 AWS access key pair to call STS AssumeRole and return temporary credentials. [write]
  • get_federated_credentials — Return AWS 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 AWS 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 — AWS STS is not connected, or the connection expired or lacks a scope. Connect once (auth type: custom credential, federated) at:

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

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

Resources