Migrating from Y-Sweet Cloud to Jamsocket
In October 2024, we added first-class support for running Y-Sweet on Jamsocket. As a result, we are deprecating Y-Sweet Cloud and migrating its users to Jamsocket. We expect the transition to require very little effort, with most users needing only to:
- create a Y-Sweet service from the Jamsocket dashboard with an associated S3 bucket, and
- swap out their Connection String for a new one from Jamsocket.
All Y-Sweet client libraries are compatible with Y-Sweet on Jamsocket, and no code updates are strictly required.
Creating a new Y-Sweet service on Jamsocket
What does this mean for my data?
If you used our Bring Your Own Storage feature on Y-Sweet Cloud, simply connect Y-Sweet on Jamsocket to the same bucket, and your data will be there.
If you used our storage, contact us and we will migrate your data to Y-Sweet on Jamsocket.
What’s the timeline?
We plan to complete the transition from Y-Sweet Cloud to Jamsocket by December 1, 2024.
What code change(s) do I need to make?
No code changes are required when migrating to Y-Sweet on Jamsocket, you’ll just need to configure a new Y-Sweet connection string.
Though it is not required, we recommend upgrading to v0.5.0 of the Y-Sweet client libraries, as this version contains important bug fixes and reconnection support. The primary change to be aware of when upgrading to v0.5.0 is the new Auth Endpoint configuration.
Who can I reach out to with questions?
If you have any questions or concerns, don’t hesitate to drop us a note at hi@jamsocket.com.