Stash

UI Files to Stash Migration Guide ​

Migration Steps ​

  1. Update your API Integrations
    • Request your client credentials. We'll probably reach out to you first!
    • Modify your existing API calls.
    • Visit the API documentation page for more details on feature changes
  2. Test and Validate Thoroughly test your applications to ensure that everything works similarly to how they do today.
  3. Let us know if you have questions or how we can help!

How can I access my existing files? ​

  • After reaching out to us for your client credentials, we will start the process of copying your existing files to S3 via AWS DataSync.
  • We request that you look over and verify your file inventory and clean up any files that might be used for testing purposes.
  • Your files and metadata will be automatically mapped to the Stash application and will be accessible via their existing uuid identifiers.

What features are changing/going away? ​

  • Stash will no longer act as a proxy for download. Applications can download files directly from S3 by retrieving the pre-signed url from Stash.
  • Stash will no longer provide long-lived public urls (TTL URLs). We believe that AWS S3's pre-signed urls are a better fit for these use cases and remove Stash as a security vulnerability.
  • Metadata searching has been retired
  • Client to Client implicit/explicit sharing of files has been retired. For security purposes, it is recommended you share files only with those who satisfy your application's access controls.
  • File expiration scheduling via API. In non-prod environments file assets are set to automatically expire in 30 days. A delete API has been added for ad-hoc file deletion. Specifying a time-to-live (TTL) during upload is no longer supported.