aws

Guide AWS CLI usage with profile-aware workflows and region enforcement.

3|Updated Feb 5, 2024
One-click install
npx skills add https://github.com/prismatic-koi/nixos-config --skill aws-prismatic-koi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aws
Source: https://github.com/prismatic-koi/nixos-config/tree/main/modules/programs/prism/opencode/skills/aws
Command: npx skills add https://github.com/prismatic-koi/nixos-config --skill aws-prismatic-koi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides users to use the AWS CLI correctly with safe, profile-aware workflows.

Core Features & Use Cases

  • Profile-aware command guidance for common tasks like listing resources, checking identity, and assuming roles.
  • Enforces explicit region usage and respects AWS_CONFIG_FILE and AWS_PROFILE to avoid accidental credential exposure.
  • Provides ready-to-run prompts and validation to prevent unsafe actions when permissions are insufficient.

Quick Start

Run an AWS CLI command using the provided profile and region to verify access.

Frequently Asked Questions about aws

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

FAQPage Schema
How do I use AWS CLI profiles to manage multiple environments safely?

Assume an AWS role safely by using profile-aware workflows that respect AWS_CONFIG_FILE. This prevents accidental credential exposure by avoiding direct edits to credentials, instead providing ready-to-run commands to assume roles across environments.

Why should I avoid directly editing AWS credentials when assuming roles?

Validate AWS CLI permissions before running commands to prevent unsafe actions. The Skill provides ready-to-run prompts and validation checks to ensure your current profile has sufficient permissions, stopping execution when access is insufficient.

What is the best way to verify my AWS CLI identity across different accounts?

The best way to verify AWS CLI identity is by running profile-aware commands that check your current caller identity. This enforces explicit region usage and validates access, ensuring you are operating under the correct profile and permissions.

Does this approach work for managing AWS resources across dev, staging, and prod?

Yes, this approach works for managing AWS resources across dev, staging, and prod by applying profile-aware command guidance. It safely handles role assumption and queries across environments by respecting AWS_PROFILE and enforcing explicit region usage.