principal
The identity making a request, such as a user, a role session or a service, that an access policy allows or denies.
In more detail
Policies attached to a resource or a role must say which principal they cover; in AWS this goes in a Principal field. A service principal names a cloud service, such as ecs-tasks.amazonaws.com, that may act on your behalf. A too broad principal lets unexpected identities in.
Example
Policies name principals, and the course asks which permissions let a principal grant itself more, such as creating roles or attaching policies.Related terms
- trust policy — A JSON document on a cloud role that says who may assume the role and under which conditions.
- resource-based policy — An IAM policy attached to a resource, such as a bucket, queue or encryption key, that names which principals may use it.
- IAM role — A cloud identity with permissions but no password, which trusted users or workloads temporarily assume.
- IAM — Identity and Access Management: the cloud service that controls who can do what with which resources.
- request context — The information attached to a single request, such as who made it, when and from where, that code or access policies check while handling it.
- service account — An identity for a program rather than a person; in Kubernetes each pod runs as one and gets a signed token for it.
Taught in
- Security Sprint: Fifteen Questions' Worth — AWS Certified Cloud Practitioner (CLF-C02) Exam Prep
- Policy Evaluation: Deny Wins, And Both Accounts Must Agree — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Many Accounts: Organizations, SCPs And Control Tower — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Who Signs In: Identity Center, STS And Cognito — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Private Paths: VPC Endpoints And PrivateLink — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- The Edge: WAF, Shield, CloudFront And GuardDuty — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- KMS And Envelope Encryption: Who Can Still Decrypt? — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Long-Stem Clinic: The Phrase That Decides — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- The Full Mock And Your Review Plan — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- IAM as the Foundation — Cloud Infrastructure & Hyperscaler Architecture
- Users, Groups and Roles — Cloud Infrastructure & Hyperscaler Architecture
- Policies and Least Privilege — Cloud Infrastructure & Hyperscaler Architecture
- The Danger of Long-Lived Keys — Cloud Infrastructure & Hyperscaler Architecture
- Policy Simulation and Dry Runs — Cloud Infrastructure & Hyperscaler Architecture
- Subnets: Public and Private — Cloud Infrastructure & Hyperscaler Architecture
- S3: Permissions, Tiers, and Policies — Cloud Infrastructure & Hyperscaler Architecture
- Managed Relational Databases (RDS) — Cloud Infrastructure & Hyperscaler Architecture
- AWS Organizations, Account Hierarchies & Azure Management Groups — Cloud Security & DevSecOps Engineering
- Service Control Policies & Guardrail Architecture — Cloud Security & DevSecOps Engineering
- Cloud Network Isolation: VPC Peering & PrivateLink — Cloud Security & DevSecOps Engineering
- Cloud IAM Architecture & Permission Boundaries — Cloud Security & DevSecOps Engineering
- Workload Identity Federation: Eliminating Static Keys — Cloud Security & DevSecOps Engineering
- Cross-Account AssumeRole Chains & Temporary STS — Cloud Security & DevSecOps Engineering
- Least Privilege Enforcement & CIEM Architecture — Cloud Security & DevSecOps Engineering
- Threat Detection with GuardDuty & Anomaly Analytics — Cloud Security & DevSecOps Engineering
- Envelope Encryption & Data Protection with KMS — Cloud Security & DevSecOps Engineering
- Least Privilege In IAM And RBAC — Application Security & Threat Modeling for Engineers