Access points for general purpose buckets naming rules, restrictions, and limitations - Amazon Simple Storage Service
Naming rules for Amazon S3 access points for general purpose bucketsRestrictions and limitations for access points for general purpose buckets
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Access points for general purpose buckets naming rules, restrictions, and limitations

Access points for general purpose buckets are named network endpoints attached to a bucket to simplify managing data. When you create an access point you choose a name and the Amazon Web Services Region to create it in. The following topics provide information about access point naming rules and restrictions and limitations.

Naming rules for Amazon S3 access points for general purpose buckets

When you create an access point for a general purpose bucket, you choose its name and the Amazon Web Services Region to create it in. Unlike general purpose buckets access point names do not need to be unique across Amazon Web Services accounts or Amazon Web Services Regions. The same Amazon Web Services account may create access points with the same name in different Amazon Web Services Regions or two different Amazon Web Services accounts may use the same access point name. However, within a single Amazon Web Services Region an Amazon Web Services account may not have two identically named access points.

Note

If you choose to publicize your access point name, avoid including sensitive information in the access point name. Access point names are published in a publicly accessible database known as the Domain Name System (DNS).

Access point names must be DNS-compliant and must meet the following conditions:

  • Must be unique within a single Amazon Web Services account and Amazon Web Services Region

  • Must begin with a number or lowercase letter

  • Must be between 3 and 50 characters long

  • Can't begin or end with a hyphen (-)

  • Can't contain underscores (_), uppercase letters, spaces, or periods (.)

  • Can't end with the suffix -s3alias. This suffix is reserved for access point alias names. For more information, see Access point for general purpose buckets aliases.

Restrictions and limitations for access points for general purpose buckets

Amazon S3 access points for general purpose buckets have the following restrictions and limitations:

  • Each access point for general purpose buckets is associated with exactly one general purpose bucket, which you must specify when you create the access point. After you create an access point, you can't associate it with a different bucket. However, you can delete an access point, and then create another one with the same name and associate that new access point with a different bucket.

  • After you create an access point, you can't change its virtual private cloud (VPC) configuration.

  • Access point policies are limited to 20 KB in size.

  • You can create a maximum of 10,000 access points per Amazon Web Services account per Amazon Web Services Region. If you need more than 10,000 access points for a single account in a single Region, you can request a service quota increase. For more information about service quotas and requesting an increase, see Amazon service quotas in the Amazon Web Services General Reference.

  • You can't use an access point as a destination for S3 Replication. For more information about replication, see Replicating objects within and across Regions.

  • You can't use S3 access point aliases as the source or destination for Move operations in the Amazon S3 console.

  • You can address access points only by using virtual-host-style URLs. For more information about virtual-host-style addressing, see Accessing an Amazon S3 general purpose bucket.

  • API operations that control access point functionality (for example, PutAccessPoint and GetAccessPointPolicy) don't support cross-account calls.

  • You must use Amazon Signature Version 4 when making requests to an access point by using the REST APIs. For more information about authenticating requests, see Authenticating Requests (Amazon Signature Version 4) in the Amazon Simple Storage Service API Reference.

  • Access points only support requests over HTTPS. Amazon S3 will automatically respond with an HTTP redirect for any requests made via HTTP, to upgrade the request to HTTPS.

  • Access points don't support anonymous access.

  • Cross-account access points don’t grant you access to data until you are granted permissions from the bucket owner. The bucket owner always retains ultimate control over access to the data and must update the bucket policy to authorize requests from the cross-account access point. To view a bucket policy example, see Configuring IAM policies for using access points for general purpose buckets.

  • In Amazon Web Services Regions where you have more than 1,000 access points, you can't search for an access point by name in the Amazon S3 console.

  • When you're viewing a cross-account access point in the Amazon S3 console, the Access column displays Unknown. The Amazon S3 console can't determine if public access is granted for the associated bucket and objects. Unless you require a public configuration for a specific use case, we recommend that you and the bucket owner block all public access to the access point and the bucket. For more information, see Blocking public access to your Amazon S3 storage.