Add AWS/SecretsManager to the services list #1330
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
taraspos
force-pushed
the
taraspos/add-secrets-manager
branch
from
9a1b855 to
5249d9d
Compare
At the moment `AWS/SecretsManager` namespace has only metric in there - `ResourceCount`, it can be used to keep track of count of secrets in the region (secrets count is not being reported to the `AWS/Usage` namespace for some reason) - https://docs.aws.amazon.com/secretsmanager/latest/userguide/monitoring-cloudwatch.html
taraspos
force-pushed
the
taraspos/add-secrets-manager
branch
from
5249d9d to
54d387b
Compare
This was referenced Apr 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Add AWS/SecretsManager to the services list
Context
At the moment
AWS/SecretsManagernamespace has only metric in there -ResourceCount, it can be used to keep track of count of secrets in the region (secrets count is not being reported to theAWS/Usagenamespace for some reason)