Integrations and operations
Manage model access, compute, and operating limits. Portfolio governance remains separate from developer execution and production release authority.
At a glance
The controls on this page change model policy or hourly compute state. Project and run evidence remain in the Studio so each operating action stays separate from source editing and deployment.
Operations do not approve source
Compute and provider switches are distinct from candidate approval. Inspect governed run evidence before recording a review head or deliberately reconciling it into canonical source.
Open evidence room →Provider basket
Permission is separate from authentication
These switches only admit a reviewed adapter to the model shelf. Provider login remains local to the encrypted workstation, and the browser, Lambda, DynamoDB, and S3 never receive a provider token.
Control-plane posture
Operating guardrails
- The API accepts only tokens issued for this application client and then requires
ProjectOwnerorPlatformAdmin. - Administrative endpoints additionally require
PlatformAdmin. - GPU jobs remain impossible until the optional Batch stack is connected and the account’s GPU Spot quota is raised from zero.
- Worker timeouts are one hour for CPU and four hours for GPU; every job uses a single attempt.
- There is no NAT gateway, load balancer, OpenSearch domain, RDS instance, or permanently running EC2 instance.
Current GPU planning range
The account’s 31 July 2026 Spot sample in us-east-1 ranged from about $0.29/hour for g4dn.xlarge to $0.96/hour for g5.xlarge, before storage and public IPv4 charges. Spot prices vary by Availability Zone and time; verify immediately before enabling a run.
aws ec2 describe-spot-price-history \
--profile categorise --region us-east-1 \
--instance-types g4dn.xlarge g5.xlarge g6.xlarge \
--product-descriptions 'Linux/UNIX' --max-items 20