awsclaw-sts

Automate AWS STS identity verification and temporary credential requests.

1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/necatiarslan/awsclaw --skill awsclaw-sts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: awsclaw-sts
Source: https://github.com/necatiarslan/awsclaw/tree/main/skills/awsclaw-sts
Command: npx skills add https://github.com/necatiarslan/awsclaw --skill awsclaw-sts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AWS STS operations require precise parameters and timely identity checks to avoid misconfigurations or unauthorized access, and manually crafting each request is error-prone. awsclaw-sts lets the assistant orchestrate STSTool commands so you can verify identities, assume roles, or decode authorization failures without reconstructing every API call.

Core Features & Use Cases

  • Identity Verification: Run GetCallerIdentity to confirm which account, ARN, and user ID your credentials represent before making changes.
  • Role Assumption & Temporary Credentials: Use AssumeRole, GetSessionToken, and federated token commands with RoleSessionName, duration, and policy overrides to obtain exactly the temporary credentials you need.
  • Authorization Troubleshooting: Decode encoded authorization failure messages or query access key info to understand denied actions for debugging and auditing.
  • Use Case: When you must switch into a cross-account role with external IDs, call AssumeRole with DurationSeconds and ExternalId to securely retrieve temporary credentials before continuing operations.

Quick Start

Ask STSTool to run GetCallerIdentity so you can confirm your AWS caller identity before making changes.

Frequently Asked Questions about awsclaw-sts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I assume an AWS cross-account role with temporary credentials using STS?

AWS STS role assumption uses AssumeRole with parameters like RoleSessionName, DurationSeconds, and ExternalId to retrieve temporary credentials for cross-account access. This lets you switch roles securely before continuing operations.

How can I verify my AWS caller identity before making account changes?

AWS caller identity verification runs GetCallerIdentity through STS to confirm your account, ARN, and user ID. Checking your caller identity prevents misconfigurations or unauthorized access before modifying resources.

How do I decode an AWS authorization failure message for debugging?

AWS authorization troubleshooting decodes encoded failure messages using DecodeAuthorizationMessage via STS. This reveals the denied actions and reasons, enabling precise debugging and auditing of access issues.

Can I get AWS session tokens with custom duration and policy overrides?

AWS STS GetSessionToken supports custom duration and policy overrides to obtain temporary credentials tailored to your session requirements. This restricts or grants permissions for specific operational scopes.

What is the best way to manage AWS federation tokens for temporary access?

AWS STS federation token commands provide temporary credentials for delegated access without sharing long-term keys. This approach secures identity verification and authorization across federated workflows.

Why do I need to check AWS access key info during authorization troubleshooting?

Querying AWS access key info via STS helps identify which credentials were used during denied actions, clarifying authorization failures. This is essential for accurate debugging and auditing of access attempts.