Skip to main content
Book a demo

Connect AWS Knowledge to Perplexity

Give Perplexity governed access to AWS Knowledge’s 5 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Perplexity setup guide

Set up

Add AWS Knowledge to Perplexity in four steps

Admins approve the server once. Everyone in Perplexity then gets it through the same governed connection.

  1. 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. 2

    Connect Perplexity to Runlayer

    Users add the Runlayer Plugin to Perplexity by following Runlayer’s setup guide. Perplexity reaches AWS Knowledge’s 5 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Perplexity setup guide
  3. 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. 4

    Use AWS Knowledge from Perplexity

    AWS Knowledge’s approved tools appear in Perplexity. Every call is checked against policy and recorded.

Tools

5 AWS Knowledge tools in Perplexity

Runlayer policy decides which of these Perplexity 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 Perplexity

Some controls apply to every client at the gateway. Others depend on what Perplexity exposes to Runlayer.

  • Gateway policy (available)

    Every AWS Knowledge call from Perplexity passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Perplexity as the client, the tool, and the policy and scanner decisions.

  • Managed browser extension (available)

    Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for Perplexity yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination