# AWS Secrets Manager now auto-rotates your Paddle and GitLab keys!

Hey there, it's me, Shii-chan! Today's news makes secret management a little easier again.

## What was announced?

According to AWS's What's New, AWS Secrets Manager's managed external secrets now supports Paddle API keys and GitLab access tokens. Managed external secrets let you rotate third-party credentials automatically, directly from AWS Secrets Manager.

## The story so far

Managed external secrets already worked with BigID, Confluent Cloud, Datadog, MongoDB Atlas, Salesforce, and Snowflake. Paddle and GitLab are simply the newest members joining that lineup.

## What changes

If you use Paddle or GitLab, the manual work of swapping keys and tokens can now be handed off to Secrets Manager. Because the rotation is managed, there's less worry about an app breaking at the exact moment a credential gets replaced.

## Dive Deep

For Paddle, rotation uses Paddle's native rotation API. It offers a configurable grace period so your applications can transition to new keys without interruption.

For GitLab, you can rotate three types of access tokens — Personal Access Tokens, Group Access Tokens, and Project Access Tokens — using GitLab's atomic rotation mechanism.

These integrations are available in all AWS Regions where AWS Secrets Manager managed external secrets is supported. For details, check out the [AWS Secrets Manager managed external secrets documentation](https://docs.aws.amazon.com/secretsmanager/latest/userguide/managed-external-secrets.html).

## Wrap-up

- Paddle and GitLab were added to Secrets Manager managed external secrets
- Paddle uses its native API plus a grace period for interruption-free rotation
- GitLab covers Personal / Group / Project access tokens
- They join the existing BigID, Confluent Cloud, Datadog, MongoDB Atlas, Salesforce, and Snowflake integrations

This is a great fit for teams that bill with Paddle and manage source with GitLab, and want to automate credential rotation!