AWS
The integration registry includes AWS. The product stores credentials, checks required fields, and makes them available to generic Environment and agent connectors.
Purpose
Store AWS credentials and bind them to an Environment. Live provider verification, resource retrieval, and cloud actions are unavailable.
Prerequisites
- A signed-in Supabase session.
- A CSRF token for POST and PATCH requests.
- AWS credential material for the current UI fields: access_key_id, secret_access_key, and default_region.
Setup
1
Create the credential with POST /api/integrations using provider `aws` and auth_type `api_key` when you are using the current settings UI flow.
2
Use Integrations settings to bind the credential to an Environment.
3
Store runtime secrets for this Environment with /api/projects/[projectId]/env-secrets when the application needs them.
API & contracts
| Field | Type | Description |
|---|---|---|
| aws | api_key | Provider slug accepted by the integration registry. |
- The verifier requires `access_key_id`, `secret_access_key`, and `default_region`.
- A connected status records saved credentials. It does not prove provider access.
- Environment connector bindings accept the `aws` connector type.
- The current agentic connector registry uses a generic API-key connector for AWS rather than an AWS-specific resource fetcher.
Failure modes
- POST /api/integrations returns 400 for unsupported auth types or missing credential fields.
- Mutation routes return 401 without a session and 403 when the CSRF token is missing.
- Environment binding fails when the selected credential is not in `connected` status.
Partial
The product stores credentials, validates fields, and binds Connectors. Field validation does not contact the provider or confirm permissions. AWS-specific resource fetching and webhook handling are not implemented in the current codebase.