Connect AWS Knowledge to Warp
Give Warp governed access to AWS Knowledge’s 5 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add AWS Knowledge to Warp in four steps
Admins approve the server once. Everyone in Warp then gets it through the same governed connection.
- 1
Add AWS Knowledge to Runlayer
AWS Knowledge isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect Warp to Runlayer
Users add the Runlayer Plugin to Warp by following Runlayer’s setup guide. Warp reaches AWS Knowledge’s 5 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Warp setup guide - 3
Sign in to AWS Knowledge
Sign in the way AWS Knowledge requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use AWS Knowledge from Warp
AWS Knowledge’s approved tools appear in Warp. Every call is checked against policy and recorded.
Tools
5 AWS Knowledge tools in Warp
Runlayer policy decides which of these Warp users can call.
Get regional availability
AWS resource availability per region.
List regions
Retrieve a list of all AWS regions.
Read documentation
Fetch full AWS doc pages as markdown.
Retrieve skill
Retrieve an AWS skill (workflows, references).
Search documentation
AWS docs search.
Control
What Runlayer can see and stop in Warp
Some controls apply to every client at the gateway. Others depend on what Warp exposes to Runlayer.
Gateway policy (available)
Every AWS Knowledge call from Warp passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Warp as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Warp yet, so control happens at the gateway.
Frequently asked questions
Connect more