[Feat] Allow AWS SECRETS MANAGER instead of storing AES Encrypted in db

[aluferraz]

This pull request introduces a significant security enhancement by providing an option to migrate away from storing AES-encrypted sensitive data directly in our database. Instead, it allows us to leverage AWS Secrets Manager to securely store, manage, and retrieve our application's secrets.

Key Highlights of this Change:

Improved Security: Sensitive data is now protected by AWS Secrets Manager's enterprise-grade security features, including encryption at rest and in transit, strict access controls, and auditing capabilities.
Compliance Alignment: This shift enhances our alignment with various regulatory compliance standards that recommend or mandate the use of dedicated secret management solutions for sensitive data.
Simplified Key Management: No longer will we need to manage AES encryption keys within our application, reducing operational overhead and potential security risks associated with key mismanagement.
Audit Trail: Traceble log of credentials

[aluferraz]

@HenryHengZJ any thoughts on this feature ? It can be toggled using env. vars.

[HenryHengZJ]

@aluferraz I've made some changes to the env variables naming:

To use aws:

SECRETKEY_STORAGE_TYPE=aws#(local | aws)
SECRETKEY_AWS_ACCESS_KEY=<your-access-key>
SECRETKEY_AWS_SECRET_KEY=<your-secret-key>
SECRETKEY_AWS_REGION=us-west-2

[aluferraz]

Thanks a lot @HenryHengZJ, I'm happy to continue contributing, are we missing anything after your updates or are we good to merge?

[HenryHengZJ]

we're good to merge! thank you @aluferraz !