Adding the InfluxDB Single and Multi-user Secret Rotation Lambda functions

[forestmvey]

Issue #, if available:

N/A

Description of changes:

The InfluxDB Single and Multi-user Secret Rotation Lambdas enables the automatic rotation for users and tokens with Timestream for InfluxDB. The Multi-user rotation lambda uses an admin authenticated session to rotate another token credentials. The Single-user rotation lambda rotates their own authenticated session to update a user password with a new random password.

InfluxDB best practice for access management is to use users to create tokens for fine grain access control within an organization. Users permissions are scoped to allAccess within an organization and tokens can have any set of permissions. Use the multi-user variant for managing token rotation and use the single-user variant for rotating user credentials.

The Timestream for InfluxDB endpoint is retrieved through get_db_instance. In the case of the Multi-user rotator the authenticated client performing the rotation is the influxAuthParametersSecretArn that is created on DB initialization.

Validations:

Linting

• - Ruff linting

single-user tests

• - test existing user
• - test re-rotation
• - test invalid password
• - test non-existent user
• - test missing password
• - test missing username
• - test invalid engine
• - test missing engine
• - test invalid DB identifier
• - test missing DB identifier

multi-user tests

• - test failure to create operator token with auth environment variable set to True
• - test failure to create operator token with auth environment variable set to False
• - test failure to create allAccess token with auth environment variable set to False
• - test failure to create custom token with auth environment variable set to False
• - test success to create allAccess token with auth environment variable set to True
• - test on successful rotation that old token value is deleted
• - test success to create custom token with auth environment variable set to True
• - test failure to create custom token without any permissions defined in secret
• - test custom token has correct permissions - 2 sets of write/read buckets and 2 permissions
• - test success rotation of allAccess token
• - test success rotation of custom token
• - test success rotation of operator token
• - test failure with missing org
• - test failure with invalid org
• - test failure with invalid DB identifier
• - test failure with missing DB identifier
• - test failure with invalid engine
• - test failure with missing engine
• - test failure with invalid token value
• - test failure with invalid token type
• - test failure with missing token type

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.