Securing content behind a paywall?

We’ve got a project where content (images, PDF’s etc) are behind a paywall and should only be available to paid users.

We’re using Xano as the backend and AWS (currently) for storage so can’t use Bubble’s private files and we’re feeling a bit stuck on security for this content. It needs to be there for usage by the user, but we don’t want a publicly accessible url so that they could copy/paste the file’s url and share to others.

I’d imagine this is relatively common so are there any best practices for this situation?

You can set up AWS to “issue” private-view-only urls

1 Like