Secrets Manager Now Rotates Databricks and Twilio Credentials for You!
Hi everyone, it's Shii-chan! Here's news that makes rotating forgotten credentials much easier!
AWS What's New
aws.amazon.com
What was announced?
According to AWS What's New, AWS Secrets Manager's managed external secrets now support Databricks and Twilio. You set up rotation from the console or API, with no custom rotation Lambda functions to write or maintain.
Why it matters
Long-lived credentials often stay unrotated because rotation is hard to set up and hard to distribute safely to the applications that use the new value. Secrets Manager takes that work off your hands.
What changes
- No custom code to rotate credentials
- Secrets Manager always returns the current credential, so apps pick up rotated values automatically
- No application code changes required
Dive Deep
The supported credentials are:
- Databricks: personal access tokens used by jobs and CI/CD pipelines
- Databricks: service principal OAuth client secrets used by automation workflows
- Twilio: API keys and Auth Tokens used to send messages and place calls
Each replacement Databricks personal access token keeps the scopes of the token it replaces, so a narrowly scoped token stays narrowly scoped.
You store the credential in Secrets Manager as a managed external secret and set a rotation schedule. These two join existing integrations such as BigID, Cisco Security Platform, Confluent Cloud, and Datadog.
Wrap-up
- Databricks and Twilio now work with managed external secrets
- No rotation Lambda functions needed
- Databricks tokens keep their scopes after rotation
- Apps always get the latest credential with no code changes
Great for anyone running Databricks pipelines or Twilio messaging who tends to put off key rotation!
