Aws Service Authorization Reference

Created By
psantusa year ago
Overview

What is AWS Service Authorization Reference?

AWS Service Authorization Reference is a documentation resource that provides exhaustive reference data on all IAM Actions, Resources, and Condition Keys for AWS services, consolidating information that was previously scattered across multiple service documentations.

How to use AWS Service Authorization Reference?

To use the AWS Service Authorization Reference, you can run the MCP server using Docker or uv. For Docker, use the command: docker run -i --rm psantus86/aws-service-authorization-reference-mcp-server:latest. For uv, run uv build followed by uv run main.py.

Key features of AWS Service Authorization Reference?

  • Access to comprehensive IAM actions, resources, and condition keys for AWS services.
  • Programmatic support for retrieving service codes, actions, resources, and condition keys.
  • Debugging capabilities using the MCP inspector.

Use cases of AWS Service Authorization Reference?

  1. Retrieving IAM actions for specific AWS services.
  2. Accessing resources and condition keys for AWS service actions.
  3. Debugging and inspecting the MCP server for development purposes.

FAQ from AWS Service Authorization Reference?

  • What is the purpose of the AWS Service Authorization Reference?

It consolidates IAM actions, resources, and condition keys into a single reference point for easier access and understanding.

  • Is there a cost associated with using the AWS Service Authorization Reference?

No, it is free to use as part of the AWS documentation and tools.

  • How can I contribute to the AWS Service Authorization Reference?

You can contribute by providing feedback or suggestions through the project's GitHub repository.

Server Config

{
  "mcpServers": {
    "aws-service-authorization-reference": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "psantus86/aws-service-authorization-reference-mcp-server:latest"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
psantus
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago