KodeKloud Notes

In AWS Identity and Access Management (IAM), policies are JSON documents that grant or deny permissions. Understanding the core components—Effect, Action, Resource, Condition, and Principal—allows you to craft fine-grained access controls.

Key Policy Elements

Element	Description	Example
Effect	Whether to Allow or Deny the specified action	`"Effect": "Allow"`
Action	One or more AWS API operations	`"s3:GetObject"`, `"ec2:StartInstances"`
Resource	Amazon Resource Names (ARNs) targeted by policy	`"arn:aws:s3:::my-bucket/*"`
Condition	Optional restrictions (time, IP address, MFA)	`"DateLessThan": {"aws:CurrentTime":"09:00:00Z"}`
Principal	Who the policy applies to (users, services)	`"Principal":{"Service":"lambda.amazonaws.com"}`

The image illustrates the structure of IAM policies in JSON format, detailing components like effect, actions, resources, conditions, and principal.

Example: Resource-Based Policy with Time and IP Conditions

This resource-based policy denies all actions on all resources unless the request originates from specified IP ranges and occurs between 09:00–17:00 UTC:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Deny",
      "Action": "*",
      "Resource": "*",
      "Condition": {
        "NotIpAddress": {
          "aws:SourceIp": [
            "203.0.113.0/24",
            "198.51.100.0/24"
          ]
        },
        "DateLessThan": {
          "aws:CurrentTime": "2023-01-01T09:00:00Z"
        },
        "DateGreaterThan": {
          "aws:CurrentTime": "2023-01-01T17:00:00Z"
        }
      }
    }
  ]
}

Note

AWS IAM requires full ISO 8601 date/time strings (for example, 2023-01-01T09:00:00Z). To enforce recurring daily time constraints, consider pairing policies with AWS Lambda functions or scheduled Amazon CloudWatch Events.

Policy Breakdown

Effect: Deny all actions when conditions aren’t met.
NotIpAddress: Blocks requests outside the trusted IP CIDRs.
DateLessThan and DateGreaterThan: Restrict access before 09:00 UTC or after 17:00 UTC.

Demo Scenario: Enforcing Access Hours

Sarah supervises a team of junior solution architects and needs to limit their administrative tasks to business hours from managed networks. Follow these steps in the AWS IAM console:

Open Policies and choose Create policy.
Paste the JSON above, adjust the IP ranges, and set your UTC window.
Review, name the policy (e.g., RestrictedBusinessHours), and save.
Attach this policy to the IAM group or role for Sarah’s team.

Now, any API call outside 09:00–17:00 UTC or from unapproved IP ranges will be denied automatically.

References

Watch Video

Watch video content