> ## 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. # Amazon S3 > Connect Amazon S3 to xpander and give agents its 33 actions: how it signs in through the AWS Operator, and which actions to hold for approval. HTTP API connector An HTTP API described by an OpenAPI spec, not an MCP server. Calls go to `https://functions.stg.xpander.ai/aws-s3` 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: 33 actions, as they appear in the skill panel. 32 of them create, change or delete something in Amazon S3; mark those under **These actions need approval** when you add the skill to an agent. * **Object management** (10): Manage Copy Object Within S3, Manage Delete Object From Bucket, Manage List Objects With Filters, Manage Upload Object To Bucket, Bucket Manage Get Bucket Tags, Manage Download Object From Bucket, Manage Get Object Tags, Bucket Manage Set Bucket Tags, Manage Set Object Tags, Manage Generate Presigned Url * **Bucket management** (10): Manage Get Bucket Encryption, Manage Head Bucket Check, Manage Create New Bucket, Manage Get Bucket Acl, Manage Get Versioning, Manage Simple Health Check, Manage Get Bucket Cors, Manage Get Bucket Policy, Manage Get Public Access Block, Manage Get Lifecycle Configuration * **Security service** (7): Set Lifecycle Configuration, Set Public Access Block, Set Bucket Cors, Bucket Manage List All Buckets, Configure Bucket Encryption, Set Bucket Policy, Configure Versioning * **Analysis service** (5): Analyze Public Buckets, Analyze Bucket Content, Analyze Enhanced Public Buckets, Analyze Unencrypted Buckets, Search Pattern In Buckets * **Synchronization engine** (1): Delete Bucket ## Connect Amazon S3 In Xpander Chat, open the agent's settings, click **Add skill**, and search for **Amazon S3**. 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). Amazon S3 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://functions.stg.xpander.ai/aws-s3`. ## Give an agent the Amazon S3 skill Once Amazon S3 is connected, any agent you can edit may be given the skill: open the agent's settings, click **Add skill**, and choose **Amazon S3**. 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)