TLS 1.2 and Direct Read-Only Access to Single File in S3 Public Bucket

0

We have a number of apps that have direct read-only access links to individual files in a public bucket. They access the content in a url structure that starts like this:

https://XXXXXXX.s3.amazonaws.com/

Will Direct Access to https://XXXXXXX.s3.amazonaws.com/ go away on June 28, 2023 if bucket is public?

I'm getting conflicted information on this and want to make sure those will still be accessible. I have run a test on another public bucket that I configured to accept only 1.2 connections and it still appears to be accessible, but I just wanted to double check.

質問済み 1年前250ビュー
2回答
0

Hi,

Are you referring about Amazon S3 Security changes that are effective from April 2023 ? This is applicable for the new buckets creation.

Also If you need public access for a new bucket you can create it as usual and then delete the public access block by calling DeletePublicAccessBlock (you will need s3:PutBucketPublicAccessBlock permission in order to call this function; read Block Public Access to learn more about the functions and the permissions).

Let us know if you are referring something else other than the setting mentioned above.

AWS
回答済み 1年前
  • The bucket is an old bucket that has public access to GetObject enabled. I just wanted to make sure GetObject won't be affected by direct linking to a public URL with the prefix: https://XXXXXXX.s3.amazonaws.com/

0

Hi,

Yes, from June 28, 2023 you must use TLS version 1.2 or later to access content that's stored in your S3 buckets, but regardless of whether it is public or private, so you have nothing to worry about.

Also from April 2023, all new S3 buckets will by default have S3 Block Public Access enabled and access control lists (ACLs) disabled, so you will deliberately need to configure it to be public.

profile picture
エキスパート
回答済み 1年前

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

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

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

関連するコンテンツ