Best and performant way of restricting user access to S3?

0

We are currently signing the url's for Cloudfront, but are experiencing some noticeable performance concerns when it comes to signing the url's - taking 40ms or so per image with Python using the private key.

We want to minimize writes to the database, hence we have come up with caching the 14 day access URL for 7 days with Redis, if any performance gains are retrievable from this.

  • But we are really curious if there exists any better way of doing this, or if we have made the correct design for retrieving the images?
  • The images use user_UUID/image_UUID as their url by default within S3, perhaps the obfuscation + throttling is enough for some use cases?
回答なし

ログインしていません。 ログイン 回答を投稿する。

優れた回答とは、質問に明確に答え、建設的なフィードバックを提供し、質問者の専門分野におけるスキルの向上を促すものです。

質問に答えるためのガイドライン

関連するコンテンツ