AWS lambda: Lambda durable encryption: DeleteDurableExecution needs no key policy statement
Summary
Amends the durable execution operator key-policy bullet to note that DeleteDurableExecution does not use the KMS key and therefore requires no statement in the key policy.
Security assessment
Clarifies the scope of KMS key-policy statements for durable execution operators, telling readers that the delete API does not require kms:Decrypt and thus should not be granted in the key policy. This is encryption/key-policy guidance rather than a fix for a specific vulnerability.
Evidence
- * **Allow durable execution operators**. Grants operators `kms:Decrypt` for calls to `GetDurableExecution`, `GetDurableExecutionHistory` with `IncludeExecutionData=true`, `GetDurableExecutionState`, `StopDurableExecution`, and the callback APIs.
Diff
diff --git a/lambda/latest/dg/durable-encryption.md b/lambda/latest/dg/durable-encryption.md index 8aaea01..71ddbba 100644 --- a//lambda/latest/dg/durable-encryption.md +++ b//lambda/latest/dg/durable-encryption.md @@ -74 +74 @@ The policy grants the following capabilities: - * **Allow durable execution operators**. Grants operators `kms:Decrypt` for calls to `GetDurableExecution`, `GetDurableExecutionHistory` with `IncludeExecutionData=true`, `GetDurableExecutionState`, `StopDurableExecution`, and the callback APIs. + * **Allow durable execution operators**. Grants operators `kms:Decrypt` for calls to `GetDurableExecution`, `GetDurableExecutionHistory` with `IncludeExecutionData=true`, `GetDurableExecutionState`, `StopDurableExecution`, and the callback APIs. `DeleteDurableExecution` doesn't use the key, so it doesn't need a statement in the key policy.