1
00:00:00,240 --> 00:00:07,860
In this video, we are going to learn Amazon three core concepts which are the buckets, objects, keys.

2
00:00:08,010 --> 00:00:10,260
S3 Versioning Bucket Policy.

3
00:00:10,440 --> 00:00:13,530
S3 Access Point Access, control list and so on.

4
00:00:14,190 --> 00:00:16,080
So let me start with the bucket.

5
00:00:16,350 --> 00:00:20,020
So a bucket is a container for object storage in Amazon S3.

6
00:00:20,040 --> 00:00:26,580
We can store any number of objects in a bucket and it can have up 100 buckets in a second.

7
00:00:26,940 --> 00:00:29,550
Every object is contained in a bucket.

8
00:00:29,580 --> 00:00:35,150
For example, if we store our photos in a bucket, which name is dock example?

9
00:00:35,160 --> 00:00:37,470
Bucket in the US is two region.

10
00:00:37,710 --> 00:00:45,210
It is addressable using a URL, it is auto generated which including the or bucket name or object name

11
00:00:45,210 --> 00:00:49,500
and it should be auto generated from the Amazon S3.

12
00:00:49,830 --> 00:00:56,040
So basically when we create a bucket, we enter a bucket name and choose a region where the bucket will

13
00:00:56,040 --> 00:00:56,760
reside.

14
00:00:56,790 --> 00:00:59,210
After that, we create a bucket.

15
00:00:59,220 --> 00:01:02,370
We cannot change the name of the bucket or its region.

16
00:01:02,370 --> 00:01:05,160
Bucket name must follow the bucket naming rules.

17
00:01:05,160 --> 00:01:10,140
And we can also configure a bucket to use S3 versioning or other storage management features.

18
00:01:10,770 --> 00:01:14,280
So the second core concept is an object.

19
00:01:14,310 --> 00:01:18,390
Objects are fundamental entities stored in the Amazon S3.

20
00:01:18,570 --> 00:01:22,320
Basically, objects consist of the object data and the metadata.

21
00:01:23,160 --> 00:01:27,150
So the metadata is a set of name value pastes that describe the object.

22
00:01:27,180 --> 00:01:33,660
This space includes some default metadata, for example, the date last modified and the standard HTTP

23
00:01:33,660 --> 00:01:35,580
metadata and so on.

24
00:01:35,580 --> 00:01:40,320
So we can also specify custom metadata at the time that the object is stored.

25
00:01:40,770 --> 00:01:43,710
So another core concept is a keys.

26
00:01:44,830 --> 00:01:45,520
Keys.

27
00:01:45,520 --> 00:01:47,320
We can say that object key.

28
00:01:47,320 --> 00:01:52,870
An object key is a unique identifier for an object within a bucket for every object in a bucket has

29
00:01:52,870 --> 00:01:54,160
exact one key.

30
00:01:54,160 --> 00:02:00,550
So the combination of a bucket object key and optional virgin id uniquely identified for each object.

31
00:02:00,550 --> 00:02:07,210
So we can think of almost an STD as a basic data map between bucket plus key plus virgin and object

32
00:02:07,210 --> 00:02:07,810
itself.

33
00:02:07,810 --> 00:02:09,880
So this will be the unique identifier.

34
00:02:10,640 --> 00:02:12,940
Another core concept is the S3 versioning.

35
00:02:12,950 --> 00:02:17,600
We can use versioning to keep multiple variants of an object in the same bucket.

36
00:02:17,630 --> 00:02:23,210
With SD versioning, we can perverse retrieve and restore every version of the object stored in the

37
00:02:23,210 --> 00:02:23,870
buckets.

38
00:02:24,970 --> 00:02:27,520
So another core concept is a bucket policy.

39
00:02:27,580 --> 00:02:33,850
A bucket policy is a resource based, a IAM policy that we can use to grant access permissions to our

40
00:02:33,850 --> 00:02:35,160
bucket and objects.

41
00:02:35,170 --> 00:02:38,450
Only the bucket owner can associate a policy with a bucket.

42
00:02:38,470 --> 00:02:44,160
So basically the bucket policy is use JSON based access policy language that is standard across the

43
00:02:44,170 --> 00:02:50,110
aid account so we can use the policies to add or deny permissions for objects in a bucket.

44
00:02:50,850 --> 00:02:53,670
Another core concept is the access point.

45
00:02:53,820 --> 00:03:00,270
Amazon access points are network and points with dedicated access policies that describe how data can

46
00:03:00,270 --> 00:03:02,010
be accessed using that endpoint.

47
00:03:02,010 --> 00:03:08,310
So access and points are attached to the buckets that we can use to perform true object operations such

48
00:03:08,310 --> 00:03:10,410
as get object and put object.

49
00:03:10,830 --> 00:03:14,460
So another important core concept is the access control list.

50
00:03:14,490 --> 00:03:15,510
Access.

51
00:03:15,510 --> 00:03:21,870
We can use ACS to grant, read and write permission to authorize users for individual bucket and objects.

52
00:03:22,230 --> 00:03:29,520
Each bucket and object has an ACL attached to it is the sub resources and the ACL defines which account

53
00:03:29,520 --> 00:03:34,170
or groups are granted to access the type of the S3 bucket and object.
