AWS
AWS is a first-class provider slug in the integration registry. The current product stores credentials, validates required fields, and exposes them to generic project and agent connectors.
Purpose
Configure AWS access in ActsAsGeek through the authenticated integration routes, then use the project monitoring, secret storage, and usage-ingestion surfaces that already exist in the product.
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
Bind the credential to a project or environment through the integrations settings surface.
3
Store any additional runtime secrets with /api/projects/[projectId]/env-secrets when the application needs environment-specific values.
API & contracts
| Field | Type | Description |
|---|---|---|
| aws | oauth2 · api_key | Provider slug accepted by the integration registry. |
- The verifier requires `access_key_id`, `secret_access_key`, and `default_region`.
- Project 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.
- Project binding fails when the selected credential is not in `connected` status.
Partial
Credential storage, verification, and connector binding are implemented. AWS-specific resource fetching and webhook handling are not implemented in the current codebase.