Cua Fleets Adds Expiring Signed Links for Sandbox Services
- Source
- x.com
- Date
1/ Cua Cloud Fleets now supports temporary, revocable links to individual sandbox services. Share a service. Set an expiry. Revoke access. Explore Fleets: https://t.co/q4Cc9z9GOp Here's how it works.
2/ Need someone or another system to reach a service in your sandbox? Create a signed URL for a service declared on your pool template. Requests route to that named service on the bound sandbox.
3/ Choose an expiry from 1 minute to 24 hours. Sharing a demo for an hour? Set expiresInSeconds: 3600. Keep the sandbox claim bound while sharing. The link doesn't keep it alive.
4/ Done sharing? Revoke the link. Anyone with the URL can access the service until it expires or is revoked. Treat the link like a credential and share it only with the intended recipients.
Context
Cua says its Cloud Fleets sandboxes now support temporary, revocable links to individual services running inside a . A link is a signed URL for one service declared on the sandbox's pool template. Requests route only to that named service on the bound sandbox, and the expiry is chosen from 1 minute to 24 hours.
Cua's example is sharing a demo for an hour. The sandbox claim has to stay bound while the link is shared, because the link does not keep it alive. Anyone with the URL can reach the service until it expires or is revoked, so Cua says to treat the link like a credential and share it only with intended recipients. Links are created, listed and revoked with the TypeScript Fleet SDK and require signed URLs to be enabled in the Fleet environment.
- sandbox — An isolated environment where AI-generated code or agent actions run without being able to touch anything real.
Checking sign-in…
Loading comments…