AWS aurora-dsql: Aurora DSQL: resource-based policy attach requirements
Summary
Documents requirements for attaching a cluster resource-based policy: max 20,480 characters, no service principals, no public access, and no denial of both dsql:PutClusterPolicy and dsql:DeleteClusterPolicy (with bypassPolicyLockoutSafetyCheck override), plus guidance to use --expected-policy-version to avoid overwriting concurrent changes.
Security assessment
The added text codifies authorization guardrails for resource-based policies: prohibiting public access, prohibiting service principals, and enforcing a lockout safety check so an administrator cannot deny themselves PutClusterPolicy/DeleteClusterPolicy (an IAM permission-boundary/lockout protection), plus optimistic concurrency via expected-policy-version. This is security documentation of access-control constraints rather than a fix for a specific disclosed vulnerability.
Evidence
+ * It doesn't grant public access. For more information, see [Blocking public access with resource-based policies in Aurora DSQL](./rbp-block-public-access.html).
Diff
diff --git a/aurora-dsql/latest/userguide/rbp-attach-policy.md b/aurora-dsql/latest/userguide/rbp-attach-policy.md index f677606..f859e17 100644 --- a//aurora-dsql/latest/userguide/rbp-attach-policy.md +++ b//aurora-dsql/latest/userguide/rbp-attach-policy.md @@ -8,0 +9,15 @@ +When you attach a policy or create a cluster with one, the policy must meet these requirements: + + * It's no longer than 20,480 characters. + + * It doesn't include service principals (the `Service` key in a `Principal` element). + + * It doesn't grant public access. For more information, see [Blocking public access with resource-based policies in Aurora DSQL](./rbp-block-public-access.html). + + * It doesn't deny you both `dsql:PutClusterPolicy` and `dsql:DeleteClusterPolicy`. + + + + +The last requirement makes sure that you can still change or remove the policy after you attach it. To attach a policy that denies you both actions anyway, set `bypassPolicyLockoutSafetyCheck` to `true`, or pass `--bypass-policy-lockout-safety-check` in the AWS CLI. + @@ -58,0 +74,2 @@ Use the `put-cluster-policy` command to attach a new policy or update an existin +To avoid overwriting a change that someone else made after you read the policy, pass the `policyVersion` value from `get-cluster-policy` in `--expected-policy-version`. If the policy changed after you read it, the command fails with a `ConflictException`. +