Claude Tag is in public beta. Features and behavior described here may change before general availability.
Where federated connections work
Federated connections are available to Claude in Slack channels, where it acts under your organization’s agent identity. They aren’t available in one-to-one direct messages, which run on the individual’s own claude.ai account, and they need an Anthropic-hosted environment; Claude can’t use them in a self-hosted environment.Identity token
Gateways
AWS roles
Google Cloud identities
What the credential-minting block refuses
With Block requests that mint new credentials on, Agent Proxy refuses these requests before they reach Google, whatever IAM would allow (current behavior, may change):- Every request to these services, whether the service is named in the host or in the path: Security Token Service, IAM, IAM Service Account Credentials, API Keys, Firebase Authentication (Identity Toolkit and Secure Token), Cloud Workstations, Cloud SQL Admin, AlloyDB, Connect Gateway, GKE Hub, Certificate Authority Service, Identity-Aware Proxy, Apigee, Secret Manager, Parameter Manager, OS Login, Cloud Shell, Cloud Identity, the Google Workspace Admin SDK, Cloud KMS, Cloud Tasks, Cloud Scheduler, Eventarc, Workflows and Workflow Executions, API Gateway, Application Integration, Deployment Manager, Cloud Build, Cloud Composer, Dataform, AI Platform Training and Prediction, Google Kubernetes Engine, Dataproc, OS Config, Dialogflow, Storage Transfer Service, BigQuery Data Transfer Service, and Vertex AI Workbench.
- On every other Google service, methods whose response carries a credential or signature, matched by method name. For example
generate,refresh, orexchangemethods ending inToken,Cert,Certificate,Credential,Credentials,Url,Secret,Password, orKey, andexchangeAppAttestAssertionandexchangeAppAttestAttestation(Bigtable’sgenerateConsistencyToken, which returns no credential, passes). - Signing methods:
sign,signJwt,signBlob,signSshPublicKey, and theirasymmetric,mac, andrawforms. show,reset, orretrievemethods ending inCredential,Credentials,Password,Secret, orSecretKey, plusaddorimportmethods ending inPublicKey, and methods starting withsignUporsignIn.setIamPolicyon any resource, and Compute EnginesetMetadata,setCommonInstanceMetadata,updatePerInstanceConfigs,patchPerInstanceConfigs, instance updates, and instance settings writes.- Cloud Storage IAM and ACL writes, and HMAC key creation.
- IAM service account key creation and upload; API Keys
keyStringand MemorystoreauthStringreads. - Pub/Sub subscription creation, update, and
modifyPushConfig, and Cloud Monitoring uptime check creation and changes. - Google’s OAuth 2.0 token endpoint (
oauth2.googleapis.com/token), HTTP batch requests (a path that starts with/batch), and any request framed as gRPC, gRPC-Web, or$rpc.
getIamPolicy, testIamPermissions, and tokeninfo pass. If Claude needs one of the refused services, clear the checkbox on that connection and rely on IAM alone.
Shared cloud hosts
A host such ass3.us-east-1.amazonaws.com or storage.googleapis.com serves every customer of that cloud, so the allowed hosts limit which services Claude calls, not which accounts or projects it reaches.
- AWS roles: Claude can reach a resource in another AWS account when the role’s permissions policy and that resource’s policy both allow it. To keep the role inside your organization, name your own resources in the policy or add an
aws:ResourceOrgIDcondition. For S3, you can also allow only your bucket’s host, such asexample-reports.s3.us-west-2.amazonaws.com. - Google Cloud identities: Claude can reach a resource in any project that grants the identity access, including a project outside your organization. To limit that reach for the permissions Google lists, bind a Principal Access Boundary policy. Allow only the hosts of the services Claude needs.
- Provider-wide wildcards:
*.amazonaws.comand*.googleapis.comallow every host under that domain, including hosts the channel’s environment doesn’t allow. Check each connection in the Allowed hosts column of the Cloud roles table, and replace the wildcard in the Edit connection dialog.
Authorization servers
Testing
The console’s connection check is the only way to have Anthropic send a token to your gateway before Claude does. There is no way to request a test token for your own use. To test end to end, follow the Verify step on each connection page.Related resources
- Identity token reference: claims, issuer, keys, and rotation
- Connect a gateway
- Connect an AWS role
- Connect a Google Cloud identity
- Connect an authorization server
- Network requirements: Anthropic’s egress range and internet reachability