agents-connect

Wire AgentCore agents to external APIs via Gateway with Cedar policy protection.

2.3k|234|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/aws/agent-toolkit-for-aws --skill agents-connect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agents-connect
Source: https://github.com/aws/agent-toolkit-for-aws/tree/main/plugins/aws-agents/skills/agents-connect
Command: npx skills add https://github.com/aws/agent-toolkit-for-aws --skill agents-connect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Use when connecting your agent to external APIs, tools, or services via Gateway, or restricting tool access with Cedar policies. Handles gateway setup, target types, outbound auth (OAuth, API key, IAM), credentials, and Cedar policy authoring. Triggers on: "connect to API", "add gateway", "connect to MCP server", "Lambda tools", "OpenAPI", "gateway target", "Cedar policy", "restrict tools", "policy engine", "gateway auth error", "store API key", "outbound credential", "env var API key", "API key None after deploy", "credential not available after deploy", "should this be a gateway target", "give my agent tools", "add tools to agent". Not for inbound auth (who can call your agent) — use agents-harden. Not for debugging agent behavior — use agents-debug. Not for VPC networking errors (agent can't reach APIs due to VPC) — use agents-build. Not for creating or hosting a new MCP server project — use agents-get-started. Note: The skill coordinates gateway setup, target typing, outbound credentials, and Cedar policy authoring to securely expose tools and APIs to agents.

Core Features & Use Cases

  • Gateway setup and target typing for external tools and services
  • Multiple outbound auth methods (none, oauth, api-key, iam)
  • Cedar policy authoring and enforcement at the gateway boundary
  • Support for MCP servers, Lambda functions, OpenAPI, API Gateway, and Smithy targets
  • Credential management and secure exposure of tools to agents

Quick Start

Connect your agent to external APIs via Gateway and configure Cedar policies to control access.

Frequently Asked Questions about agents-connect

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

FAQPage Schema
How do I connect my agent to an external API via a gateway?

To connect your agent to an external API, you wire it through a gateway by defining target types such as OpenAPI or Lambda, and configuring outbound authentication options like OAuth or API key.

How do I restrict agent tool access using Cedar policies?

You restrict agent tool access by authoring Cedar policies that enforce edge-based authorization at the gateway boundary, controlling which tools and APIs the agent can securely discover and invoke.

What outbound authentication methods can I configure for my gateway?

Supported outbound authentication methods include none, OAuth, API key, and IAM, enabling secure credential management and access when connecting agents to external services and APIs.

Does the gateway support connecting agents to MCP servers and Lambda functions?

Yes, the gateway supports MCP servers and Lambda functions as target types, alongside OpenAPI, API Gateway, and Smithy, allowing you to securely expose diverse external tools to your agent.

Why is my API key showing as None after deploying the gateway?

If your API key is None after deploy, it indicates a credential management issue. You must properly configure outbound credentials and store the API key correctly so the gateway can expose it to the agent.