Cua Fleets Adds Expiring Signed Links for Sandbox Services
- Source
- Cua
- 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.
- A signed URL targets a service declared on the pool template, and requests route to that named service on the bound .
- The link does not keep the sandbox alive: the sandbox claim must stay bound for the whole sharing window, for example expiresInSeconds: 3600 for a one-hour demo.
- Anyone holding the URL can reach the service until it expires or is revoked, so Cua says to treat it like a credential. Signed URLs must be enabled in the Fleet environment.
Cua Fleets now lets you generate an expiring, revocable link to a single service inside an sandbox, useful for sharing a live demo or giving temporary external access without keeping credentials open.
Checking sign-in…
Loading comments…