Thalassa Cloud
Service accounts are non‑human identities designed for automated systems, applications, and integrations. In Thalassa Cloud, they are organisation‑level principals with their own roles and one or more access credentials. Use them for CI/CD pipelines, controllers, monitoring, provisioning, or any workload that needs programmatic access.
Service accounts separate machine access from human users, enabling least‑privilege policies, independent credential rotation, and clean audit trails. Each service account can hold multiple credentials, so you can rotate keys with zero downtime.
Service accounts in Thalassa Cloud are designed to be used across various scenarios. In CI/CD pipelines, they facilitate the deployment of infrastructure and applications with precisely scoped permissions. For automation, they are essential in managing scheduled jobs, operators, and controllers. They are perfect if you’re deploying your own Kubernetes clusters on Thalassa Cloud IaaS, when combining with our CSI or Cloud Controller Manager.
Additionally, in observability, service accounts provide read-only access to your Cloud services. This allows you to use the Prometheus Exporter for Thalassa Cloud to collect metrics and information about your Cloud usage.
It is easy to get started with Service Accounts. Simply;
Note: Make sure you have the permissions to manage service accounts and their access credentials. Your Organisation admin can adjust your role permissions if need be.
Learn more about Service accounts through our documentation.
