Service account
A service account is a non-human identity or account used by software, services, or automated processes to authenticate and access authorized resources.
Effective Platform Engineering
A service account is a non-human identity used by software or automation to access resources and perform authorized actions.
- How it is used
- Provides a team-managed identity for infrastructure and deployment automation without depending on an employee’s personal token.
- How deep it goes
- Explains ownership, AWS role assumption, least-privilege permissions, provisioning, and credential rotation through a pipeline implementation pattern.
- Examples
- Illustrates AWS IAM service accounts assuming environment-specific roles and a scheduled pipeline rotating credentials.
- What you can do after
- Operate/configure it by giving pipelines dedicated roles, storing credentials in team secrets, and automating rotation.
Read how Effective Platform Engineering explains service account →
Acing the Certified Kubernetes Administrator Exam, Second Edition
A Service Account is a Kubernetes API resource representing an identity usable by workloads and other cluster clients.
- How it is used
- Provides pod workloads with an identity for authenticating to the Kubernetes API.
- How deep it goes
- Works through default-account discovery, token mounts, automount disablement, role binding, and permission checks without detailing token generation internals.
- Examples
- Uses namespace and pod inspections, a disabled-automount manifest, a role binding, and `kubectl auth can-i`.
- What you can do after
- Operate/configure it with `kubectl` and YAML to assign pod identities, control token mounting, grant permissions, and verify access.
Cyber Threat Hunting
A service account is a non-human identity used by software workloads or services to authenticate and access resources.
- How it is used
- Supports threat hunting by attributing Kubernetes API calls and identifying unexpected workload identities.
- How deep it goes
- Works through audit searches, permission checks, and RoleBinding-change review rather than service-account implementation internals.
- Examples
- Uses a namespace default account, Kubernetes API event searches, kubectl authorization checks, and RoleBinding audit records.
- What you can do after
- Diagnose/debug with it by tracing API activity to an account, checking its permissions, and reviewing authorization changes.
Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform
A service account is a non-human identity used by software or automated processes to authenticate and access resources.
- How it is used
- Uses service accounts to authenticate automated infrastructure and applications while granting controlled access to resources.
- How deep it goes
- Traces permissions, configuration drift, resource dependencies, state imports, and safe IaC extraction without detailing identity internals.
- Examples
- Uses GCP project IAM, a promotions service account, Cloud SQL Auth proxy access, Terraform state import, and drift checks.
- What you can do after
- Diagnose service-account failures, verify effective permissions, trace dependencies, and refactor managed IAM resources without disrupting live infrastructure.
Road to Kubernetes
A Kubernetes service account is an identity for processes running in a cluster that can be granted permissions to access Kubernetes resources.
- How it is used
- Authenticates kubectl and automated workflows so they can access and manage Kubernetes cluster resources.
- How deep it goes
- Defines authentication, kubeconfig use, and deployment prerequisites, but defers service-account creation and advanced security management.
- Examples
- Demonstrates a GitHub Actions workflow that loads kubeconfig, verifies access, applies manifests, and restarts Deployments.
- What you can do after
- Operate/configure kubectl and GitHub Actions with a service account, kubeconfig file, and appropriate cluster permissions.
Kubernetes for Developers
A Kubernetes ServiceAccount is an identity and credential object intended for workloads that access the Kubernetes API.
- How it is used
- Grants in-cluster workloads controlled access to the Kubernetes API through RBAC bindings.
- How deep it goes
- Explains the workload identity role and RBAC-binding pattern, while stopping short of a complete ServiceAccount manifest.
- Examples
- Uses a monitoring Pod inspecting another Deployment and contrasts distributed developer certificates with federated human identities.
- What you can do after
- Apply it via RBAC to authorize in-cluster code while preserving identity-system control for human access.
Read how Kubernetes for Developers explains service account →
.NET MAUI in Action
A service account is a non-human identity used by software to authenticate to cloud or application services.
- How it is used
- Authenticates automated deployment workflows that upload signed builds to Google Play.
- How deep it goes
- Defines creation, role assignment, key generation, secret storage, and workflow use, but does not detail key rotation.
- Examples
- Uses a GCP_SERVICE_ACCOUNT secret to authenticate an Android AAB upload action.
- What you can do after
- Operate a GitHub Actions job that uploads signed Android artifacts to Google Play.
Google Anthos in Action
A Kubernetes service account is a namespace-scoped Kubernetes identity that supplies credentials and permissions to workloads or users.
- How it is used
- Supports token-based authentication, RBAC authorization, external-cluster registration, and Google Cloud operational integrations.
- How deep it goes
- Demonstrates account creation, role bindings, token extraction, kubeconfig use, and separation of Google Cloud roles.
- Examples
- Uses kubectl account and binding commands, a token-extraction command, and an external-cluster kubeconfig template.
- What you can do after
- Operate/configure token-based cluster login by creating a KSA, binding RBAC roles, and supplying its token through kubeconfig.
100 SQL Server Mistakes and How to Avoid Them
A service account is a noninteractive identity used by a software service to access operating-system or network resources.
- How it is used
- Frames service accounts as a SQL Server security-strategy decision involving privilege, manageability, password rotation, and compromise scope.
- How deep it goes
- Compares fine-grain and coarse-grain strategies with scale, rotation, synchronization, lateral-movement, and compromise consequences, but stops before implementation details.
- Examples
- Uses three servers with nine services and a 200-instance estate requiring 400 accounts to demonstrate granularity trade-offs.
- What you can do after
- Evaluate service-account granularity against password rotation, coordination effort, lateral movement, and compromise blast radius.
Read how 100 SQL Server Mistakes and How to Avoid Them explains service account →
Machine Learning for Tabular Data: XGBoost, Deep Learning, and AI
A service account is a non-human identity that applications or automated services use to authenticate and access authorized cloud resources.
- How it is used
- Automates authentication for Vertex AI machine-learning pipelines that must run without individual manual intervention.
- How deep it goes
- Explains creation, role assignment, key setup, and delegated access, while deferring detailed credential documentation.
- Examples
- Uses a Kuala Lumpur real-estate prediction pipeline and Google Cloud Console role-assignment walkthroughs as concrete examples.
- What you can do after
- Operate/configure an authenticated Vertex AI pipeline by creating an identity, assigning roles, supplying its key, and granting delegated access.
Related concepts
- accountkind of · An account is a record associated with a person, organization, or other entity that represents an identity or relationship, or tracks financial holdings and activity.
- principle of least privilegeconfigured by · The principle of least privilege is a security principle that grants each user, process, or other subject only the access rights necessary for its authorized tasks.
- group managed service accountincludes · A group managed service account is an Active Directory service identity whose password is automatically managed and usable by services on authorized computers.
- xp_cmdshellused by · xp_cmdshell is a SQL Server system procedure that executes operating-system commands from within SQL Server.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.