MySQL MultiUser Increase Username limit from 16 to 32 about aws-secrets-manager-rotation-lambdas HOT 5 CLOSED

@crus-umich this is ok from code point of view, but I believe this code is used by hosted rotation lambda functions, where I do not see option to modify ENV. Ref.: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-secretsmanager-rotationschedule-hostedrotationlambda.html

from aws-secrets-manager-rotation-lambdas.

Code branching based on version seems necessary.
For MySQL 5.6 (Aurora 1.x) ... 16 characters
For MySQL 5.7 (Aurora 2.x) ... 32 characters
For MySQL 8.0 (Aurora 3.x) ... 32 characters

from aws-secrets-manager-rotation-lambdas.

According to official version documentation Aurora 1.x is depreciated so may be branching is not needed. Source: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.VersionPolicy.html

from aws-secrets-manager-rotation-lambdas.

Given that Aurora 1.x is deprecated, would you receive a PR to check for 32 characters instead of 16, in all cases?

from aws-secrets-manager-rotation-lambdas.

Hello,
In order to maintain backward compatibility we have added a configurable environment variable named 'USERNAME_CHARACTER_LIMIT' to the lambda for MySQL alternating user rotation in this PR. It is defaulted to 16 but can be raised to 32 allowing for usernames up to 26 characters as we still reserve 6 for the '_clone' suffix.

Here's documentation on customizing your rotation function with this variable

from aws-secrets-manager-rotation-lambdas.