Secrets Manager stores encrypted credentials outside application code. These sections explain how applications retrieve versions, how rotation updates the target credential, and how replication and policies support regional and account boundaries.
Secret versions and runtime access
Secrets Manager stores encrypted credentials separately from application code. A secret has metadata and versions of its value; applications retrieve the required version at runtimeRuntime is the period when application code retrieves and uses a secret while running., meaning while the application is running.
How it works
-
Store a string or binary value. A JSONJSON represents structured secret data as named key-value pairs. object, a set of named key-value pairs, can hold related fields such as a username and password. The value size quota is 65,536 bytes.
-
Secrets Manager encrypts the stored value with a KMS encryption key. A value change creates a new version, which is a saved copy of the encrypted value.
-
Use staging labelsA staging label is a name attached to a secret version to identify its role., names attached to versions, to identify their roles.
Label Meaning AWSCURRENT Current value, returned by default AWSPREVIOUS Previous value AWSPENDING Value being prepared during rotation -
Call GetSecretValue with permission to read the secret and, for a customer managed keyA customer managed key is a KMS encryption key whose policy the customer controls., permission to decrypt with that key. A VersionId selects a specific version; VersionStage selects a label. If both are supplied, they must agree. Retrieval creates a CloudTrail audit event.
-
Account for how the consumer receives updates. ECS environment injection happens at container startup, so rotated values require new tasks. Environment variables are available to code, logs, and debugging tools inside the container.
-
A tool that accepts Parameter Store references can use /aws/reference/secretsmanager/ followed by the secret name with GetParameter or GetParameters. This passes the request through to Secrets Manager and preserves its access controls.
Existing CodeGuru Reviewer repository associations can find unprotected secrets and guide replacement with Secrets Manager references. Since November 7, 2025, CodeGuru Reviewer has not accepted new repository associations.
Exam cues
- If the question says read the current password without pinning a version, think GetSecretValue without version selectors, because AWSCURRENT is the default.
- If the question says ECS kept the old password after rotation, think new tasks, because startup injection does not refresh a running container.
- If the question says use an existing Parameter Store integration for a Secrets Manager value, think the reserved reference path, because Parameter Store passes through the request.
Remember
- Secret value quota: 65,536 bytes.
- Retrieval requires secretsmanager:GetSecretValue and, for a customer managed key, kms:Decrypt.
- GetSecretValue defaults to AWSCURRENT.
- AWSPREVIOUS is a version label, not a command that changes the database password.
- CodeGuru Reviewer accepts only existing repository associations as of November 7, 2025.
Trap: Updating a Secrets Manager version does not refresh an environment variable already injected into a running ECS container.
From the AWS docs (15)
- A Secrets Manager secret contains a string or binary value and metadata; JSON key-value pairs can hold several related string values.
- The Secrets Manager secret value size quota is 65,536 bytes.
- Secrets Manager encrypts stored secret values using a KMS key and encrypts secrets in transit.
- Changing or rotating a secret value creates a new encrypted secret version.
- AWSCURRENT identifies the current secret version, AWSPREVIOUS the previous version, and AWSPENDING a pending rotation version.
- GetSecretValue returns AWSCURRENT if neither VersionId nor VersionStage is specified.
- GetSecretValue can select VersionId or VersionStage; if both are provided they must identify the same version.
- GetSecretValue requires secretsmanager:GetSecretValue; a customer managed KMS key also requires kms:Decrypt.
- Retrieving a Secrets Manager secret generates a CloudTrail log entry.
- ECS injects a referenced secret when a container starts; later rotation requires a new task or forced service deployment to update the injected value.
- Code, logs, and debugging tools inside an ECS container can access its environment variables.
- Parameter Store can retrieve a Secrets Manager secret through the reserved /aws/reference/secretsmanager/ path using GetParameter or GetParameters; it enforces the secret permissions and does not retain secret data.
- CodeGuru Reviewer integrates with Secrets Manager to find unprotected secrets in code and guide replacement of hardcoded values.
- Since November 7, 2025, CodeGuru Reviewer cannot create new repository associations and can be used only with existing associations.
- Credential rotation updates both the stored secret and the credential in the target database or service.
Managed and Lambda rotation
Secret rotation periodically changes a credential in both Secrets Manager and its database or service. Treat the stored value and the credential accepted by the target as a pair that must stay in sync.
How it works
-
Choose the rotation path supported by the secret.
Path Who performs the update Lambda function Managed rotation A supporting AWS service, such as RDS or Aurora for master credentials Not used Managed external secrets rotation Secrets Manager updates a secret held by a supported partner Not used Lambda rotation A configured function updates the secret and target Required -
For Lambda database rotation, choose a strategy. Single user changes one user’s password. Alternating users switches between an original and cloned user, with a separate privileged secret to create the clone. Both credentials remain valid after alternating-users rotation.
-
For a CloudFormation database secret, use AWS::SecretsManager::SecretTargetAttachment to add the connection information needed for rotation to the secret JSONJSON represents structured secret data as named key-value pairs..
Managed external secrets launched in November 2025.
Exam cues
- If the question says supported database master credentials with no custom function, think managed rotation, because the database service manages the updates.
- If the question says a custom service password must change with its stored value, think Lambda rotation, because the function can update the secret and target system.
- If the question says credentials must stay usable during rotation, think alternating users, because the current user stays valid while the other user’s password changes.
- If the question says expire or notify about an old Parameter Store value, think parameter policies, because those actions do not change a database password.
- If the question says a database secret lacks connection information for rotation, think SecretTargetAttachment, because it adds those fields to the secret JSON.
Remember
- Single-user rotation keeps open database connections but can briefly affect new authentication.
- Alternating users requires a separate privileged secret for cloning.
- Managed rotation for supported services and managed external secrets rotation do not require a Lambda function.
Trap: Saving a new password value is only one part of rotation. The target credential must also be updated.
Create the pending version before changing the target.
Apply the pending credential before testing it.
Promote the tested version and retain AWSPREVIOUS.
Allow pending and current header values in the WAF rule.
Update the CloudFront custom origin header while both values remain accepted.
Test both header values against the ALB before promoting the new secret version.
From the AWS docs (12)
- Secrets Manager credential rotation updates both the stored secret and the database or service credential.
- Managed rotation lets a supporting service configure and manage secret rotation without a Lambda rotation function.
- RDS and Aurora support managed rotation for their master user credentials.
- Secrets Manager managed external secrets can rotate secrets held by supported partners without a Lambda function.
- Other Secrets Manager secrets can use a Lambda rotation function, with a custom function when no suitable template exists.
- Single-user database rotation changes one user password; existing open connections remain, but new authentication can fail briefly between the database update and secret promotion.
- Alternating-users rotation switches between an original and cloned database user, using a separate privileged secret to clone the user; both credentials remain valid after rotation.
- Parameter Store advanced parameter policies are Expiration, ExpirationNotification, and NoChangeNotification; they delete or notify rather than rotate database credentials.
- Secrets Manager managed external secrets launched in November 2025.
- CloudFormation AWS::SecretsManager::SecretTargetAttachment adds the target database connection information to the secret JSON required for database rotation.
- The documented origin-header rotation tests both AWSPENDING and AWSCURRENT header values against the ALB before finishSecret.
- A CloudFront origin is the backend from which the distribution retrieves content.
Rotation failures and client caching
A rotation failure can occur while creating, applying, testing, or promoting a credential. Client cachingA client-side cache keeps retrieved secret values locally for reuse between refreshes., keeping a retrieved value in application memory for reuse, can also leave an application using an older value after rotation succeeds.
How it works
- Start with the Lambda function’s CloudWatch logs and find the failing step. A new AWSPENDING version does not prove that setSecret changed the database password.
- Check the function’s network paths to both Secrets Manager and the database or service. Review endpoint access and security groupA security group controls which network traffic can reach or leave a resource. rules, which control permitted network traffic.
- Inspect the version labels. AWSPENDING on a different version from AWSCURRENT makes a later RotateSecret request report a rotation still in progress. AWSPENDING on the same current version, or absent after success, is allowed.
- Repair the failing workflow before retrying. During normal execution, finishSecret handles promotion; removing AWSPENDING early in separate calls can disrupt the workflow. Secrets Manager retries failed Lambda rotation during the open rotation windowA rotation window is the scheduled time period during which Secrets Manager attempts rotation..
- Inspect application refresh behavior as well. AWS recommends client-side caching. The Python caching component refreshes hourly by default and allows a different interval, but has no cache invalidationCache invalidation discards an outdated cached value so it can be retrieved again. mechanism that immediately discards an outdated cached value.
Exam cues
- If the question says createSecret succeeded but the target password stayed old, think setSecret failure, because that step applies the pending credential.
- If the question says the next rotation reports another rotation in progress, think a separate AWSPENDING version, because the labels still show unfinished work.
- If the question says rotation succeeded but a cached client uses old credentials, think cache refresh configuration, because cached values are reused between refreshes.
- If the question says new logins briefly fail during single-user rotation, think retries, because the target password can change before the secret is promoted.
Remember
- Check logs, version state, permissions, and both network paths.
- The Python caching component defaults to a one-hour refresh; this is not a service-wide cache default.
- Successful rotation does not require AWSPENDING to disappear if it labels AWSCURRENT too.
- Single-user rotation can briefly affect new authentication; retry handling can reduce that impact.
Trap: Login errors after rotation do not identify one cause by themselves. An unapplied target password, an unfinished rotation, and an older cached value require different repairs.
From the AWS docs (11)
- For Lambda rotation failures, AWS recommends starting with CloudWatch logs and checking that every rotation step was attempted.
- A Lambda rotation function needs network access to both Secrets Manager and the target database or service; check endpoint access and security group rules.
- setSecret applies the AWSPENDING credential to the database or service; creating a version alone does not perform this step.
- If AWSPENDING labels a different version from AWSCURRENT, a later RotateSecret call treats rotation as still in progress and returns an error.
- Successful rotation can leave AWSPENDING on the same version as AWSCURRENT or on no version.
- During normal rotation, do not remove AWSPENDING early or in a separate API call before finishSecret.
- If a Lambda rotation step fails, Secrets Manager retries the entire rotation process multiple times during the open rotation window.
- AWS recommends client-side caching of secret values to improve retrieval speed and reduce API costs.
- The Secrets Manager Python caching component refreshes secrets every hour by default and allows configuring the refresh interval.
- The Secrets Manager Python caching component does not implement cache invalidation and is not security hardened.
- Single-user rotation can briefly reject new authentication between the database password update and the secret update; applications can mitigate this with retries.
Regional replication
Secrets Manager regional replication gives applications copies of a secret in selected Regions. The primary secret is the source of updates; a replica stays linked to that source until it is promoted to an independent secret.
How it works
- Select enabled destination Regions for the primary secret. Secrets Manager copies encrypted data and metadata, including tags and resource policies.
- Choose a replica encryption key if needed. That KMS key must be in the replica Region. The replica ARNAn ARN is an AWS resource identifier that includes its service, Region, account, and resource name., the resource’s unique AWS identifier, differs from the primary ARN only in its Region.
- Rotate at the primary. Secrets Manager propagates the new value to the replicas, so each replica does not need its own rotation schedule.
- Check the secret’s connection details. Database host information stays the same in the replica; add Region-specific fields if applications need other database endpoints.
- When the replica must become independently managed, promote it to standalone. This stops the link to the primary and allows independent replication and management.
Exam cues
- If the question says applications need local secret access in multiple Regions, think replication, because it creates regional copies.
- If the question says rotation must reach every regional copy, think rotate the primary, because its updated value propagates to replicas.
- If the question says the recovery Region must manage its secret independently, think standalone promotion, because it stops replication from the primary.
Remember
- Replica ARN: same as primary except for Region.
- Replica KMS key: located in the replica Region.
- Replication preserves source connection details.
- Cross-Region retrieval can also call the secret’s original regional endpoint without replication.
- Commercial-to-specialized Region replication is unsupported.
Trap: Replicating a database secret does not replace its host field with the destination Region’s database endpoint.
Rotation at the primary propagates the new secret value to linked replicas.
Applications retrieve the regional copy using its regional ARN and endpoint.
From the AWS docs (8)
- Secrets Manager replication copies encrypted secret data and metadata, including tags and resource policies, to selected enabled Regions.
- A replica secret ARN differs from the primary secret ARN only in its Region.
- A replica can use a selected KMS key that must be in the replica Region.
- Rotation runs on the primary secret and the new value propagates to its associated replicas; replicas do not need independent rotation schedules.
- A replicated database secret keeps the source database connection information; extra key-value pairs can store Region-specific connection details.
- Promoting a replica to standalone stops its link to the primary, allowing independent management and replication.
- Secrets Manager cannot replicate between commercial Regions and specialized Regions such as AWS GovCloud (US) or China Regions.
- An application can access a secret in another Region without replication by calling the endpoint of the Region that stores it.
Cross-account access
Cross-account secret access lets an application read a secret owned by another AWS account. The owner authorizes the reader on the secret and its encryption key, and the consumer account authorizes the reader to use both.
How it works
- Name the consumer principalA principal is the identity requesting access to a resource. in the secret’s resource policyA resource policy is a permission document attached to the secret being accessed.. A principal is the identity making a request; a resource policy is a permission document attached to the resource being accessed.
- Grant secretsmanager:GetSecretValue on that secret in the principal’s identity policyAn identity policy grants permissions to the user or role making a request., the permission document attached to its user or role.
- Encrypt the secret with a customer managed KMS key, a key whose policy the owner controls. The AWS managed key aws/secretsmanager cannot support cross-account access.
- Allow kms:Decrypt in both the owning key policyA key policy defines which principals can use a KMS key. and the reader’s identity policy. A key policy is the permission document attached to a KMS key.
- Retrieve the secret using its ARNAn ARN is an AWS resource identifier that includes its service, Region, account, and resource name.. AWS recommends the complete ARN, the identifier containing the service, Region, account, and resource.
- Protect policy changes with BlockPublicPolicy on PutResourcePolicy and review cross-account access with IAM Access Analyzer. Limit PutResourcePolicy permission because it can let a principal expand its own access.
Exam cues
- If the question says share a secret across accounts, think secret resource policy, reader identity policy, and customer managed KMS key, because both read and decryption permissions must cross the account boundary.
- If the question says secret access is allowed but decryption fails, think key policy and identity permission for kms:Decrypt, because permission to read the secret is separate from permission to use its key.
- If the question says prevent public secret policies, think BlockPublicPolicy, because it checks the resource policy being attached.
Remember
- Cross-account GetSecretValue requires an ARN; prefer the complete ARN.
- aws/secretsmanager cannot be used for cross-account secret access.
- Read permission: secretsmanager:GetSecretValue. Decryption permission: kms:Decrypt.
- Restrict who can call PutResourcePolicy.
Trap: A resource policy on the secret is only part of cross-account access. The reader’s identity policy and the customer managed keyA customer managed key is a KMS encryption key whose policy the customer controls. policy must also permit the required operations.
The role in account 2 calls
GetSecretValueusing the secret's full ARN. Both the identity policy and the secret's resource policy must allow it.Secrets Manager decrypts the value with the secret's customer managed key. The caller needs KMS permission from the key policy and its own identity policy.
Box details (3)
- App role
Needs an identity policy allowing
secretsmanager:GetSecretValueon the secret ARN andkms:Decrypton the key ARN. Use the full secret ARN, not the name.- Secret
A resource policy names the account 2 role. Cross-account access works only for a defined list of actions such as
GetSecretValue.- KMS key
Use a customer managed key. Its key policy and the caller identity policy must allow kms:Decrypt for a cross-account read; aws/secretsmanager cannot be used.
From the AWS docs (8)
- A cross-account Secrets Manager read requires a secret resource policy allowing the consumer principal and an identity policy allowing that principal to read the secret.
- Cross-account secret access cannot use aws/secretsmanager; encrypt with a customer managed KMS key.
- A cross-account reader needs kms:Decrypt allowed by both the owning key policy and its own identity policy.
- GetSecretValue requires an ARN for another account secret; AWS recommends a complete ARN rather than a partial ARN.
- PutResourcePolicy with BlockPublicPolicy helps prevent public access through a secret resource policy.
- IAM Access Analyzer can review cross-account access to Secrets Manager secrets.
- Granting secretsmanager:PutResourcePolicy can allow principals to escalate their access by changing the secret resource policy.
- Cross-account Secrets Manager access is effective only for the documented supported actions, including GetSecretValue.
Rotation workflow and coordination
Secrets Manager Lambda rotation coordinates a new secret versionA secret version is a saved encrypted copy of a secret value. with the credential used by a database or service. Staging labelsA staging label is a name attached to a secret version to identify its role. track the pending, current, and previous versions through the rotation workflow.
How it works
createSecretstores the new version with theAWSPENDINGlabel.setSecretchanges the database or service credential to matchAWSPENDING, andtestSecretuses that value to test access.finishSecretmovesAWSCURRENTto the new version. Secrets Manager assignsAWSPREVIOUSto the former current version.- For retries, the ClientRequestToken identifies the new version and supports idempotencyIdempotency lets a retried rotation step refer to the same pending change without creating it twice., so a retry does not create the same change twice.
In AWS’s CloudFront origin-header example, Lambda rotation updates both the CloudFront custom originAn origin is the backend from which CloudFront retrieves content. header and the WAF rule protecting the origin Application Load Balancer (ALB). The rule accepts both AWSPENDING and AWSCURRENT while the distribution change propagates.
Exam cues
- If the question says a rotation retry must not create the same version twice, think
ClientRequestToken, because it identifies the new version and supports idempotency. - If the question says an Aurora cluster in CloudFormation needs its master password managed in Secrets Manager, think
ManageMasterUserPasswordonAWS::RDS::DBCluster, because the property enables that management. - If the question says a CloudFront origin header must rotate during distribution propagation, think coordinated CloudFront and WAF updates, because the documented rule accepts both pending and current values during the change.
Remember
- Lambda order:
createSecret,setSecret,testSecret,finishSecret. AWSPENDINGis tested beforeAWSCURRENTmoves; the former current version becomesAWSPREVIOUS.- Rotation schedules use UTC
rate()orcron()expressions and can run as often as every four hours.
Trap: Updating the CloudFront header alone is not enough in the documented origin-header rotation. The WAF rule must accept both the current and pending values while the distribution change propagates.
From the AWS docs (9)
- The createSecret step stores the new secret version with the AWSPENDING staging label.
- The setSecret step changes the database or service credential to match AWSPENDING.
- The testSecret step uses AWSPENDING to test access to the database or service.
- The finishSecret step moves AWSCURRENT to the new version, and Secrets Manager assigns AWSPREVIOUS to the former current version.
- The rotation ClientRequestToken identifies the new version and supports idempotency, meaning retries avoid creating the same change twice.
- Secrets Manager rotation schedules use UTC rate() or cron() expressions and can rotate as frequently as every four hours.
- CloudFormation ManageMasterUserPassword enables Secrets Manager management of master credentials for supported RDS and Aurora DB clusters.
- AWS documents Lambda rotation that updates both a CloudFront origin custom header and the WAF rule protecting the origin ALB.
- The documented CloudFront origin-header rotation accepts both AWSPENDING and AWSCURRENT in the WAF rule while the distribution change propagates.
Flashcards
Nothing to review here right now. Pick other topics or another filter.
·
All 34 cards as a list
What does Secrets Manager return when GetSecretValue has no VersionId or VersionStage?
The AWSCURRENT version. AWSPREVIOUS selects the previous version, and AWSPENDING identifies a pending rotation version.
An application must retrieve the previous Secrets Manager value for troubleshooting. Which selector should it use?
VersionStage set to AWSPREVIOUS. If VersionId is also provided, both selectors must identify the same version.
An application reads a Secrets Manager secret encrypted with a customer managed KMS key. Which permissions are required?
secretsmanager:GetSecretValue on the secret and kms:Decrypt on the key.
An ECS service still uses an old Secrets Manager password after rotation. How does it receive an updated environment value?
Launch new tasks, such as through a forced service deployment. Secrets injected at container startup do not update automatically.
What is the Secrets Manager secret value size quota?
65,536 bytes.
A deployment tool supports Parameter Store references but the credential is in Secrets Manager. What reference can it use?
Use /aws/reference/secretsmanager/ followed by the secret name with GetParameter or GetParameters. Secrets Manager permissions still apply.
Can a team create a new CodeGuru Reviewer repository association to discover hardcoded secrets?
No. Since November 7, 2025, only existing repository associations can use CodeGuru Reviewer. Those associations can use its Secrets Manager integration to find exposed secrets.
A database password must rotate automatically with its Secrets Manager value and database kept in sync. Which rotation service fits?
Secrets Manager. Use the database service's managed rotation when supported or configure a Lambda rotation function.
Which Secrets Manager rotation paths use Lambda, and which do not?
Managed rotation for supporting AWS services and managed external secrets rotation do not use Lambda. Other secret types can use a configured Lambda rotation function.
Can Parameter Store Expiration or NoChangeNotification policies replace Secrets Manager automatic rotation for a database password?
No. They delete a parameter or issue a notification. Use Secrets Manager automatic rotation to update both the credential store and database.
An application needs database credentials that stay valid while Secrets Manager rotates them. Which Lambda strategy fits?
Alternating users. It switches between an original and cloned user and requires a separate privileged secret for cloning.
A supported RDS master credential in Secrets Manager should rotate without maintaining a Lambda function. Which rotation path fits?
Managed rotation configured through the supporting database service.
A CloudFormation database secret lacks host and connection fields needed for rotation. Which resource fills them in?
AWS::SecretsManager::SecretTargetAttachment adds the database connection information to the secret JSON.
Secrets Manager createSecret succeeded, but setSecret failed and the database still accepts the old password. What must be repaired?
The target credential update in setSecret. Inspect the rotation logs, access permissions, and network path; creating AWSPENDING alone does not update the database.
A Secrets Manager secret has AWSPENDING on a different version from AWSCURRENT. What happens to the next RotateSecret request?
It returns an error because rotation appears to be in progress. Investigate the failed workflow and version state before retrying.
What is the default refresh interval of the Secrets Manager Python caching component?
One hour. The refresh interval is configurable; the component does not implement cache invalidation.
An application uses the Secrets Manager Python cache and begins rejecting new database connections after rotation. What should the team inspect?
Compare the cached credential with the current version and inspect the refresh configuration. Also check rotation logs and target connectivity before concluding that caching is the cause.
Does an AWSPENDING label remaining after Secrets Manager rotation always mean failure?
No. Successful rotation can leave AWSPENDING on the same version as AWSCURRENT. A separate pending version causes later rotation requests to report rotation in progress.
A Secrets Manager rotation Lambda cannot reach the database from its VPC. Which paths must work?
The function needs a network path to both the target and Secrets Manager, including suitable endpoint access and security group rules.
How can a multi-Region application read local copies of a Secrets Manager secret?
Replicate the primary secret to the enabled destination Regions. Choose a KMS key in each replica Region as needed; rotation at the primary propagates the new value.
Will replicating a Secrets Manager database secret change its connection details to a regional database endpoint?
No. The replica keeps the source connection details. Store additional Region-specific key-value pairs when different endpoints are needed.
A Secrets Manager replica must be rotated and managed independently after recovery. What should the team do?
Promote it to a standalone secret. This stops its link to the primary and allows independent management.
How does a Secrets Manager replica ARN differ from its primary ARN?
Only the Region portion differs.
Must a Secrets Manager secret be replicated before an application in another Region can retrieve it?
No. The application can call the endpoint in the Region that stores the secret. Replication provides regional copies.
An application must read a Secrets Manager secret in another account. What permissions and encryption are required?
Allow the consumer principal in the secret resource policy and its identity policy. Use a customer managed KMS key, with kms:Decrypt allowed by its key policy and the consumer identity policy. Retrieve using the secret ARN.
How can a team prevent a Secrets Manager resource policy from granting public access?
Set BlockPublicPolicy on PutResourcePolicy. Use IAM Access Analyzer to review external access, and restrict who can change the resource policy.
A Secrets Manager resource policy permits a role in another account, but the secret uses aws/secretsmanager. What must change?
Encrypt the secret with a customer managed KMS key and grant the role decrypt permission through the key policy and identity policy.
A cross-account Secrets Manager reader has GetSecretValue but KMS denies decryption. Which policies must allow kms:Decrypt?
The owning KMS key policy and the reader identity policy. Secret permissions alone do not grant key use.
Can a cross-account Secrets Manager GetSecretValue request identify the secret only by name?
No. It must use an ARN; AWS recommends the complete ARN.
What does a Secrets Manager Lambda rotation function do, in order?
createSecret stores AWSPENDING; setSecret changes the target credential; testSecret tests access; finishSecret promotes AWSCURRENT and retains the old version as AWSPREVIOUS.
What prevents retries of a Secrets Manager rotation request from creating the same new version twice?
The ClientRequestToken identifying the version supports idempotency across retries.
What time zone and minimum interval can a Secrets Manager rotation schedule use?
UTC, using rate() or cron(); rotation can run as often as every four hours.
An Aurora DB cluster declared in CloudFormation should have its master password managed in Secrets Manager. Which property enables this?
Set ManageMasterUserPassword on AWS::RDS::DBCluster.
A CloudFront origin header stored in Secrets Manager must rotate without WAF rejecting requests during propagation. What must the rotation coordinate?
Update both the CloudFront custom origin header and the WAF rule on the origin ALB. Temporarily accept AWSPENDING and AWSCURRENT while the distribution change propagates.