liveBook · Manning

AWS Secrets Manager

As explained in Grokking Software Architecture

AWS Secrets Manager is an AWS service for storing, retrieving, and managing application secrets.

A password fetched at startup can become a trap: when it expires, database requests fail. AWS Secrets Manager can automate password rotation, but the application must also recover gracefully. section 11.5.3

When a database rejects an expired password, the application should:

  • Catch the authentication error, clear the cached password, fetch the fresh secret, and retry the operation. section 11.5.3
  • Use a connection pool or framework integration to avoid repeating this recovery logic around every query. section 11.5.3
Figure 11.7 Mature architectures "catch" authentication failures and swap in fresh secrets without stopping the application.

Shows how an application can catch an authentication failure and switch to fresh credentials without stopping. section 11.5.3

How Grokking Software Architecture covers it

How deep it goes
Details a four-step recovery path without showing how to configure secret rotation.
Examples
Uses a midnight password change, 30-day automatic rotation, and a Spring Boot connection-pool scenario.
What you can do after
Apply AWS Secrets Manager rotation by designing credential-refresh and retry behavior for database authentication failures.
How it connects
Connects secret rotation with resilience patterns, credential caching, database connection pools, and Spring Boot integrations.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.