Guides / Use your own cloud
Use your own cloud
Connect AWS Bedrock through a role you control. Caps and receipts stay the same.
For: A team with AWS credits that wants Claude billed to its own AWS account.
npm run dev does not wire it yet: there the routes answer 503 cloud_unavailable. Try the flow in the sandbox Clouds screen.Your AWS account pays for Claude on Bedrock (AWS Activate credits count). Petrova charges 5% of list price above the first $3,000 of list-price use each month; the first $3,000 is free. Caps, receipts and your tool settings stay the same. A connected account runs only on its own AWS: it never falls back to Petrova's suppliers.
Get your external id and the stack link
curl -s http://127.0.0.1:4100/v1/clouds/aws -H "authorization: Bearer $ADMIN_KEY" # needs cloud:writeOpen
quick_create_url. It creates a role frominfra/aws/petrova-bedrock-role.yamlthat can only call Anthropic models and read inference profiles, and only Petrova with your external id can use it. Copy theRoleArnoutput.Paste the role back
curl -s -X POST http://127.0.0.1:4100/v1/clouds/aws -H "authorization: Bearer $ADMIN_KEY" -H 'content-type: application/json' \ -d '{"role_arn":"arn:aws:iam::123456789012:role/PetrovaBedrockAccess","external_id":"ptrv-..."}'Check it works
curl -s -X POST http://127.0.0.1:4100/v1/clouds/aws/verify -H "authorization: Bearer $ADMIN_KEY"Petrova assumes the role and sends a one-token call to Opus 5.5 and Sonnet 5.5.
access_deniedmeans Amazon's one-time model access form is needed;throttledmeans a low starting quota.To stop
curl -s -X DELETE http://127.0.0.1:4100/v1/clouds/aws -H "authorization: Bearer $ADMIN_KEY"Or delete the CloudFormation stack.
What can go wrong
external_id_mismatch: paste the external id Petrova gave you, not a new one.invalid_role: the ARN is not a role ARN.cloud_not_connected: paste the role before you verify.
Next
Checked against the code on 16 November 2026.