Reference AWS Secrets Manager rotation for API keys and SATs#38116
Open
anthony-dgx wants to merge 2 commits into
Open
Reference AWS Secrets Manager rotation for API keys and SATs#38116anthony-dgx wants to merge 2 commits into
anthony-dgx wants to merge 2 commits into
Conversation
…ion keys, and SATs
Contributor
Preview links (active after the
|
jeff-morgan-dd
approved these changes
Jul 13, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What does this PR do? What is the motivation?
Adds a reference to AWS Secrets Manager's new managed rotation support for Datadog credentials (announced May 2026). Recommends storing long-lived API keys, application keys, and Service Access Tokens (SATs) in a secrets manager such as AWS Secrets Manager, HashiCorp Vault, or Azure Key Vault, rather than in source code or environment files.
Personal Access Tokens (PATs) are not covered, since they require an expiration and aren't supported by the AWS managed rotation feature.
Merge instructions
Merge readiness:
Additional notes