Container Registry & per-bucket S3 access keys
Two new ways to control private artifacts on DanubeData: a managed Container Registry for your Docker images, and per-bucket scoped access keys so each application credential is restricted to exactly the buckets and permissions it needs.
What's changed
- Container Registry — push and pull private Docker/OCI images via cr.danubedata.ro with per-team isolation, no node setup required
- Container Registry — create scoped access tokens for CI/CD pipelines, with separate push and pull credentials
- Container Registry — anti-abuse limits and quota tracking included; bundled storage in your team plan
- S3 access keys — choose between Team-wide (default, full access to every bucket) and Specific buckets (per-bucket, per-level grants) when creating a key
- S3 access keys — per-bucket permission levels: Read-only, Read-write, or Full (admin)
- S3 access keys — scoped keys are enforced at the storage backend itself via bucket policies, not just in the dashboard, so the restriction holds wherever the key is used
- S3 access keys — create directly from a bucket detail page to scope a key to that bucket, or from Account → Security → S3 Credentials to span multiple buckets
- S3 access keys — Set an optional expiry date and the key will be auto-revoked after the date