AWS S3 - Simple Storage Service Explained

-

Amazon S3 (Simple Storage Service) is one of the most important and widely used AWS services. It is a highly scalable, durable, and secure object storage service where you can store any type of file—images, videos, PDFs, logs, backups, or application data.

Whether you're building a web application, mobile backend, analytics pipeline, or simply need cloud storage, S3 is often the first service developers work with.

What is Amazon S3?

Amazon S3 is an object storage service, which means data is stored as objects inside containers called buckets. Unlike traditional file systems, S3 is designed for:

  • High durability (99.999999999%)
  • High scalability
  • Global availability

It is ideal for storing:

  • Images, videos, and documents
  • Application uploads
  • Static website assets
  • Logs and analytics data
  • Backups and archives

S3 is accessible from anywhere over the internet or directly from AWS applications and services.

Key Concepts: Bucket, Object, Key, Region

Before using S3, you must clearly understand four core concepts:

1. Bucket

A bucket is a top-level container where your objects are stored. Bucket names must be globally unique across all AWS accounts. All S3 objects must belong to a bucket.

2. Object

An object is any file you upload to S3—image, PDF, video, ZIP, or log file. Each object contains:

  • File data
  • Metadata
  • Permissions

3. Key

The key is the full unique path of an object within a bucket. It is similar to a file path in a filesystem:

photos/2024/sunset.png

4. Region

Each bucket is created in a specific AWS region, such as Mumbai (ap-south-1) or US-East-1. Placing buckets close to your users can reduce latency and optimize performance.

S3 also supports virtual folders to organize your data, although these are logical prefixes, not actual directories.

How to Create an S3 Bucket (Step Overview)

When creating a bucket from the AWS Management Console, you configure several key settings:

  • Region: Choose where your bucket will reside. Typically the region closest to your application.
  • Bucket Type: General purpose (recommended) or Directory bucket.
  • Bucket Name: Must be globally unique, e.g., my-app-bucket-v1.
  • Object Ownership / ACLs:
    • ACLs disabled (recommended): Only account owner manages access.
    • ACLs enabled: Allows complex cross-account control.
  • Block Public Access: Enabled by default — keeps your bucket private.
  • Versioning: Maintains old versions of objects for accidental delete/overwrite protection.
  • Tags: Add cost allocation tags like env=prod.
  • Default Encryption: Encrypt all uploaded objects using SSE-S3 or AWS KMS.
  • Object Lock: Prevents deletion/modification (used for compliance).

After clicking Create Bucket, the bucket appears in your S3 dashboard and is ready for use.

Uploading Files and Folders in S3

Once your bucket is created, uploading data is simple:

  • Create a folder such as images or logs.
  • Use the Upload button to select files.
  • Confirm the destination folder.
  • Complete the upload.

After uploading, S3 displays object details such as:

  • Object name
  • Size
  • Last modified
  • Amazon Resource Name (ARN)
  • S3 URL (used for accessing the file)

S3 Storage Classes and When to Use Them

S3 offers multiple storage classes designed for different access patterns and cost requirements. Choosing the right class can significantly reduce your bill.

📌 Most Common S3 Storage Classes

1. S3 Standard

Best for frequently accessed data like website assets, app uploads, and images.

2. S3 Intelligent-Tiering

Automatically moves objects between tiers based on usage. Ideal for unpredictable access patterns.

3. S3 Standard-IA (Infrequent Access)

For data accessed occasionally but requiring fast retrieval.

4. S3 Glacier Instant Retrieval

Archive storage with near-instant access. Great for logs retained for compliance.

5. S3 Glacier Flexible Retrieval

Long-term archival storage with slower restore times (minutes/hours).

6. S3 Glacier Deep Archive

The cheapest storage class. Best for “store and forget” data accessed very rarely.

Each class differs in storage cost per GB, retrieval cost, and performance.

S3 Pricing Basics

S3 pricing depends mainly on:

  • Storage (per GB per month): Standard is more expensive; archival classes are cheaper.
  • Storage class: High-performance = higher cost; deep archive = lowest cost.
  • Requests: PUT, GET, COPY, LIST requests incur small charges.
  • Data Transfer: Data leaving AWS (internet) costs extra.

