Scribd
Upload
109 views

Aws s3 Guide

Amazon S3 is an object storage service that offers simple, durable storage infrastructure at low costs. It stores data as objects within buckets in a distributed system across multiple facilities. S3 provides options for access control, storage classes, static websites, transfer acceleration, versioning, encryption and replication of data. Lifecycle rules can optimize storage costs by transitioning or expiring objects based on configurable actions.

Uploaded by

Antonio Ban
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
109 views

Aws s3 Guide

Amazon S3 is an object storage service that offers simple, durable storage infrastructure at low costs. It stores data as objects within buckets in a distributed system across multiple facilities. S3 provides options for access control, storage classes, static websites, transfer acceleration, versioning, encryption and replication of data. Lifecycle rules can optimize storage costs by transitioning or expiring objects based on configurable actions.

Uploaded by

Antonio Ban
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 4

S3

s3.png
General
Amazon S3 is object storage built to store and retrieve any amount of data from
anywhere on the Internet.
It’s a simple storage service that offers an extremely durable, highly available,
and infinitely scalable data
storage infrastructure at very low costs.

Amazon S3 is a distributed architecture and objects are redundantly stored on


multiple devices across multiple
facilities (AZs) in an Amazon S3 region.

Amazon S3 is a simple key-based object-store.


Keys can be any string, and they can be constructed to mimic hierarchical
attributes.
Files are stored in buckets.
100 buckets per account by default.
You can store unlimited objects in your buckets.
Files can be from 0 bytes to 5TB.
The largest object that can be uploaded in a single PUT is 5 gigabytes.
For objects larger than 100 megabytes use the Multipart Upload capability.
Requester pays function causes the requester to pay (removes anonymous access).
Can provide time-limited access to objects.
Provides read after write consistency for PUTS of new objects.
Provides eventual consistency for overwrite PUTS and DELETES (takes time to
propagate).
You cannot create nested buckets.
Bucket ownership is not transferrable.
Bucket names cannot be changed after they have been created.
If a bucket is deleted its name becomes available again.
Bucket names are part of the URL used to access the bucket.
An S3 bucket is region-specific.
S3 is a universal namespace so names must be unique globally
Additional Capabilities

s3-capabilities.jpg

Storage Classes
S3 Standard (durable, immediately available, frequently accessed).
S3 Intelligent-Tiering (automatically moves data to the most cost-effective tier).
S3 Standard-IA (durable, immediately available, infrequently accessed).S3 One Zone-
IA (lower cost for infrequently accessed data with less resilience).
S3 Glacier (archived data, retrieval times in minutes or hours).
S3 Glacier Deep Archive (lowest cost storage class for long term retention)
Access
By default, a bucket, its objects, and related sub-resources are all private.

There are four mechanisms for controlling access to Amazon S3 resources:

IAM policies.
Bucket policies.
Access Control Lists (ACLs).
Query string authentication (URL to an Amazon S3 object which is only valid for a
limited time).
Resource-based policies:

Attached to buckets and objects.


ACL-based policies define permissions.
ACLs can be used to grant read/write permissions to other accounts.
Bucket policies can be used to grant other AWS accounts or IAM users permission to
the bucket and
objects.
User policies:

Can use IAM to manage access to S3 resources.


Using IAM you can create users, groups, and roles and attach access policies to
them granting them
access to resources.
You cannot grant anonymous permissions in an IAM user policy as the policy is
attached to a user.
User policies can grant permissions to a bucket and the objects in it.

ACLs:

S3 ACLs enable you to manage access to buckets and objects.


Each bucket and object has an ACL attached to it as a subresource.
Bucket and object permissions are independent of each other.
The ACL defines which AWS accounts (grantees) or pre-defined S3 groups are granted
access and the
type of access.
A grantee can be an AWS account or one of the predefined Amazon S3 groups.
When you create a bucket or an object, S3 creates a default ACL that grants the
resource owner full
control over the resource.

Cross account access:

You grant permission to another AWS account using the email address or the
canonical user ID.
However, if you provide an email address in your grant request, Amazon S3 finds the
canonical user ID
for that account and adds it to the ACL.
Grantee accounts can then delegate the access provided by other accounts to their
individual users.

Transfer Acceleration
Amazon S3 Transfer Acceleration enables fast, easy, and secure transfers of files
over long distances between
your client and your Amazon S3 bucket.

S3 Transfer Acceleration leverages Amazon CloudFront’s globally distributed AWS


Edge Locations.
Used to accelerate object uploads to S3 over long distances (latency).
Transfer acceleration is as secure as a direct upload to S3.
You are charged only if there was a benefit in transfer times.
Static Websites
S3 can be used to host static websites.
Cannot use dynamic content such as PHP, .Net, etc.
Automatically scales.
You can use a custom domain name with S3 using a Route 53 Alias record.
When using a custom domain name the bucket name must be the same as the domain
name.
Pre-Signed URLs
pre-signed URLs can be used to provide temporary access to a specific object to
those who do not have AWS
credentials.
By default, all objects are private and can only be accessed by the owner.
To share an object, you can either make it public or generate a pre-signed URL.
The expiration date and time must be configured
Can be used for downloading and uploading S3 objects.
Versioning
Versioning stores all versions of an object (including all writes and even if an
object is deleted).
Versioning protects against accidental object/data deletion or overwrites.
Enables “roll-back” and “un-delete” capabilities.
Versioning can also be used for data retention and archive.
Old versions count as billable sizes until they are permanently deleted.
Enabling versioning does not replicate existing objects.
Can be used for backup.
Once enabled versioning cannot be disabled only suspended.
Can be integrated with lifecycle rules.
Multi-factor authentication (MFA) delete can be enabled.
MFA delete can also be applied to changing versioning settings.

MFA delete applies to:

Changing the bucket’s versioning state.


Permanently deleting an object.
Lifecycle Management
Used to optimize storage costs, adhere to data retention policies and keep S3
volumes well-maintained.
A lifecycle configuration is a set of rules that define actions that Amazon S3
applies to a group of objects.

There are two types of actions:

Transition actions—Define when objects transition to another storage class. For


example, you might
choose to transition objects to the STANDARD_IA storage class 30 days after you
created them, or
archive objects to the GLACIER storage class one year after creating them.
There are costs associated with the lifecycle transition requests. For pricing
information, see Amazon S3
Pricing.
Expiration actions—Define when objects expire. Amazon S3 deletes expired objects on
your behalf.
s3-tiers.png

Encryption
SSE-S3: handled/managed by AWS, AES 256
SSE-KMS: managed with AWS KMS keys
SSE-C: client manages the keys, S3 manages encryption
Replication
SRR - same region replication
CRR - cross-region replication
only works on versioned buckets
this is an async process
no chaining allowed, can't set up replication region A -> region B - > region C
Exam tips
Combine S3 and EC2 in the same AWS Region to optimize performance, reduce latency
and data transfer cost.
Use Byte-Range Fetches for partial data retrieval and parallel download.
Use Transfer Acceleration to minimize latency caused by distance (GB/TB of data
across large geographical
distances or access to a centralized bucket)

You might also like