Getting started by using the Amazon Web Services Management Console - Amazon Simple Storage Service
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).

Getting started by using the Amazon Web Services Management Console

With Amazon S3 on Outposts, you can create S3 buckets on your Amazon Outposts and easily store and retrieve objects on premises for applications that require local data access, local data processing, and data residency. S3 on Outposts provides a new storage class, S3 Outposts (OUTPOSTS), which uses the Amazon S3 APIs, and is designed to store data durably and redundantly across multiple devices and servers on your Amazon Outposts. You communicate with your Outpost bucket by using an access point and endpoint connection over a virtual private cloud (VPC). You can use the same APIs and features on Outpost buckets as you do on Amazon S3 buckets, including access policies, encryption, and tagging. You can use S3 on Outposts through the Amazon Web Services Management Console, Amazon Command Line Interface (Amazon CLI), Amazon SDKs, or REST API. For more information, see What is Amazon S3 on Outposts?

To get started with S3 on Outposts by using the console, see the following topics. To get started by using the Amazon CLI or Amazon SDK for Java, see Getting started by using the Amazon CLI and SDK for Java.

Create a bucket, an access point, and an endpoint

The following procedure shows you how to create your first bucket in S3 on Outposts. When you create a bucket using the console, you also create an access point and an endpoint associated with the bucket so that you can immediately begin storing objects in your bucket.

  1. Sign in to the Amazon Web Services Management Console and open the Amazon S3 console at

  2. In the left navigation pane, choose Outposts buckets.

  3. Choose Create Outposts bucket.

  4. For Bucket name, enter a Domain Name System (DNS)-compliant name for your bucket.

    The bucket name must:

    • Be unique within the Amazon Web Services account, the Outpost, and the Amazon Web Services Region that the Outpost is homed to.

    • Be 3–63 characters long.

    • Not contain uppercase characters.

    • Start with a lowercase letter or number.

      After you create the bucket, you can't change its name. For information about naming buckets, see Bucket naming rules.


      Avoid including sensitive information such as account numbers in the bucket name. The bucket name is visible in the URLs that point to the objects in the bucket.

  5. For Outpost, choose the Outpost where you want the bucket to reside.

  6. Under Bucket Versioning, set the S3 Versioning state for your S3 on Outposts bucket to one of the following options:

    • Disable (default) – The bucket remains unversioned.

    • Enable – Enables S3 Versioning for the objects in the bucket. All objects added to the bucket receive a unique version ID.

    For more information about S3 Versioning, see Managing S3 Versioning for your S3 on Outposts bucket.

  7. (Optional) Add any optional tags that you would like to associate with the Outposts bucket. You can use tags to track criteria for individual projects or groups of projects, or to label your buckets by using cost-allocation tags.

    By default, all objects stored in your Outposts bucket are stored by using server-side encryption with Amazon S3 managed encryption keys (SSE-S3). You can also explicitly choose to store objects by using server-side encryption with customer-provided encryption keys (SSE-C). To change the encryption type, you must use the REST API, Amazon Command Line Interface (Amazon CLI), or Amazon SDKs.

  8. In the Outposts access point settings section, enter the access point name.

    S3 on Outposts access points simplify managing data access at scale for shared datasets in S3 on Outposts. Access points are named network endpoints that are attached to Outposts buckets that you can use to perform S3 object operations. For more information, see Access points.

    Access point names must be unique within the account for this Region and Outpost, and comply with the Access points restrictions and limitations.

  9. Choose the VPC for this Amazon S3 on Outposts access point.

    If you don't have a VPC, choose Create VPC. For more information, see Creating access points restricted to a virtual private cloud.

    A virtual private cloud (VPC) enables you to launch Amazon resources into a virtual network that you define. This virtual network closely resembles a traditional network that you would operate in your own data center, with the benefits of using the scalable infrastructure of Amazon.

  10. (Optional for an existing VPC) Choose an Endpoint subnet for your endpoint.

    A subnet is a range of IP addresses in your VPC. If you don't have the subnet that you want, choose Create subnet. For more information, see Networking for S3 on Outposts.

  11. (Optional for an existing VPC) Choose an Endpoint security group for your endpoint.

    A security group acts as a virtual firewall to control inbound and outbound traffic.

  12. (Optional for an existing VPC) Choose the Endpoint access type:

    • Private – To be used with the VPC.

    • Customer owned IP – To be used with a customer-owned IP address pool (CoIP pool) from within your on-premises network.

  13. (Optional) Specify the Outpost access point policy. The console automatically displays the Amazon Resource Name (ARN) for the access point, which you can use in the policy.

  14. Choose Create Outposts bucket.


    It can take up to 5 minutes for your Outpost endpoint to be created and your bucket to be ready to use. To configure additional bucket settings, choose View details.

Next steps

With Amazon S3 on Outposts, object data is always stored on the Outpost. When Amazon installs an Outpost rack, your data stays local to your Outpost to meet data-residency requirements. Your objects never leave your Outpost and are not in an Amazon Web Services Region. Because the Amazon Web Services Management Console is hosted in-Region, you can't use the console to upload or manage objects in your Outpost. However, you can use the REST API, Amazon Command Line Interface (Amazon CLI), and Amazon SDKs to upload and manage your objects through your access points.

After you create an S3 on Outposts bucket, access point, and endpoint, you can use the Amazon CLI or SDK for Java to upload an object to your bucket. For more information, see Upload an object to an S3 on Outposts bucket.