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.
Creates a policy store. A policy store is a container for policy resources.
Although Cedar
supports multiple namespaces, Verified Permissions currently supports only one
namespace per policy store.
Verified Permissions is eventually
consistent . It can take a few seconds for a new or changed element to propagate
through the service and be visible in the results of other Verified Permissions operations.
For .NET Core this operation is only available in asynchronous form. Please refer to CreatePolicyStoreAsync.
Namespace: Amazon.VerifiedPermissions
Assembly: AWSSDK.VerifiedPermissions.dll
Version: 3.x.y.z
public virtual CreatePolicyStoreResponse CreatePolicyStore( CreatePolicyStoreRequest request )
Container for the necessary parameters to execute the CreatePolicyStore service method.
| Exception | Condition |
|---|---|
| AccessDeniedException | You don't have sufficient access to perform this action. |
| ConflictException | The request failed because another request to modify a resource occurred at the same. |
| InternalServerException | The request failed because of an internal error. Try your request again later |
| ServiceQuotaExceededException | The request failed because it would cause a service quota to be exceeded. |
| ThrottlingException | The request failed because it exceeded a throttling quota. |
| ValidationException | The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid. The possible reasons include the following: UnrecognizedEntityType The policy includes an entity type that isn't found in the schema. UnrecognizedActionId The policy includes an action id that isn't found in the schema. InvalidActionApplication The policy includes an action that, according to the schema, doesn't support the specified principal and resource. UnexpectedType The policy included an operand that isn't a valid type for the specified operation. IncompatibleTypes The types of elements included in a set, or the types of expressions used in an if...then...else clause aren't compatible in this context. MissingAttribute The policy attempts to access a record or entity attribute that isn't specified in the schema. Test for the existence of the attribute first before attempting to access its value. For more information, see the has (presence of attribute test) operator in the Cedar Policy Language Guide. UnsafeOptionalAttributeAccess The policy attempts to access a record or entity attribute that is optional and isn't guaranteed to be present. Test for the existence of the attribute first before attempting to access its value. For more information, see the has (presence of attribute test) operator in the Cedar Policy Language Guide. ImpossiblePolicy Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision. WrongNumberArguments The policy references an extension type with the wrong number of arguments. FunctionArgumentValidationError Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character. |
.NET Framework:
Supported in: 4.5 and newer, 3.5