Amazon Verified Permissions
Amazon Verified Permissions is a permissions management service from Amazon Web Services. You can use Verified Permissions to manage permissions for your…
Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.
Overview
Amazon Verified Permissions is a permissions management service from Amazon Web Services. You can use Verified Permissions to manage permissions for your application, and authorize user access based on those permissions. Using Verified Permissions, application developers can grant access based on information about the users, resources, and requested actions. You can also evaluate additional information like group membership, attributes of the resources, and session context, such as time of request and IP addresses. Verified Permissions manages these permissions by letting you create and store authorization policies for your applications, such as consumer-facing web sites and enterprise business systems. Verified Permissions uses Cedar as the policy language to express your permission requirements. Cedar supports both role-based access control (RBAC) and attribute-based access control (ABAC) authorization models. For more information about configuring, administering, and using Amazon Verified Permissions in your applications, see the Amazon Verified Permissions User Guide . For more information about the Cedar policy language, see the Cedar Policy Language Guide . When you write Cedar policies that reference principals, resources and actions, you can define the unique identifiers used for each of those elements. We strongly recommend that you follow these best practices: Use values like universally unique identifiers (UUIDs) for all principal and resource identifiers. For example, if user jane leaves the company, and you later let someone else use the name jane , then that new user automatically gets access to everything granted by policies that still reference User::"jane" . Cedar can’t distinguish between the new user and the old. This applies to both principal and resource identifiers. Always use identifiers that are guaranteed unique and never reused to ensure that you don’t unintentionally grant access because of the presence of an old identifier in a policy. Where you use a UUID for an entity, we recommend that you follow it with the // comment specifier and the ‘friendly’ name of your entity. This helps to make your policies easier to understand. For example: principal == User::"a1b2c3d4-e5f6-a1b2-c3d4-EXAMPLE11111", // alice Do not include personally identifying, confidential, or sensitive information as part of the unique identifier for your principals or resources. These identifiers are included in log entries shared in CloudTrail trails. Several operations return structures that appear similar, but have different purposes. As new functionality is added to the product, the structure used in a parameter of one operation might need to change in a way that wouldn't make sense for the same parameter in a different operation. To help you understand the purpose of each, the following naming convention is used for the structures: Parameter type structures that end in Detail are used in Get operations. Parameter type structures that end in Item are used in List operations. Parameter type structures that use neither suffix are used in the mutating (create and update) operations.
Endpoints 34
Policy store
- POSTBatch get policy
/#X-Amz-Target=VerifiedPermissions.BatchGetPolicyRetrieves information about a group (batch) of policies. The BatchGetPolicy operation doesn't have its own IAM permission. To authorize this operation for… - POSTBatch is authorized
/#X-Amz-Target=VerifiedPermissions.BatchIsAuthorizedMakes a series of decisions about multiple authorization requests for one principal or resource. Each request contains the equivalent content of an… - POSTBatch is authorized with token
/#X-Amz-Target=VerifiedPermissions.BatchIsAuthorizedWithTokenMakes a series of decisions about multiple authorization requests for one token. The principal in this request comes from an external identity source in the… - POSTCreate policy store
/#X-Amz-Target=VerifiedPermissions.CreatePolicyStoreCreates a policy store. A policy store is a container for policy resources. As of May 2026, Verified Permissions has aligned with Cedar and now supports… - POSTDelete policy store
/#X-Amz-Target=VerifiedPermissions.DeletePolicyStoreDeletes the specified policy store. This operation is idempotent. If you specify a policy store that does not exist, the request response will still return a… - POSTGet policy store
/#X-Amz-Target=VerifiedPermissions.GetPolicyStoreRetrieves details about a policy store. - POSTGet schema
/#X-Amz-Target=VerifiedPermissions.GetSchemaRetrieve the details for the specified schema in the specified policy store. - POSTIs authorized
/#X-Amz-Target=VerifiedPermissions.IsAuthorizedMakes an authorization decision about a service request described in the parameters. The information in the parameters can also define additional context that… - POSTIs authorized with token
/#X-Amz-Target=VerifiedPermissions.IsAuthorizedWithTokenMakes an authorization decision about a service request described in the parameters. The principal in this request comes from an external identity source in… - POSTList policy stores
/#X-Amz-Target=VerifiedPermissions.ListPolicyStoresReturns a paginated list of all policy stores in the calling Amazon Web Services account. - POSTPut schema
/#X-Amz-Target=VerifiedPermissions.PutSchemaCreates or updates the policy schema in the specified policy store. The schema is used to validate any Cedar policies and policy templates submitted to the… - POSTUpdate policy store
/#X-Amz-Target=VerifiedPermissions.UpdatePolicyStoreModifies the validation setting for a policy store. Verified Permissions is eventually consistent . It can take a few seconds for a new or changed element to…
Identity source
- POSTCreate identity source
/#X-Amz-Target=VerifiedPermissions.CreateIdentitySourceAdds an identity source to a policy store–an Amazon Cognito user pool or OpenID Connect (OIDC) identity provider (IdP). After you create an identity source,… - POSTDelete identity source
/#X-Amz-Target=VerifiedPermissions.DeleteIdentitySourceDeletes an identity source that references an identity provider (IdP) such as Amazon Cognito. After you delete the identity source, you can no longer use… - POSTGet identity source
/#X-Amz-Target=VerifiedPermissions.GetIdentitySourceRetrieves the details about the specified identity source. - POSTList identity sources
/#X-Amz-Target=VerifiedPermissions.ListIdentitySourcesReturns a paginated list of all of the identity sources defined in the specified policy store. - POSTUpdate identity source
/#X-Amz-Target=VerifiedPermissions.UpdateIdentitySourceUpdates the specified identity source to use a new identity provider (IdP), or to change the mapping of identities from the IdP to a different principal…
Policy
- POSTCreate policy
/#X-Amz-Target=VerifiedPermissions.CreatePolicyCreates a Cedar policy and saves it in the specified policy store. You can create either a static policy or a policy linked to a policy template. To create a… - POSTDelete policy
/#X-Amz-Target=VerifiedPermissions.DeletePolicyDeletes the specified policy from the policy store. This operation is idempotent; if you specify a policy that doesn't exist, the request response returns a… - POSTGet policy
/#X-Amz-Target=VerifiedPermissions.GetPolicyRetrieves information about the specified policy. - POSTList policies
/#X-Amz-Target=VerifiedPermissions.ListPoliciesReturns a paginated list of all policies stored in the specified policy store. - POSTUpdate policy
/#X-Amz-Target=VerifiedPermissions.UpdatePolicyModifies a Cedar static policy in the specified policy store. You can change only certain elements of the UpdatePolicyDefinition parameter. You can directly…
Policy store alias
- POSTCreate policy store alias
/#X-Amz-Target=VerifiedPermissions.CreatePolicyStoreAliasCreates a policy store alias for the specified policy store. A policy store alias is an alternative identifier that you can use to reference a policy store in… - POSTDelete policy store alias
/#X-Amz-Target=VerifiedPermissions.DeletePolicyStoreAliasDeletes the specified policy store alias. This operation is idempotent. If you specify a policy store alias that does not exist, the request response will… - POSTGet policy store alias
/#X-Amz-Target=VerifiedPermissions.GetPolicyStoreAliasRetrieves details about the specified policy store alias. - POSTList policy store aliases
/#X-Amz-Target=VerifiedPermissions.ListPolicyStoreAliasesReturns a paginated list of all policy store aliases in the calling Amazon Web Services account.
Policy template
- POSTCreate policy template
/#X-Amz-Target=VerifiedPermissions.CreatePolicyTemplateCreates a policy template. A template can use placeholders for the principal and resource. A template must be instantiated into a policy by associating it… - POSTDelete policy template
/#X-Amz-Target=VerifiedPermissions.DeletePolicyTemplateDeletes the specified policy template from the policy store. This operation also deletes any policies that were created from the specified policy template.… - POSTGet policy template
/#X-Amz-Target=VerifiedPermissions.GetPolicyTemplateRetrieve the details for the specified policy template in the specified policy store. - POSTList policy templates
/#X-Amz-Target=VerifiedPermissions.ListPolicyTemplatesReturns a paginated list of all policy templates in the specified policy store. - POSTUpdate policy template
/#X-Amz-Target=VerifiedPermissions.UpdatePolicyTemplateUpdates the specified policy template. You can update only the description and the some elements of the policyBody . Changes you make to the policy template…
- POSTList tags for resource
/#X-Amz-Target=VerifiedPermissions.ListTagsForResourceReturns the tags associated with the specified Amazon Verified Permissions resource. In Verified Permissions, policy stores can be tagged. - POSTTag resource
/#X-Amz-Target=VerifiedPermissions.TagResourceAssigns one or more tags (key-value pairs) to the specified Amazon Verified Permissions resource. Tags can help you organize and categorize your resources.… - POSTUntag resource
/#X-Amz-Target=VerifiedPermissions.UntagResourceRemoves one or more tags from the specified Amazon Verified Permissions resource. In Verified Permissions, policy stores can be tagged.
API details
- Base URL
https://verifiedpermissions.{region}.amazonaws.com- Authentication
- AWS Signature Version 4 (requests signed with your AWS access key)
- Operations
- 34 operations on 34 pathsPOST 34
- Main resources
- Policy store 12Identity source 5Policy 5Policy template 5Policy store alias 4
- Description format
- AWS Smithy model, API version
2021-12-01 - Links
- Documentation · OpenAPI document
- Listed from
- AWS Smithy API model (aws/api-models-aws) (Apache-2.0)
How to test the Amazon Verified Permissions in Swastik Codes
- Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
- Fork it into your workspaceChoose a workspace. You get your own copy of the Amazon Verified Permissions collection, without the publisher's secrets.
- Add your credentialsThis API uses AWS Signature Version 4 (requests signed with your AWS access key). Add yours in the collection's variables or an environment; the requests already reference it.
- Send a requestPick an endpoint, for example “Batch get policy” (POST /#X-Amz-Target=VerifiedPermissions.BatchGetPolicy), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the Amazon Verified Permissions?
Amazon Verified Permissions is a permissions management service from Amazon Web Services. You can use Verified Permissions to manage permissions for your… It is listed under Identity & security and has 34 endpoints.
Who publishes the Amazon Verified Permissions?
It is listed from Amazon Web Services, Inc.'s public API description (an OpenAPI document), not published by Amazon Web Services, Inc. on Swastik Codes. Anyone who controls amazonaws.com can claim the profile by adding a DNS TXT record.
What is the base URL of the Amazon Verified Permissions?
Requests go to https://verifiedpermissions.{region}.amazonaws.com. Endpoint paths are added to this base URL.
How do I authenticate with the Amazon Verified Permissions?
With AWS Signature Version 4 (requests signed with your AWS access key).
How many endpoints does the Amazon Verified Permissions have?
34 operations on 34 paths (34 POST). The largest groups are Policy store, Identity source, Policy, Policy template.
Is forking the Amazon Verified Permissions free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.