1 Answer
- Newest
- Most votes
- Most comments
1
In general, we don't talk about how services are built behind the scenes. They are managed services and they are designed to deliver the features that are in the documentation. While the implementation details may be interesting in general they aren't public. This also gives us the freedom to find different ways of implementing services which might increase performance or decrease the cost to customers. There are absolutely cases where we talk about these things; but for the most part we don't.
In this case: Does knowing how the service work influence your decision to use it? Or change how you would use it?
Relevant content
- Accepted Answerasked 7 months ago
AWS OFFICIALUpdated 6 months ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 8 months ago
The reason I'd like to know is that $0.40 per secret plus $0.05 per 10,000 requests feels high to me. As an alternative, for example, you could store a SecureString in SSM parameter store. Knowing a little more about how it works under the hood might give us insight into why we should use the secrets manager instead (and incur the higher cost)
I'm not sure that knowing how it is built helps here - it's more about how you intended to use it. Secrets Manager has extra functionality (in terms of how secrets are rotated and integration with other services to make that invisible to you); while Parameter Store has a wider range of use cases - it's not just about passwords and other "secret" data. Do you need that extra functionality? Then Secrets Manager is for you. If not, Parameter Store and less expense is the way to go.