AWS cli medium security documentation change
Summary
Updated regex patterns for user attributes, added CLI error formatting, and enhanced documentation about custom workflows/Lambda triggers
Security assessment
The regex pattern change from [\p{L}\p{M}\p{S}\p{N}\p{P}]+ to [\p{L}\p{M}\p{S}\p{N}\p{P}\t\n\r ]+ addresses potential input validation issues by expanding allowed whitespace characters. The documentation explicitly states this affects pools created before May 2024 across multiple regions, indicating a security-related update to prevent attribute injection or validation bypasses. The clarification about Lambda triggers improves security documentation by linking API actions to runtime security controls.
Diff
diff --git a/cli/latest/reference/cognito-idp/sign-up.md b/cli/latest/reference/cognito-idp/sign-up.md index b87e32388..ced29ff7e 100644 --- a//cli/latest/reference/cognito-idp/sign-up.md +++ b//cli/latest/reference/cognito-idp/sign-up.md @@ -15 +15 @@ - * [AWS CLI 2.33.29 Command Reference](../../index.html) » + * [AWS CLI 2.34.0 Command Reference](../../index.html) » @@ -108,0 +109 @@ See also: [AWS API Documentation](https://docs.aws.amazon.com/goto/WebAPI/cognit + [--cli-error-format <value>] @@ -174 +175,3 @@ See also: [AWS API Documentation](https://docs.aws.amazon.com/goto/WebAPI/cognit ->>> The name of the attribute. +>>> The name of the attribute, for example `email` or `custom:department` . +>>> +>>> In some older user pools, the regex pattern for acceptable values of this parameter is `[\p{L}\p{M}\p{S}\p{N}\p{P}]+` . Older pools will eventually be updated to use the new pattern. Affected user pools are those created before May 2024 in US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Tokyo), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), Europe (Stockholm), Middle East (Bahrain), and South America (São Paulo). @@ -180 +183 @@ See also: [AWS API Documentation](https://docs.aws.amazon.com/goto/WebAPI/cognit ->>> * pattern: `[\p{L}\p{M}\p{S}\p{N}\p{P}]+` +>>> * pattern: `[\p{L}\p{M}\p{S}\p{N}\p{P}\t\n\r ]+` @@ -226 +229,3 @@ JSON Syntax: ->>> The name of the attribute. +>>> The name of the attribute, for example `email` or `custom:department` . +>>> +>>> In some older user pools, the regex pattern for acceptable values of this parameter is `[\p{L}\p{M}\p{S}\p{N}\p{P}]+` . Older pools will eventually be updated to use the new pattern. Affected user pools are those created before May 2024 in US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Tokyo), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), Europe (Stockholm), Middle East (Bahrain), and South America (São Paulo). @@ -232 +237 @@ JSON Syntax: ->>> * pattern: `[\p{L}\p{M}\p{S}\p{N}\p{P}]+` +>>> * pattern: `[\p{L}\p{M}\p{S}\p{N}\p{P}\t\n\r ]+` @@ -338 +343 @@ JSON Syntax: -> A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers. +> A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers. You create custom workflows by assigning Lambda functions to user pool triggers. @@ -340 +345 @@ JSON Syntax: -> You create custom workflows by assigning Lambda functions to user pool triggers. When you use the SignUp API action, Amazon Cognito invokes any functions that are assigned to the following triggers: _pre sign-up_ , _custom message_ , and _post confirmation_ . When Amazon Cognito invokes any of these functions, it passes a JSON payload, which the function receives as input. This payload contains a `clientMetadata` attribute, which provides the data that you assigned to the ClientMetadata parameter in your SignUp request. In your function code in Lambda, you can process the `clientMetadata` value to enhance your workflow for your specific needs. +> When Amazon Cognito invokes any of these functions, it passes a JSON payload, which the function receives as input. This payload contains a `clientMetadata` attribute that provides the data that you assigned to the ClientMetadata parameter in your request. In your function code, you can process the `clientMetadata` value to enhance your workflow for your specific needs. @@ -342 +347 @@ JSON Syntax: -> For more information, see [Using Lambda triggers](https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html) in the _Amazon Cognito Developer Guide_ . +> To review the Lambda trigger types that Amazon Cognito invokes at runtime with API requests, see [Connecting API actions to Lambda triggers](https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pools-working-with-lambda-triggers.html#lambda-triggers-by-event) in the _Amazon Cognito Developer Guide_ . @@ -415,0 +421 @@ The formatting style for command output. + * off @@ -481,0 +488,13 @@ Disable automatically prompt for CLI input parameters. +`--cli-error-format` (string) + +The formatting style for error output. By default, errors are displayed in enhanced format. + + * legacy + * json + * yaml + * text + * table + * enhanced + + + @@ -549 +568 @@ CodeDeliveryDetails -> (structure) ->> * pattern: `[\p{L}\p{M}\p{S}\p{N}\p{P}]+` +>> * pattern: `[\p{L}\p{M}\p{S}\p{N}\p{P}\t\n\r ]+` @@ -585 +604 @@ Session -> (string) - * [AWS CLI 2.33.29 Command Reference](../../index.html) » + * [AWS CLI 2.34.0 Command Reference](../../index.html) »