CreatePolicyStore
Creates a policy store. A policy store is a container for policy resources.
Note
Although Cedar supports multiple namespaces
Note
Verified Permissions is
eventually consistent
Request Syntax
{
"clientToken": "string
",
"description": "string
",
"validationSettings": {
"mode": "string
"
}
}
Request Parameters
For information about the parameters that are common to all actions, see Common Parameters.
The request accepts the following data in JSON format.
Note
In the following list, the required parameters are described first.
- validationSettings
-
Specifies the validation setting for this policy store.
Currently, the only valid and required value is
Mode
.Important
We recommend that you turn on
STRICT
mode only after you define a schema. If a schema doesn't exist, thenSTRICT
mode causes any policy to fail validation, and Verified Permissions rejects the policy. You can turn off validation by using the UpdatePolicyStore. Then, when you have a schema defined, use UpdatePolicyStore again to turn validation back on.Type: ValidationSettings object
Required: Yes
- clientToken
-
Specifies a unique, case-sensitive ID that you provide to ensure the idempotency of the request. This lets you safely retry the request without accidentally performing the same operation a second time. Passing the same value to a later call to an operation requires that you also pass the same value for all other parameters. We recommend that you use a UUID type of value.
. If you don't provide this value, then AWS generates a random one for you.
If you retry the operation with the same
ClientToken
, but with different parameters, the retry fails with anConflictException
error.Verified Permissions recognizes a
ClientToken
for eight hours. After eight hours, the next request with the same parameters performs the operation again regardless of the value ofClientToken
.Type: String
Length Constraints: Minimum length of 1. Maximum length of 64.
Pattern:
[a-zA-Z0-9-]*
Required: No
- description
-
Descriptive text that you can provide to help with identification of the current policy store.
Type: String
Length Constraints: Minimum length of 0. Maximum length of 150.
Required: No
Response Syntax
{
"arn": "string",
"createdDate": "string",
"lastUpdatedDate": "string",
"policyStoreId": "string"
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
The following data is returned in JSON format by the service.
- arn
-
The Amazon Resource Name (ARN) of the new policy store.
Type: String
Length Constraints: Minimum length of 1. Maximum length of 2500.
Pattern:
arn:[^:]*:[^:]*:[^:]*:[^:]*:.*
- createdDate
-
The date and time the policy store was originally created.
Type: Timestamp
- lastUpdatedDate
-
The date and time the policy store was last updated.
Type: Timestamp
- policyStoreId
-
The unique ID of the new policy store.
Type: String
Length Constraints: Minimum length of 1. Maximum length of 200.
Pattern:
[a-zA-Z0-9-]*
Errors
For information about the errors that are common to all actions, see Common Errors.
- AccessDeniedException
-
You don't have sufficient access to perform this action.
HTTP Status Code: 400
- ConflictException
-
The request failed because another request to modify a resource occurred at the same.
HTTP Status Code: 400
- InternalServerException
-
The request failed because of an internal error. Try your request again later
HTTP Status Code: 500
- ServiceQuotaExceededException
-
The request failed because it would cause a service quota to be exceeded.
HTTP Status Code: 400
- ThrottlingException
-
The request failed because it exceeded a throttling quota.
HTTP Status Code: 400
- 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 anif...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.
HTTP Status Code: 400
-
Examples
Example
The following example creates a new policy store with strict validation turned on.
Sample Request
POST HTTP/1.1
Host: verifiedpermissions.us-east-1.amazonaws.com
X-Amz-Date: 20230613T200059Z
Accept-Encoding: identity
X-Amz-Target: VerifiedPermissions.CreatePolicyStore
User-Agent: <UserAgentString>
Authorization: AWS4-HMAC-SHA256 Credential=<Credential>, SignedHeaders=<Headers>, Signature=<Signature>
Content-Length: <PayloadSizeBytes>
{
"validationSettings": {"mode": "STRICT"},
"clientToken": "a1b2c3d4-e5f6-a1b2-c3d4-TOKEN1111111"
}
Sample Response
HTTP/1.1 200 OK
Date: Tue, 13 Jun 2023 20:00:59 GMT
Content-Type: application/x-amz-json-1.0
Content-Length: <PayloadSizeBytes>
vary: origin
vary: access-control-request-method
vary: access-control-request-headers
x-amzn-requestid: a1b2c3d4-e5f6-a1b2-c3d4-EXAMPLE11111
Connection: keep-alive
{
"policyStoreId":"PSEXAMPLEabcdefg111111",
"arn":"arn:aws:verifiedpermissions::123456789012:policy-store/PSEXAMPLEabcdefg111111",
"createdDate":"2023-05-16T17:41:29.103459Z",
"lastUpdatedDate":"2023-05-16T17:41:29.103459Z"
}
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following: