Identity Types: Users, Groups, and Service Accounts
You'll learn the three fundamental identity types in cloud IAM and when to use each one for secure access control.
Understanding Cloud Identity Types
Cloud IAM manages three distinct types of identities, each serving different purposes in your security model:
Users (Human Identities)
Users represent individual people who need access to cloud resources. Each user typically has unique credentials (username/password, MFA tokens) and should map to exactly one person. Think of users like individual employee badges — each person gets their own, never shared.
Common use cases:
- Developers accessing the cloud console
- Administrators managing resources
- Analysts running queries or generating reports
Groups (Collections of Users)
Groups bundle multiple users together for easier permission management. Instead of assigning permissions to 50 developers individually, you assign them once to a "Developers" group. Groups are like department mailing lists — you send to one address, and everyone in that department receives access.
Benefits:
- Simplified permission management at scale
- Consistent access control across teams
- Easier onboarding and offboarding
Service Accounts (Non-Human Identities)
Service accounts represent applications, containers, or automated processes — not people. A container running your API needs credentials to access a database, but it's not a human logging in. Service accounts provide these non-human identities with the credentials and permissions they need.
Critical differences from users:
- No interactive login or password
- Used by code, not people
- Often long-lived and need extra monitoring
- Should follow principle of least privilege strictly
Key Takeaway: Users are for people, groups simplify managing multiple users, and service accounts are for applications and automation. Never use a human user account for service-to-service authentication, and never share user credentials across people.