AWS services or capabilities described in AWS Documentation may vary by region/location. Click Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.
Name | Description | |
---|---|---|
![]() |
AmazonVerifiedPermissionsClient |
Implementation for accessing VerifiedPermissions 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:
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:
|
![]() |
AmazonVerifiedPermissionsConfig |
Configuration for accessing Amazon VerifiedPermissions service |
![]() |
AmazonVerifiedPermissionsDefaultConfiguration |
Configuration for accessing Amazon VerifiedPermissions service |
![]() |
AmazonVerifiedPermissionsException |
Common exception for the VerifiedPermissions service. |
![]() |
AmazonVerifiedPermissionsRequest |
Base class for VerifiedPermissions operation requests. |
![]() |
Decision |
Constants used for properties of type Decision. |
![]() |
OpenIdIssuer |
Constants used for properties of type OpenIdIssuer. |
![]() |
PolicyEffect |
Constants used for properties of type PolicyEffect. |
![]() |
PolicyType |
Constants used for properties of type PolicyType. |
![]() |
ResourceType |
Constants used for properties of type ResourceType. |
![]() |
ValidationMode |
Constants used for properties of type ValidationMode. |
Name | Description | |
---|---|---|
![]() |
IAmazonVerifiedPermissions |
Interface for accessing VerifiedPermissions 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:
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:
|