Back

Product Update: Deprecating client secrets

We've made it easier to configure authentication

Author Photo
Stately Team
, 1 minute read

We’ve made requesting and revoking Access Keys self-service, so you don’t need to get them from our team. You will need to create new Access Keys when using the latest versions of our SDKs.

What’s New: You need to visit the console and create a new Access Key. Click the Manage Access Keys button on the Dashboard page.

  • You will need to update to the latest version of our SDK to use an Access Key.
  • See the Creating a Client section of our documentation for help on configuring Access Keys.

Breaking Changes:

  • On February 15th any API calls using STATELY_CLIENT_ID and STATELY_CLIENT_SECRET will stop working.
  • SDK versions that use the legacy authentication will be revoked on March 1st.

Need Help? Email us at support@stately.cloud if you need any help migrating off of legacy authentication!

Latest from our blog

/images/posts/encoding-sortable-binary-database-keys.png
Solving sorting for nested keys with mixed data types
Author Photo
Ben Hollis
August 25, 2025
/images/posts/aws-just-explained-why-you-need-elastic-schema.jpg
It's a lot of work that your database could do for you
Author Photo
Ben Hollis
August 7, 2025
/images/posts/sea-creatures-evolve-into-crabs-databases-evolve-into-dynamodb.jpg
As companies grow, their database infrastructure always ends up looking very familiar…
Author Photo
Ben Hollis
July 29, 2025
View all posts

Using DynamoDB today? Want to try StatelyDB?