An area for improvement in AWS Secrets Manager could be expanding integration options beyond AWS services. Enhancing compatibility with other platforms like Azure and providing more automated options for secret rotation could simplify the overall integration process for users.
DevOps Lead at a manufacturing company with 1,001-5,000 employees
Real User
Top 20
2023-10-06T17:15:08Z
Oct 6, 2023
There is room for improvement in the pricing model. In future releases, I would like to see a feature. For example, other secret managers don't allow the use of services other than AWS service. So, if we have AWS Secrets Manager allowed to a user outside the AWS environment, it will be an additional feature.
Even though I said that the employee or programmer doesn't need to see the secret, he can view the secret if he intends to. He just has to display the value he fetched from the AWS Secrets Manager. The solution should add one more layer of encoding and decoding so that when the programmer fetches the value from the AWS Secrets Manager, what he receives is only an encoded version. Instead of directly sending it to Google, he sends the authentication information to another AWS service which decodes it and then sends it to Google. If you add one more layer of security to AWS Secrets Manager, even the programmer will not be able to see the secrets.
Find out what your peers are saying about Amazon Web Services (AWS), Microsoft, HashiCorp and others in Enterprise Password Managers. Updated: November 2024.
Associate Technical Architect at a computer software company with 1,001-5,000 employees
Real User
2021-08-31T19:57:59Z
Aug 31, 2021
If you don't have enterprise support, then you will not be able to get through to them to get the help. It is not only applicable to AWS Secrets Manager. It is also applicable to any service on AWS.
Enterprise password management solutions store and administer sensitive data such as passwords, records, and identity credentials for organizations. Since most cyber-attacks use legitimate credentials to enter an organization, password security is an essential part of an organization’s security posture.
An area for improvement in AWS Secrets Manager could be expanding integration options beyond AWS services. Enhancing compatibility with other platforms like Azure and providing more automated options for secret rotation could simplify the overall integration process for users.
There is room for improvement in the pricing model. In future releases, I would like to see a feature. For example, other secret managers don't allow the use of services other than AWS service. So, if we have AWS Secrets Manager allowed to a user outside the AWS environment, it will be an additional feature.
AWS Secrets Manager could support hybrid infrastructure. There could be more functionalities compared to different solution providers.
Even though I said that the employee or programmer doesn't need to see the secret, he can view the secret if he intends to. He just has to display the value he fetched from the AWS Secrets Manager. The solution should add one more layer of encoding and decoding so that when the programmer fetches the value from the AWS Secrets Manager, what he receives is only an encoded version. Instead of directly sending it to Google, he sends the authentication information to another AWS service which decodes it and then sends it to Google. If you add one more layer of security to AWS Secrets Manager, even the programmer will not be able to see the secrets.
There is a need for better environmental implementation, such as having a security fund as a solution.
The sidecar feature has room for improvement.
If you don't have enterprise support, then you will not be able to get through to them to get the help. It is not only applicable to AWS Secrets Manager. It is also applicable to any service on AWS.
We occasionally have problems with rate limits, although that is a problem more generally with AWS.
It would be good if the AWS Secrets Manager were more customizable.