In this video, we are going to learn Amazon three core concepts which are the buckets, objects, keys.
S3 Versioning Bucket Policy.
S3 Access Point Access, control list and so on.
So let me start with the bucket.
So a bucket is a container for object storage in Amazon S3.
We can store any number of objects in a bucket and it can have up 100 buckets in a second.
Every object is contained in a bucket.
For example, if we store our photos in a bucket, which name is dock example?
Bucket in the US is two region.
It is addressable using a URL, it is auto generated which including the or bucket name or object name
and it should be auto generated from the Amazon S3.
So basically when we create a bucket, we enter a bucket name and choose a region where the bucket will
reside.
After that, we create a bucket.
We cannot change the name of the bucket or its region.
Bucket name must follow the bucket naming rules.
And we can also configure a bucket to use S3 versioning or other storage management features.
So the second core concept is an object.
Objects are fundamental entities stored in the Amazon S3.
Basically, objects consist of the object data and the metadata.
So the metadata is a set of name value pastes that describe the object.
This space includes some default metadata, for example, the date last modified and the standard HTTP
metadata and so on.
So we can also specify custom metadata at the time that the object is stored.
So another core concept is a keys.
Keys.
We can say that object key.
An object key is a unique identifier for an object within a bucket for every object in a bucket has
exact one key.
So the combination of a bucket object key and optional virgin id uniquely identified for each object.
So we can think of almost an STD as a basic data map between bucket plus key plus virgin and object
itself.
So this will be the unique identifier.
Another core concept is the S3 versioning.
We can use versioning to keep multiple variants of an object in the same bucket.
With SD versioning, we can perverse retrieve and restore every version of the object stored in the
buckets.
So another core concept is a bucket policy.
A bucket policy is a resource based, a IAM policy that we can use to grant access permissions to our
bucket and objects.
Only the bucket owner can associate a policy with a bucket.
So basically the bucket policy is use JSON based access policy language that is standard across the
aid account so we can use the policies to add or deny permissions for objects in a bucket.
Another core concept is the access point.
Amazon access points are network and points with dedicated access policies that describe how data can
be accessed using that endpoint.
So access and points are attached to the buckets that we can use to perform true object operations such
as get object and put object.
So another important core concept is the access control list.
Access.
We can use ACS to grant, read and write permission to authorize users for individual bucket and objects.
Each bucket and object has an ACL attached to it is the sub resources and the ACL defines which account
or groups are granted to access the type of the S3 bucket and object.