> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xpander.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# AWS SSO

> Connect AWS SSO to xpander and give agents its 3 actions: how it signs in through the AWS Operator, and which actions to hold for approval.

<Badge color="blue">HTTP API connector</Badge>

An HTTP API described by an OpenAPI spec, not an MCP server. Calls go to `https://api.archive.org/search/v1` and carry a signature from the AWS Operator's IAM role in your cluster, so there is no key to paste.

## What the skill can do

API connector: 3 actions, as they appear in the skill panel. 0 of them create, change or delete something in AWS SSO; mark those under **These actions need approval** when you add the skill to an agent.

* **Search service** (3): Internet Archive Field Management Get Searchable Fields, Internet Archive Search Service Perform Relevance Based Search, Internet Archive Result Scraping Retrieve Results With Cursor

## Connect AWS SSO

In Xpander Chat, open the agent's settings, click **Add skill**, and search for **AWS SSO**. The connect dialog asks for a connection name and whether the connection is for the **Organization** (one shared account) or **Personal** (your own account, so the agent acts with your permissions where systems allow). On an agent other people use, a personal connection runs their requests as you unless the binding requires each person's own sign-in; see [whose credential a shared agent uses](/use/agents/permissions#whose-credential-a-shared-agent-uses).

AWS SSO is served by the AWS Operator in your cluster and signs its calls with the pods' own AWS identity; there is no key to paste. The IAM setup is on [AWS Operator](/self-hosted/aws-operator).

Calls go to `https://api.archive.org/search/v1`.

## Give an agent the AWS SSO skill

Once AWS SSO is connected, any agent you can edit may be given the skill: open the agent's settings, click **Add skill**, and choose **AWS SSO**. Enable only the action groups the agent needs, and mark the actions that should wait for a named person's sign-off under **These actions need approval**. Which skills exist for your organization, and who may add them, is decided by your admins; see [Skills](/use/skills).

## Related Resources

* [Skills](/use/skills)