AWS Free Tier includes a limited amount of S3 storage (e.g., 5 GB), which helps beginners get started at zero cost.

Manual vs Programmatic Access

In demos and tutorials, files are often uploaded manually using the S3 console. But real-world applications rarely do this.

Production-grade systems use programmatic access:

  • AWS SDKs (Java, Python, Node.js)
  • AWS CLI
  • Spring Boot backend services

Applications authenticate using IAM users or IAM roles to upload, download, and delete objects.

This sets the foundation for building a Spring Boot → S3 file upload API, which is the next logical step in your learning.

Key Takeaways

  • Amazon S3 is a secure, scalable, and durable cloud object storage service.
  • Buckets, objects, keys, regions, and folders are core concepts every developer must know.
  • Bucket settings like encryption, versioning, access control, and tags are critical for security and reliability.
  • S3 storage classes help optimize cost based on access frequency.
  • Manual file uploads are only for learning; real apps (e.g., Spring Boot APIs) use programmatic S3 operations.

With these fundamentals, you are ready to start building real cloud applications that use Amazon S3 securely and efficiently.

Comments

Post a Comment

Popular posts from this blog

Spring Boot on AWS EC2: Upload to S3 Securely Using IAM Role

-
When running a Spring Boot application on AWS EC2 , the most common security mistake is hardcoding AWS access keys inside application.properties . This is unnecessary and risky. AWS already provides a secure mechanism: IAM Roles attached to EC2 . In this blog, you will learn how to upload and download files to Amazon S3 from Spring Boot running on EC2 without any access keys , using: Spring Profiles AWS SDK v2 Instance Metadata Service (IMDS) IAM Roles Why Access Keys Are a Bad Idea on EC2 Typical S3 setups use: Access key Secret key Region Bucket This works only for local development. It should NOT be used on EC2. Problems with access keys: Stored in config or code (high risk) Might leak through Git, logs, or screenshots Require manual rotation Not needed if app runs on EC2 AWS automatically manages temporary credentials using the EC2 Instance Profile (IAM Role) . Architecture: EC2 → IAM Role → S3 Spring Boot app r...
Read more

Java Streams Intermediate Operations Explained with Examples

-
Image
The Java Stream API lets you process collections in a fluent, declarative style. In this post, we’ll walk through the most useful intermediate operations with simple examples. Note: Examples below use Java 8 compatible collect(Collectors.toList()) . If you’re on Java 16+, you can replace it with toList() . 1) filter() — Select elements by a condition Keeps only elements that match the predicate. List<Integer> list = Arrays.asList(1,2,3,4,5,6,7,8,9,10); List<Integer> res = list.stream() .filter(num -> num % 2 != 0) // keep only odd numbers .collect(Collectors.toList()); System.out.println(res); // [1, 3, 5, 7, 9] 2) map() — Transform each element Applies a function to every element and returns a stream of results. List<String> strs = Arrays.asList("rama", "anjaneya", "krishna"); List<String> upper = strs.stream() .map(String::toUpperCase) .collect(Collectors.toList()); System.o...
Read more

ConcurrentHashMap vs Synchronized HashMap in Java

-
Image
Introduction In multi-threaded Java applications, managing shared data safely and efficiently is crucial. Two common approaches are using Synchronized HashMap (via Collections.synchronizedMap(...) ) and ConcurrentHashMap . While both aim to provide thread-safety, their implementations and performance characteristics differ significantly. This post explores these differences in detail. What is a Synchronized HashMap? Created by wrapping a regular HashMap using: Map<K, V> syncMap = Collections.synchronizedMap(new HashMap<>()); Enforces synchronization at the object level , meaning only one thread can access the map at any time (read or write). Supports null keys and values since it relies on HashMap behavior. Iterators are fail-fast , throwing ConcurrentModificationException if the map is modified while iterating. Simpler implementation, suitable when concurrency is low or performance is not cri...
Read more