Skip to main content
In this guide you’ll create your first Amazon S3 bucket, explore the main console screens, and upload an object. The steps below preserve the console workflows and screenshots so you can follow along in the same sequence.

1. Open S3 in the AWS Console

Sign in to the AWS Management Console and search for S3. If you have no buckets yet, the S3 dashboard shows a prompt to create one. If you already have buckets, you will see a list and the same “Create bucket” action.
A screenshot of the Amazon S3 web console showing an Account snapshot (storage, object count, average size) and the Buckets panel. The Buckets list is empty and there's a prominent "Create bucket" button.
Important: the region selector at the top of the console controls the default region view, but S3 displays a global list of your buckets. When you create a bucket you explicitly choose the region in which that individual bucket will reside.

2. Create a bucket (name and region)

Click Create bucket and enter a globally unique name for your bucket. Bucket names must be unique across all AWS accounts and regions, so pick a name that is unlikely to be taken (for example, include your initials, project name, or a timestamp).
S3 bucket names are globally unique across all AWS accounts and regions. Use a descriptive, unique name (for example yourname-project-2026) to avoid naming conflicts.
Example of the Create bucket page showing a chosen name and region:
A screenshot of the AWS S3 "Create bucket" configuration page showing the bucket name "kk-demo-123", region set to US East (N. Virginia), and Object Ownership settings with ACLs disabled selected. The lower part of the page shows Block Public Access settings.
For full naming requirements, see the S3 documentation:
A screenshot of the Amazon S3 User Guide showing the "Bucket naming rules" page, with a list of bullet-point rules for naming S3 buckets and a navigation menu on the left. The page includes notes about character limits, allowed characters, and suffix/prefix restrictions.

3. Key Create bucket settings (overview)

On the Create bucket page you’ll configure several important options. Below is a concise summary of the common settings and their purpose:
SettingPurposeTypical choice for beginners
Object ownershipControls ownership for objects uploaded by different AWS accountsBucket owner preferred (or leave default)
Block Public AccessPrevents public access unless explicitly allowedEnabled (recommended)
VersioningRetain prior versions of objectsDisabled (enable if you need object version history)
Default encryptionAutomatically encrypt objects at restDisabled (or enable SSE-S3 / SSE-KMS for production)
Advanced options (Object Lock, MFA Delete)Regulatory retention and protection featuresLeave disabled unless required
For this lesson we leave defaults (bucket locked down, no versioning or default encryption) and click Create bucket. After creation the new bucket appears in the list with its region and creation time — click the bucket name to open its detail view.

4. Bucket Properties

The Properties tab displays high-level metadata and status flags:
  • Bucket ARN (the canonical identifier)
  • Region and creation date
  • Status of features (versioning, default encryption, MFA delete)
  • Links to configure server access logging, CloudTrail data events, event notifications, transfer acceleration, object lock, requester pays, and static website hosting
A screenshot of an AWS S3 bucket Properties page for "kk-demo-123," showing the bucket overview (region US East. N. Virginia, ARN, creation date) and that versioning and MFA delete are disabled. It also shows there are no tags or default encryption configured.
Some property panes show sources of additional visibility and control:
Screenshot of an AWS S3 console showing the "AWS CloudTrail data events" and "Event notifications" sections. Both sections show no entries ("No data events" and "No event notifications") with buttons to configure CloudTrail or create an event notification.

5. Permissions tab — access control

The Permissions tab centralizes who can access the bucket and its objects. By default:
  • Block Public Access is turned on and prevents public access
  • Only the creating AWS account has full access
  • You can add bucket policies, IAM policies, or ACLs to grant other principals access
A screenshot of an AWS S3 bucket settings page showing "Block all public access" turned on and the Bucket policy section reporting "Public access is blocked" with "No policy to display." The panel also includes an Edit button and links to learn more about Amazon S3 Block Public Access.
Be careful when disabling Block Public Access or making objects public. Misconfigured public buckets can expose sensitive data to the internet.

6. Metrics and Management

  • Metrics (CloudWatch) show storage size, object count, and request rates.
  • Management contains lifecycle policies, replication rules, inventory, analytics, and access points — use these to control costs, durability, and access over time.
A screenshot of an Amazon S3 bucket settings page showing the "Replication rules" and "Inventory configurations" sections. Both sections are empty and display buttons to create a replication rule or create an inventory configuration.

7. Upload an object

Open the Objects tab and click Upload (or drag-and-drop files/folders). During upload you can:
  • Add single files or a folder
  • Set the destination path (key prefix)
  • Choose a storage class (Standard, Intelligent‑Tiering, Standard‑IA, One Zone‑IA, Glacier, etc.)
  • Set metadata and permissions (defaults inherit bucket settings)
A screenshot of the AWS S3 "Upload" page showing one file (pexels-julio-nery-1687147.jpg, 2.7 MB) queued for upload. The destination bucket is s3://kk-demo-123 and there's an orange "Upload" button at the bottom.
S3 storage classes trade off cost and availability. For most general-purpose objects choose Standard. You can change the class per object or add lifecycle rules later to move objects to cheaper tiers.
A screenshot of the Amazon S3 console showing a bucket's Permissions and Properties sections, with a Storage class table listing options like Standard, Intelligent‑Tiering, Standard‑IA, One Zone‑IA, and Glacier. The Standard storage class is selected.
Click Upload to start the transfer. When complete the object appears in the bucket’s object list showing name, size, and last modified timestamp.
Screenshot of an Amazon S3 bucket named "kk-demo-123" showing the Objects tab with one file (pexels-julio-nery-1687147.jpg) listed, size 2.7 MB and last modified April 4, 2023.

Next steps and references

Now that you’ve created a bucket and uploaded an object, consider these follow-up topics:
  • Enable versioning and practice restoring older object versions
  • Configure lifecycle policies to move or expire objects automatically
  • Turn on default encryption (SSE-S3 or SSE-KMS) for data-at-rest protection
  • Set up replication rules if you need cross-region redundancy
  • Create fine-grained access using bucket policies and IAM policies
References: This completes the basics: creating an S3 bucket, inspecting its properties and permissions, and uploading your first object. Future lessons will dive deeper into versioning, lifecycle rules, encryption, replication, and advanced access patterns.

Watch Video

Practice Lab