Create IAM policies (console)
A policy is an entity that, when attached to an identity or resource, defines their permissions. You can use the AWS Management Console to create customer managed policies in IAM. Customer managed policies are standalone policies that you administer in your own AWS account. You can then attach the policies to identities (users, groups, and roles) in your AWS account.
The number and size of IAM resources in an AWS account are limited. For more information, see IAM and AWS STS quotas.
Topics
Creating IAM policies
You can create a customer managed policy in the AWS Management Console using one of the following methods:
-
JSON — Paste and customize a published example identity-based policy.
-
Visual editor — Construct a new policy from scratch in the visual editor. If you use the visual editor, you do not have to understand JSON syntax.
-
Import — Import and customize a managed policy from within your account. You can import an AWS managed policy or a customer managed policy that you previously created.
The number and size of IAM resources in an AWS account are limited. For more information, see IAM and AWS STS quotas.
Creating policies using the JSON editor
You can type or paste policies in JSON by choosing the JSON option. This method is useful for copying an example policy to use in your account. Or, you can type your own JSON policy document in the JSON editor. You can also use the JSON option to toggle between the visual editor and JSON to compare the views.
When you create or edit a policy in the JSON editor, IAM performs policy validation to help you create an effective policy. IAM identifies JSON syntax errors, while IAM Access Analyzer provides additional policy checks with actionable recommendations to help you further refine the policy.
A JSON policy document consists of one or more
statements. Each statement should contain all the actions that share the same effect
(Allow or Deny) and support the same resources and conditions. If
one action requires you to specify all resources ("*") and another action
supports the Amazon Resource Name (ARN) of a specific resource, they must be in two separate
JSON statements. For details about ARN formats, see Amazon Resource Name (ARN) in the
AWS General Reference Guide. For general information about IAM policies, see
Policies and permissions in AWS Identity and Access Management. For information about the
IAM policy language, see IAM JSON policy reference.
To use the JSON policy editor to create a policy
Sign in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/
. -
In the navigation pane on the left, choose Policies.
-
Choose Create policy.
-
In the Policy editor section, choose the JSON option.
-
Type or paste a JSON policy document. For details about the IAM policy language, see IAM JSON policy reference.
-
Resolve any security warnings, errors, or general warnings generated during policy validation, and then choose Next.
Note
You can switch between the Visual and JSON editor options anytime. However, if you make changes or choose Next in the Visual editor, IAM might restructure your policy to optimize it for the visual editor. For more information, see Policy restructuring.
-
(Optional) When you create or edit a policy in the AWS Management Console, you can generate a JSON or YAML policy template that you can use in AWS CloudFormation templates.
To do this, in the Policy editor choose Actions, and then choose Generate CloudFormation template. To learn more about AWS CloudFormation see AWS Identity and Access Management resource type reference in the AWS CloudFormation User Guide.
-
When you are finished adding permissions to the policy, choose Next.
-
On the Review and create page, type a Policy Name and a Description (optional) for the policy that you are creating. Review Permissions defined in this policy to see the permissions that are granted by your policy.
-
(Optional) Add metadata to the policy by attaching tags as key-value pairs. For more information about using tags in IAM, see Tags for AWS Identity and Access Management resources.
-
Choose Create policy to save your new policy.
After you create a policy, you can attach it to your groups, users, or roles. For more information, see Adding and removing IAM identity permissions.
Creating policies with the visual editor
The visual editor in the IAM console guides you through creating a policy without having to write JSON syntax. To view an example of using the visual editor to create a policy, see Controlling access to identities.
To use the visual editor to create a policy
Sign in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/
. -
In the navigation pane on the left, choose Policies.
-
Choose Create policy.
-
In the Policy editor section, find the Select a service section, and then choose an AWS service. You can use the search box at the top to limit the results in the list of services. You can choose only one service within a visual editor permission block. To grant access to more than one service, add multiple permission blocks by choosing Add more permissions.
-
In Actions allowed, choose the actions to add to the policy. You can choose actions in the following ways:
-
Select the checkbox for all actions.
-
Choose add actions to type the name of a specific action. You can use wildcards (
*) to specify multiple actions. -
Select one of the Access level groups to choose all actions for the access level (for example, Read, Write, or List).
-
Expand each of the Access level groups to choose individual actions.
By default, the policy that you are creating allows the actions that you choose. To deny the chosen actions instead, choose Switch to deny permissions. Because IAM denies by default, we recommend as a security best practice that you allow permissions to only those actions and resources that a user needs. You should create a JSON statement to deny permissions only if you want to override a permission separately allowed by another statement or policy. We recommend that you limit the number of deny permissions to a minimum because they can increase the difficulty of troubleshooting permissions.
-
-
For Resources, if the service and actions that you selected in the previous steps do not support choosing specific resources, all resources are allowed and you cannot edit this section.
If you chose one or more actions that support resource-level permissions, then the visual editor lists those resources. You can then expand Resources to specify resources for your policy.
You can specify resources in the following ways:
-
Choose Add ARNs to specify resources by their Amazon Resource Names (ARN). You can use the visual ARN editor or list ARNs manually. For more information about ARN syntax, see Amazon Resource Name (ARN) in the AWS General Reference Guide. For information about using ARNs in the
Resourceelement of a policy, see IAM JSON policy elements: Resource. -
Choose Any in this account next to a resource to grant permissions to any resources of that type.
-
Choose All to choose all resources for the service.
-
-
(Optional) Choose Request conditions - optional to add conditions to the policy that you are creating. Conditions limit a JSON policy statement's effect. For example, you can specify that a user is allowed to perform the actions on the resources only when that user's request happens within a certain time range. You can also use commonly used conditions to limit whether a user must be authenticated using a multi-factor authentication (MFA) device. Or you can require that the request originate from within a certain range of IP addresses. For lists of all of the context keys that you can use in a policy condition, see Actions, resources, and condition keys for AWS services in the Service Authorization Reference.
You can choose conditions in the following ways:
-
Use checkboxes to select commonly used conditions.
-
Choose Add another condition to specify other conditions. Choose the condition's Condition Key, Qualifier, and Operator, and then type a Value. To add more than one value, choose Add. You can consider the values as being connected by a logical "OR" operator. When you are finished, choose Add condition.
To add more than one condition, choose Add another condition again. Repeat as needed. Each condition applies only to this one visual editor permission block. All the conditions must be true for the permission block to be considered a match. In other words, consider the conditions to be connected by a logical "AND" operator.
For more information about the Condition element, see IAM JSON policy elements: Condition in the IAM JSON policy reference.
-
-
To add more permission blocks, choose Add more permissions. For each block, repeat steps 2 through 5.
Note
You can switch between the Visual and JSON editor options anytime. However, if you make changes or choose Next in the Visual editor, IAM might restructure your policy to optimize it for the visual editor. For more information, see Policy restructuring.
-
(Optional) When you create or edit a policy in the AWS Management Console, you can generate a JSON or YAML policy template that you can use in AWS CloudFormation templates.
To do this, in the Policy editor choose Actions, and then choose Generate CloudFormation template. To learn more about AWS CloudFormation see AWS Identity and Access Management resource type reference in the AWS CloudFormation User Guide.
-
When you are finished adding permissions to the policy, choose Next.
-
On the Review and create page, type a Policy Name and a Description (optional) for the policy that you are creating. Review the Permissions defined in this policy to make sure that you have granted the intended permissions.
-
(Optional) Add metadata to the policy by attaching tags as key-value pairs. For more information about using tags in IAM, see Tags for AWS Identity and Access Management resources.
-
Choose Create policy to save your new policy.
After you create a policy, you can attach it to your groups, users, or roles. For more information, see Adding and removing IAM identity permissions.
Importing existing managed policies
An easy way to create a new policy is to import an existing managed policy within your account that has at least some of the permissions that you need. You can then customize the policy to match it to your new requirements.
You cannot import an inline policy. To learn about the difference between managed and inline policies, see Managed policies and inline policies.
To import an existing managed policy in the visual editor
Sign in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/
. -
In the navigation pane on the left, choose Policies.
-
Choose Create policy.
-
In the Policy editor , choose Visual and then on the right side of the page, choose Actions then choose Import policy.
-
In the Import policy window, choose the managed policies that most closely match the policy that you want to include in your new policy. You can use the search box at the top to limit the results in the list of policies.
-
Choose Import policy.
The imported policies are added in new permission blocks at the bottom of your policy.
-
Use the Visual editor or choose JSON to customize your policy. Then choose Next.
Note
You can switch between the Visual and JSON editor options anytime. However, if you make changes or choose Next in the Visual editor, IAM might restructure your policy to optimize it for the visual editor. For more information, see Policy restructuring.
-
On the Review and create page, type a Policy Name and a Description (optional) for the policy that you are creating. You cannot edit these settings later. Review the Permissions defined in this policy and then choose Create policy to save your work.
To import an existing managed policy in the JSON editor
Sign in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/
. -
In the navigation pane on the left, choose Policies.
-
Choose Create policy.
-
In the Policy editor section, choose the JSON option, and then on the right side of the page, choose Actions then choose Import policy.
-
In the Import policy window, choose the managed policies that most closely match the policy that you want to include in your new policy. You can use the search box at the top to limit the results in the list of policies.
-
Choose Import policy.
Statements from the imported policies are added to the bottom of your JSON policy.
-
Customize your policy in JSON. Resolve any security warnings, errors, or general warnings generated during policy validation, and then choose Next. Or, customize your policy in the Visual editor. Then choose Next.
Note
You can switch between the Visual and JSON editor options anytime. However, if you make changes or choose Next in the Visual editor, IAM might restructure your policy to optimize it for the visual editor. For more information, see Policy restructuring.
-
On the Review and create page, type a Policy Name and a Description (optional) for the policy that you are creating. You cannot edit these later. Review the policy Permissions defined in this policy and then choose Create policy to save your work.
After you create a policy, you can attach it to your groups, users, or roles. For more information, see Adding and removing IAM identity permissions.
