@zboule/wasp-infra

WaspAgent deploys wasp into your AWS account with SST v3: the AgentCore runtime and its image, the table and bucket that keep threads, a KMS key, the waker, and IAM built for a hostile sandbox.

import { WaspAgent } from '@zboule/wasp-infra';

const agent = new WaspAgent('Agent', {
  claudeCredentialsParameter: '/my-app/claude', // SSM SecureString: {"CLAUDE_CODE_OAUTH_TOKEN":"…"} or {"ANTHROPIC_API_KEY":"…"}
  definition: 'agent',                          // agent/prompt.md
  flavor: 'browser'                             // adds Chromium to the sandbox
});
new sst.aws.Function('Api', { handler: 'src/api.handler', link: [agent] });

Browsers upload files straight to the bucket. Set allowedOrigins: ['https://app.example.com'] to restrict which pages may send them (default: any origin; the presigned POST is what authorises an upload).

Your sst.config.ts must list the aws-native (1.72.0), docker-build (>= 0.0.14) and time (0.1.1) providers. Deploying builds a linux/arm64 image, so Docker must be running.