AWS Payment Cryptography identity-based policy examples
By default, IAM users and roles don't have permission to create or modify AWS Payment Cryptography resources. They also can't perform tasks using the AWS Management Console, AWS CLI, or AWS API. An IAM administrator must create IAM policies that grant users and roles permission to perform specific API operations on the specified resources they need. The administrator must then attach those policies to the IAM users or groups that require those permissions.
To learn how to create an IAM identity-based policy using these example JSON policy documents, see Creating Policies on the JSON Tab in the IAM User Guide.
Topics
Policy best practices
Identity-based policies determine whether someone can create, access, or delete AWS Payment Cryptography resources in your account. These actions can incur costs for your AWS account. When you create or edit identity-based policies, follow these guidelines and recommendations:
-
Get started with AWS managed policies and move toward least-privilege permissions – To get started granting permissions to your users and workloads, use the AWS managed policies that grant permissions for many common use cases. They are available in your AWS account. We recommend that you reduce permissions further by defining AWS customer managed policies that are specific to your use cases. For more information, see AWS managed policies or AWS managed policies for job functions in the IAM User Guide.
-
Apply least-privilege permissions – When you set permissions with IAM policies, grant only the permissions required to perform a task. You do this by defining the actions that can be taken on specific resources under specific conditions, also known as least-privilege permissions. For more information about using IAM to apply permissions, see Policies and permissions in IAM in the IAM User Guide.
-
Use conditions in IAM policies to further restrict access – You can add a condition to your policies to limit access to actions and resources. For example, you can write a policy condition to specify that all requests must be sent using SSL. You can also use conditions to grant access to service actions if they are used through a specific AWS service, such as AWS CloudFormation. For more information, see IAM JSON policy elements: Condition in the IAM User Guide.
-
Use IAM Access Analyzer to validate your IAM policies to ensure secure and functional permissions – IAM Access Analyzer validates new and existing policies so that the policies adhere to the IAM policy language (JSON) and IAM best practices. IAM Access Analyzer provides more than 100 policy checks and actionable recommendations to help you author secure and functional policies. For more information, see Validate policies with IAM Access Analyzer in the IAM User Guide.
-
Require multi-factor authentication (MFA) – If you have a scenario that requires IAM users or a root user in your AWS account, turn on MFA for additional security. To require MFA when API operations are called, add MFA conditions to your policies. For more information, see Secure API access with MFA in the IAM User Guide.
For more information about best practices in IAM, see Security best practices in IAM in the IAM User Guide.
Using the AWS Payment Cryptography console
To access the AWS Payment Cryptography console, you must have a minimum set of permissions. These permissions must allow you to list and view details about the AWS Payment Cryptography resources in your AWS account. If you create an identity-based policy that is more restrictive than the minimum required permissions, the console won't function as intended for entities (IAM users or roles) with that policy.
To ensure that those entities can still use the AWS Payment Cryptography console, also attach the following AWS managed policy to the entities. For more information, see Adding Permissions to a User in the IAM User Guide.
You don't need to allow minimum console permissions for users that are making calls only to the AWS CLI or the AWS API. Instead, allow access to only the actions that match the API operation that you're trying to perform.
Allow users to view their own permissions
This example shows how you might create a policy that allows IAM users to view the inline and managed policies that are attached to their user identity. This policy includes permissions to complete this action on the console or programmatically using the AWS CLI or AWS API.
{ "Version": "2012-10-17", "Statement": [ { "Sid": "ViewOwnUserInfo", "Effect": "Allow", "Action": [ "iam:GetUserPolicy", "iam:ListGroupsForUser", "iam:ListAttachedUserPolicies", "iam:ListUserPolicies", "iam:GetUser" ], "Resource": ["arn:aws:iam::*:user/${aws:username}"] }, { "Sid": "NavigateInConsole", "Effect": "Allow", "Action": [ "iam:GetGroupPolicy", "iam:GetPolicyVersion", "iam:GetPolicy", "iam:ListAttachedGroupPolicies", "iam:ListGroupPolicies", "iam:ListPolicyVersions", "iam:ListPolicies", "iam:ListUsers" ], "Resource": "*" } ] }
Ability to access all aspects of AWS Payment Cryptography
Warning
This example provides wide permissions and is not recommended. Consider least priviledged access models instead.
In this example, you want to grant an IAM user in your AWS account access to all of your AWS Payment Cryptography keys and the ability to call all AWS Payment Cryptography apis including both ControlPlane and DataPlane operations.
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "payment-cryptography:*" ], "Resource": [ "*" ] } ] }
Ability to call APIs using specified keys
In this example, you want to grant an IAM user in your AWS account access to one
of your AWS Payment Cryptography key, arn:aws:payment-cryptography:us-east-2:111122223333:key/kwapwa6qaifllw2h and then use this resource
in two APIs, GenerateCardData and VerifyCardData. Conversely,
the IAM user will not have access to use this key on other operations such as
DeleteKey or ExportKey
Resources can be either keys,
prefixed with key or aliases, prefixed with alias.
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "payment-cryptography:VerifyCardData", "payment-cryptography:GenerateCardData" ], "Resource": [ "arn:aws:payment-cryptography:us-east-2:111122223333:key/kwapwa6qaifllw2h" ] } ] }
Ability to specifically deny a resource
Warning
Carefully consider the implications of granting wildcard access. Consider a least privilege model instead.
In this example, you want to permit an IAM user in your AWS account access to
any of your AWS Payment Cryptography key but want to deny permissions to one specific key. The user will have
access to VerifyCardData and GenerateCardData with all keys
with the exception of the one specified in the deny statement.
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "payment-cryptography:VerifyCardData", "payment-cryptography:GenerateCardData" ], "Resource": [ "arn:aws:payment-cryptography:us-east-2:111122223333:key/*" ] }, { "Effect": "Deny", "Action": [ "payment-cryptography:GenerateCardData" ], "Resource": [ "arn:aws:payment-cryptography:us-east-2:111122223333:key/kwapwa6qaifllw2h" ] } ] }
