Back

Product Update: Deprecating client secrets

StatelyDB is a friendlier way to use DynamoDB! If you’ve wanted the scalability of DynamoDB but found the developer experience frustrating, we’re building a better path. Our elastic schema combines the best of NoSQL and relational databases so you can build faster and stop worrying about every little decision.

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 [email protected] if you need any help migrating off of legacy authentication!

Our blog

Latest from our blog

/images/posts/reducing-dynamodb-read-costs-using-sync.png
Reducing DynamoDB read costs by 60% using Sync
How StatelyDB’s built-in Sync API let DIM drastically reduce read costs.
/images/posts/monitoring-github-action-runners-with-statelydb-aws-cdk-and-lambda.jpg
Monitoring GitHub Action Runners with StatelyDB, AWS CDK, and Lambda
A homegrown simple monitoring solution using StatelyDB and AWS Lambda
/images/posts/migrating-destiny-item-manager-to-statelydb.jpg
Migrating Destiny Item Manager to StatelyDB
Porting a popular web app from Postgres to StatelyDB.

Let's stay in touch.

Join our mailing list to get early access to stay up to date on the future of data management with no regrets.