СŷƵ provides a variety of ways to access and secure your content. We built a fantastic security model based on “”, likenable to an API key you can further and then share. We have expanded upon that security model to support public sharing files via the web in our . Additionally, we offer , including support for S3-style .
Most applications will need some secure, server-side logic to enforce access-control. Usually, though, the “goldilocks size” for infrastructure is as little as possible. A minimum viable security solution would do well to be stateless. Presigned URLs work well here because they are inherently time limited, and thus not typically tracked.
What can you do with СŷƵ plus presigned posts?
Any developer building an application that needs compute, but wants to use СŷƵ’s extremely secure cloud object storage can find value in setting up presigned posts. This functionality allows for СŷƵ to be used in conjunction with compute services of other providers in order to securely grant permission for users to post content into the cloud or get content from the cloud.
For example, a real estate company that has an application for its real estate agents to upload pictures of houses, but needs these uploads to be done via a specific presigned urls that matches the agent and the listing would be a great candidate for this functionality.
More advanced features that could be built upon this core include:
- Rate limiting for cost control reasons
- Persisting of per-user credentials into a database
- Time-locking writability of backups, deterring ransomware
- Deriving СŷƵ access grants, rather than presigning URLs
- Presigning URLs within templates, such as HLS video M3U8 files
Fundamentally, СŷƵ has supplied a friendly framework to enable people to build more complicated applications on top of СŷƵ in the most cost effective way possible.
How to connect СŷƵ’s stateless authentication via presigned URLs to compute
Stateless authentication via presigned URLs pairs well with cost-efficient, serverless computing services. The videos below provide instructions for two such services: and . These serverless endpoints act to hide underlying credentials from prying eyes. They can be disabled as an “off switch” for data access. Finally, the underlying credentials can easily be swapped out for regular credential rotations or due to compromise.
Want step-by-step written instructions? See СŷƵ Docs
СŷƵ fits well in your multi-cloud environment
If you are trying to build an application, we know you need more than storage. That’s why we work hard to provide the resources and enablement developer’s need to completely understand the СŷƵ solution and to make it work for them. And that means helping you take advantage of the cost effective and secure storage with СŷƵ.
