AWS cli: Social Messaging: add Direct Send enforcement status fields
Summary
Documents new account fields directSendEnforcementStatus and directSendEnforcementStatusExpiresAt in get-linked-whatsapp-business-account output, plus CLI version bump.
Security assessment
Adds messaging-policy enforcement metadata (abuse/rate enforcement status and expiry) to the API output; it is operational/abuse-control information, not a security control or vulnerability fix.
Evidence
+> directSendEnforcementStatus -> (string)
Diff
diff --git a/cli/latest/reference/socialmessaging/get-linked-whatsapp-business-account.md b/cli/latest/reference/socialmessaging/get-linked-whatsapp-business-account.md index 3f19060..c41c960 100644 --- a//cli/latest/reference/socialmessaging/get-linked-whatsapp-business-account.md +++ b//cli/latest/reference/socialmessaging/get-linked-whatsapp-business-account.md @@ -15 +15 @@ - * [AWS CLI 2.38.1 Command Reference](../../index.html) » + * [AWS CLI 2.38.2 Command Reference](../../index.html) » @@ -329,0 +330,15 @@ account -> (structure) +> +> directSendEnforcementStatus -> (string) +> +>> The Direct Send enforcement status for the WhatsApp Business Account. Enforcement applies when an account repeatedly sends messages in a category that does not match the content. This field is not present when no enforcement is active. +>> +>> Constraints: +>> +>> * min: `1` +>> * max: `30` +>> + +> +> directSendEnforcementStatusExpiresAt -> (timestamp) +> +>> The time when the current Direct Send enforcement is expected to lift. This field is not present for permanent enforcement or when no enforcement is active. @@ -450 +465 @@ account -> (structure) - * [AWS CLI 2.38.1 Command Reference](../../index.html) » + * [AWS CLI 2.38.2 Command Reference](../../index.html) »