EXPERIMENT - 4

AIM: Create an AWS account, configure IAM users, create and manage S3 buckets.

Amazon AWS account creation.

Simulation scenario
For this simulation, you create users and groups to enable permissions that
support the following business scenario.

Your company is growing its use of AWS services, and is using many Amazon
Elastic Compute Cloud (Amazon EC2) instances and Amazon Simple Storage
Service (Amazon S3) buckets. You hire three new employees and want to give
access to new staff, based on their job function, as indicated in the following table.
User In Group Permissions

user-1 S3-Support Read-only access to Amazon S3

user-2 EC2-Support Read-only access to Amazon EC2

user-3 EC2-Admin View, start, and stop Amazon EC2 instances

Page | 18
Task 1: Creating a custom IAM policy

In this task, you create a custom IAM policy for limited administrative Amazon EC2 access.
The permissions will give any user attached to the policy access to view, start, and stop EC2
instances. You will create the policy now, so that you can use it later.

1. In the AWS Management Console, enter in the search field.

o Note: To record your entry, press Enter on your keyboard or choose any place
outside of the entry field.
2. Then, choose IAM from the search results.
3. In the left navigation pane, choose Policies.

IAM offers a wide variety of AWS managed policies. These are created and administered by
AWS. However, you can create your own policies that meet your specific needs.

4. Choose Create policy.

5. For the Policy editor, choose JSON.

The policy editor field generates a policy template where you can start editing your
code. You can also delete the existing code and paste your own code into the policy
editor.

The following custom JSON policy provided for you grants the user the access to
start, stop, and view nano-type and micro-type instances. If this is the only policy that
is attached to the user, the user will not have access to perform any other actions.

{
"Version": "2012-10-17",
"Statement": [
{
"Condition": { "ForAllValues:StringLikeIfExists": { "ec2:InstanceType": [
"*.nano",
"*.micro" ] },
"StringEqualsIfExists": { "ec2:Owner": "amazon" } },
"Action": [ "ec2:Describe*", "ec2:StartInstances", "ec2:StopInstances" ],
"Resource": [ "*" ],
"Effect": "Allow" } ] }

6. Copy and paste the preceding code into the policy editor field.

NOTE: Keyboard shortcuts won’t work for this simulation. To simulate replacing the
existing code with the preceding code, follow these specific steps:

o Open the context (right-click) menu for the policy editor field.
o From the menu, choose Select all.
o Open the context (right-click) menu for the highlighted text.
o From the menu, choose Paste.
7. Choose the scroll bar to scroll down, then choose Next.
8. In the Policy name field, enter.
o Note: To record your entry, press Enter on your keyboard or choose any place
outside of the entry field.
9. Choose the scroll bar to scroll down, then choose Create policy.
Page | 19
You have just created a custom managed policy that provides a user with the ability to start,
stop, and view instances. This policy will be used for the EC2-Admin group.

Task 2: Creating user groups with permissions

In this task, you create a user group for each of the three roles and attach the appropriate
permission to the group. Users will inherit the permissions of the group or groups that they
are added to. You can attach permissions directly to a user. However, it is generally a best
practice to manage permissions by adding users to user groups, especially when there are
multiple users with the same set of permissions.

Create the EC2-Admin user group

1. In the left navigation pane, choose User groups.

2. Choose Create group.
3. In the User group name field, enter EC2-Admin.
o Note: To record your entry, press Enter on your keyboard or choose any place
outside of the entry field.
4. Choose the scroll bar to scroll down.
5. In the Attach permissions policies search field, enter EC2-Admin-Policy.
o Note: To record your entry, press Enter on your keyboard or choose any place
outside of the entry field.

This is the policy that you created in Task 1.

6. Select the EC2-Admin-Policy check box.

7. Choose Create user group.

Create the EC2-Support group

Page | 20
 8. Use what you learned from the previous steps to create the EC2-Support group. For
the name of the group, use EC2-Support, and for the policy, use
AmazonEC2ReadOnlyAccess.

Create the S3-Support group

9. Use what you learned from the previous steps to create the S3-Support group. For the
name of the group, use S3-Support, and for the policy, use
AmazonS3ReadOnlyAccess.

Task 3: Creating users and adding them to groups

Create user-1 and add to the S3-Support user group

1. In the left navigation pane, choose Users.
2. Choose Create user.
3. In the User name field, enter user-1.
4. Select the Provide user access to the AWS Management Console check box.
5. For User type, choose I want to create an IAM user.
6. Choose the scroll bar and scroll down. Then, for Console password, choose Custom
password.
7. Select the Show password check box.
8. In the Custom password field, enter Sim-Password1.
9. Clear the User must create a new password at next sign-in check box.
10. Choose Next.
11. Keep the Permissions options default setting Add user to group selected.
12. In the User groups list, select the S3-Support check box.
13. Choose Next.
14. Review the user details.
15. Choose Create user.
Page | 21
 16. On the Console sign-in details panel, choose Show to review the Console password.
17. Choose Return to users list.

Create user-2 and add to the EC2-Support user group

18. Choose Create user.
19. In the User name field, enter user-2.
20. Select the Provide user access to the AWS Management Console check box.
21. For User type, choose I want to create an IAM user.
22. Choose the scroll bar and scroll down. Then, for Console password, choose Custom
password.
23. Select the Show password check box.
24. In the Custom password field, enter Sim-Password2.
• Note: To record your entry, press Enter on your keyboard or choose any place
outside of the entry field.
25. Clear the User must create a new password at next sign-in check box.
26. Choose Next.
27. Keep the Permissions options default setting Add user to group selected.
28. In the User groups list, select the EC2-Support check box.
29. Choose Next.
30. Choose Create user.
31. Choose Return to users list.
Unlike with user-1, you didn’t review the password by choosing Show. A pop-up will appear.
32. On the Continue without viewing or downloading console password pop-up box,
choose Continue.

Create user-3 without adding the user to a group

33. Choose Create user.
34. In the User name field, enter user-3.
35. Select the Provide user access to the AWS Management Console check box.
36. For User type, choose I want to create an IAM user.
37. Choose the scroll bar and scroll down. Then, for Console password, choose Custom
password.
38. Select the Show password check box.
39. In the Custom password field, enter Sim-Password3.
• Note: To record your entry, press Enter on your keyboard or choose any place
outside of the entry field.
40. Clear the User must create a new password at next sign-in check box.
41. Choose Next.
In Task 4, you will explore another way to add users to a group. Therefore, you will not
assign user-3 to a group at this point.
42. Choose Next.
43. Choose Create user.
44. Choose Return to users list.
45. On the Continue without viewing or downloading console password pop-up box,
choose Continue.

You have now created the three users required for the Business scenario.
• user-1 and user-2 each have a 1 in the Groups column, indicating that they belong to
a group.
• user-3 has a 0 in the Groups column, because you did not add the user to a group yet.

Page | 22
Task 4: Using the user group to add users
An alternative way to add users to groups is to go into the group and add users directly. In
this task, you add user-3 to the EC2-Admin group.

1. In the left navigation pane, choose User groups.

2. Choose the EC2-Admin group name.
3. Choose Add users.
4. From the list of users, select the user-3 check box.
5. Choose Add users.
6. In the left navigation pane, choose Users.

Page | 23
Task 5: Reviewing policies attached to a user
If you need to confirm the access that any user has, you can review the policies attached to
that user. In this task, you will review the permissions for user-2.

Steps
1. On the Users page, choose user-2 from the User name column.
The Permissions policies pane lists all of the policies that are attached to the user in the
Policy name section. Both policies that are directly attached to the user and those inherited
from user groups will appear here.
2. In the Policy name section, choose AmazonEC2ReadOnlyAccess.
A new tab opens, displaying the AmazonEC2ReadOnlyAccess information page.
3. On the Permissions defined in this policy pane, choose JSON.
4. Choose the scroll bar to scroll down.
From here, you can review the permissions that this AWS managed policy grants to the user.
5. Close the AmazonEC2ReadOnlyAccess browser tab.
6. In the navigation pane on the left, choose Users.

Task 6: Testing the access of user-1

In this task, you will log in to the AWS Management Console as user-1 and test the
permissions. User-1 is in the S3-Support group.
The S3-Support group has the AmazonS3ReadOnlyAccess policy attached to it. Therefore,
user-1 should be able to go to the S3 console page and view buckets and content in the
buckets. However, the user should not be able to upload or delete objects.

Get the console sign-in URL

1. In the left navigation pane, choose Dashboard.
Notice the Sign-in URL for IAM users in this account section at the top right of the page.
The sign-in URL looks similar to the following:
[Link]
This link can be used to sign in to the AWS account that you are currently using. (The
Page | 24
account number is blurred out for security reasons).
2. On the AWS Account pane, choose the copy icon for Sign-in URL for IAM users
in this account to copy the link.

Open an incognito window

3. Open a private or incognito window in your browser. To do this, follow these steps:
4. Simulate pasting the sign-in browser URL in the incognito window’s search bar. To
do this, follow these steps:
5. Open the context (right-click) menu for your browser tab.
6. Choose Duplicate.
7. Open the context (right-click) menu for your second browser tab.
8. Choose Duplicate.

Test user-1 permissions

9. Sign in with the following credentials:
o IAM user name: user-1
o Password: Sim-Password1
Note: To record each entry, press Enter on your keyboard or choose any place outside of the
entry field.
10. In the Recently visited section, choose S3.
11. Choose the sim-website bucket.
12. Choose Upload.
13. Choose Add files.
14. Select the [Link] file.
15. Choose Open.
16. Choose the scroll bar to scroll down. Then, choose Upload.
The failed upload message confirms that the user’s permissions are working as expected.
17. Close the browser tab.

Page | 25
Task 7: Testing the access of user-2
In this task, you will log in to the AWS Management Console as user-2 and test the
permissions. User-2 has been hired as an Amazon EC2 support person and is in the EC2-
Support group.
The EC2-Support group has the AmazonEC2ReadOnlyAccess policy attached to it.
Therefore, user-2 should be able to go to the EC2 dashboard and view instances. However,
the user should not be able to stop or start instances.

1. Sign in with the following credentials:

o IAM user name: user-2
o Password: Sim-Password2
Note: To record each entry, press Enter on your keyboard or choose any place outside of the
entry field.
2. In the Recently visited section, choose EC2.
3. In the left navigation pane, choose Instances.
You can see two EC2 instances. However, you cannot make any changes to Amazon EC2
resources because you have read-only permissions.
4. Select the Application server instance check box.
5. Choose the Instance state menu. Then, choose Stop instance.
6. To confirm you want to stop the instance, choose Stop.
An error message appears that says:
You are not authorized to perform this operation.
This demonstrates that the policy only allows you to view information without making
changes.
7. Close the Instances browser tab.

Task 8: Testing the access of user-3

In this task, you will log in to the AWS Management Console as user-3 and test the
permissions. User-3 has been hired as an Amazon EC2 admin and is therefore in the EC2-
Admin group.
The EC2-Admin group has the EC2-Admin-Policy attached to it. This is the custom policy
that you created in Task 1. Therefore, user-3 should be able to go to the EC2 dashboard and
Page | 26
view instances. Unlike user-2, however, user-3 should also be able to stop and start
instances.

Steps
1. Sign in with the following credentials:
o IAM user name: user-3
o Password: Sim-Password3
Note: To record each entry, press Enter on your keyboard or choose any place outside of the
entry field.
2. In the Recently visited section, choose EC2.
3. In the Resources pane, choose Instances (running).
EC2 instances are listed. As an Amazon EC2 Administrator, this user should have
permissions to stop EC2 instances.
4. Select the Application server instance check box.
5. Choose the Instance state menu, then choose Stop instance.
6. To confirm that you want to stop the instance, choose Stop.
This time, the action is successful because user-3 has permissions to stop EC2 instances. The
Instance state changes to Stopping and begins to shut down.

Modifying access to grant user-3 read-only access to Amazon S3

Next, you will test whether the EC2-Admin-Policy that user-3 inherits from the EC2-
Admin group provides any access to Amazon S3.
7. To return to the AWS Management Console home page, choose the AWS icon in the
top left corner. In the Recently visited section, choose S3.
8. In the left navigation pane, choose Buckets.
An error message appears that says:
You don’t have permissions to list buckets.
This demonstrates that the EC2-Admin-Policy does not grant any access for S3.
If you wanted to give your EC2 administrator access to view S3 buckets, you could add the
user to the S3-Support group. Next, you will update the permissions for user-3.
9. Return to your normal browser window, where you are logged into the IAM console.
o Hover near the bottom of the browser to bring up the task bar.
o Choose the Google Chrome icon.
10. Choose User groups.
11. In the list of user groups, choose S3-Support.
The group displays a list of users that are already in it.
12. Choose Add users.
Note: user-1 is not on the list, because this page only shows users not yet in the group.
13. In the Other users in this account pane, select the user-3 check box.
14. Choose Add users.
15. Return to the incognito window by closing the current IAM tab.
16. In the top left of your browser, choose Refresh.
The new access is available immediately. There is no requirement for user-3 to log out and
log back in. Now, user-3 has the same access to S3 that user-1 has — but unlike user-1, they
still retain EC2 administrative access.
Page | 27
Conclude the simulation
17. Choose the user-3 account dropdown list.
18. Choose Sign out.

Simulation overview and objectives

In this simulation, you use some of the Amazon Simple Storage Service
(Amazon S3) features that you just learned about to create a static website.
Static websites can contain HTML pages, images, style sheets, and all
files that are needed to render a website. Static websites do not use
server-side scripting or a database. However, they might contain client-
side scripts that run in a user's web browser.
You can host a static website on Amazon S3 by uploading the content and
making it readable by users. No servers are needed, and you can use
Amazon S3 to store and retrieve any amount of data anytime from
anywhere on the web.

Objectives
After completing this simulation, you will know how to do the following:
• Create a bucket in Amazon S3.
• Configure a bucket to host a static website.
• Upload content to a bucket.
• Turn on public access to bucket objects.
• Securely share a bucket object by using a presigned URL.
• Secure a bucket by using a bucket policy.
Page | 28
• Update the website.
• View object versions in the Amazon S3 console.

Task 1: Creating a bucket in Amazon S3

In this task, you create an S3 bucket that you will use for static website hosting.
1. In the AWS Management Console, choose the search bar and enter S3.
2. Then choose S3 from the search results.
3. Choose Create bucket.
An S3 bucket name is globally unique, and all AWS accounts share the namespace. After you
create a bucket, no other AWS accounts in any AWS Regions can use the name of that bucket
unless you delete the bucket.
4. For Bucket name, enter sim-website.
5. Choose the scroll bar to scroll down to Object Ownership.
6. For Object Ownership, choose ACLs enabled. Keep the default Bucket owner
preferred selected.
7. Choose the scroll bar to scroll down to Block Public Access settings for this bucket.
Public access to buckets is blocked by default. Because the files in your static website must
be accessible through the internet, you must permit public access.
8. For Block Public Access settings for this bucket, clear the checkbox for Block all
public access. Then, select the box that states I acknowledge that the current
settings might result in this bucket and the objects within becoming public.
9. Choose the scroll bar to scroll down to Bucket Versioning.
10. For Bucket Versioning, choose Enable.
11. For Tags, choose Add tag, and enter the following:
• Key: Department
• Value: Marketing
12. Choose the scroll bar to scroll down.
13. Choose Create bucket.

Page | 29
Task 2: Configuring a static website on Amazon S3
You will now configure the bucket for static website hosting.
17. In the list of your buckets, choose the name of the bucket that you just created, sim-
website.
18. Choose the Properties tab.
19. Choose the scroll bar to scroll to the Static website hosting panel.
20. Choose Edit to the Static website hosting panel.
21. Choose Enable.
22. For Hosting type, keep the default setting Host a static website.
23. Configure the following settings:
• Index document: Enter [Link]
• Error document: Enter [Link]
Note: To record your entry, press Enter on your keyboard or choose any place outside the
entry field.
Note: You must enter [Link] and [Link] even though they are already displayed.
The display that you see is only an example of what the field is expecting.
24. Choose the scroll bar to scroll down.
25. Choose Save changes.
26. Choose the scroll bar to scroll to the Static website hosting panel.
27. In the Static website hosting panel under Bucket website endpoint, choose the link.
A new tab opens where you receive a 403 Forbidden message because you have not yet
configured the bucket permissions. You can return to it later.
28. Choose the AWS Management Console tab on your browser.
You have configured your bucket to host a static website.

Task 3: Uploading content to your bucket

Page | 30
In this task, you upload the static files to your bucket.
22. Choose the scroll bar to scroll to the top of the page, and choose the Objects tab.
23. Choose Upload.
24. Choose Add files.
25. Choose the Website files folder, and choose Open to open the folder.
26. Use your mouse to choose each of the following files: [Link], [Link], and
[Link] (order does not matter). Then choose Open.
27. Choose the scroll bar to scroll down.
28. Choose Upload.
Your files are uploaded to the bucket.
29. Choose Close.

Task 4: Turning on public access to the objects

Objects that are stored in Amazon S3 are private by default. This setting helps keep your
organization's data secure.
In this task, you make the uploaded objects publicly accessible so users can view your
website.
First, confirm that the objects are currently private.
28. Return to the browser tab that showed the 403 Forbidden message.
29. Choose the Refresh button for the webpage.
You should still see a 403 Forbidden message. This response is expected. This message
indicates that your static website is being hosted by Amazon S3 but that the content is private.
You can make Amazon S3 objects public in two different ways:
• To make either a whole bucket public or a specific directory in a bucket public, use a
bucket policy.
• To make individual objects in a bucket public, use an access control list (ACL).

Page | 31
It is normally safer to make individual objects public because doing so avoids accidentally
making other objects public. However, if you know that the entire bucket contains no
sensitive information, you can use a bucket policy.
You now configure the individual objects to be publicly accessible.
30. Keep the website tab open, and return to the web browser tab with the Amazon S3
console.
31. Choose the Name checkbox to select all three objects.
32. In the Actions menu, choose Make public using ACL.
A list of the three objects is displayed.
33. Choose Make public.
Your static website is now publicly accessible.
34. Choose Close.
35. Return to the web browser tab that has the 403 Forbidden message.
36. Refresh the webpage.
You should now see the static website that Amazon S3 is hosting.
37. On your browser, choose the x on the My Static Website tab.

Task 5: Securely sharing an object by using a presigned URL

When you must temporarily and securely share an object with a person or group of people,
you can create a presigned URL. When you create the URL, you must configure how long the
URL will be valid. Then, you can share this URL with the users who should have access to
the object.
If the presigned URL is valid, anyone who has it can get to the object. Avoid keeping the
URL active longer than necessary, and only share the URL with people you trust.
38. Choose Upload.
39. Choose Add files.
40. Choose the file new-report file and choose Open.
Page | 32
 41. Choose the scroll bar to scroll down.
42. Choose Upload.
You have uploaded your file to the bucket.
43. Choose Close.
Like when you first uploaded the website files, the [Link] file is private by default.
This time, instead of making the object public, you create a presigned URL to access the file.
44. In the Objects tab, choose [Link].
45. From the Actions menu, select Share with a presigned URL.
46. In the pop-up window, keep the default Minutes selected for the Time interval until
the presigned URL expires.
47. For Number of minutes, enter 2.
Note: To record your entry, press Enter on your keyboard or choose any place outside the
entry field.
48. Choose Create presigned URL.
49. From the banner at the top of the page, choose Copy presigned URL.
50. Open a new browser tab.
51. Paste the URL that you copied into the address bar. Use these specific steps to paste
and launch the URL:
• Choose the browser URL search bar.
• Press Ctrl + v on your keyboard.
• Note: Mac users should also press Ctrl + v on their keyboard. This command is not
the pasting command for Mac keyboards, but this simulation requires you to use your
keyboard as a Windows keyboard.
• Press Enter to load the page.
A report is displayed in the web browser.
If you wait 2 minutes and use the link again, you will find that the URL has expired and no
longer works.
52. Choose the Refresh icon on the browser.
Now that the presigned URL is expired, you get an Access denied page.
53. Choose x to close the Access denied tab.

Page | 33
Task 6: Using a bucket policy to secure your bucket
You want to protect your website files and make sure that no one can delete them. To do so,
you apply a bucket policy that denies delete privileges on your website files.
50. Choose the Permissions tab.
51. Choose the scroll bar to scroll down to the Bucket policy panel.
52. In the Bucket policy panel, choose Edit.
53. Copy the following policy text and paste it in the Policy text editor field. To do so,
follow these specific steps:
• Open the context (right-click) menu for the Policy text editor field.
• Choose Paste.
{
"Version": "2012-10-17",
"Id": "MyBucketPolicy",
"Statement": [
{
"Sid": "BucketPutDelete",
"Effect": "Deny",
"Principal": "*",
"Action": "s3:DeleteObject",
"Resource": [
"arn:aws:s[Link]sim-website/[Link]",
"arn:aws:s[Link]sim-website/[Link]",
"arn:aws:s[Link]sim-website/[Link]"
]
}
]
}
This policy prevents everyone from deleting the three files that make your website work.
Note: If you use this code in your own AWS account, you must use the name of your bucket
in place of this simulation’s sim-website bucket.
54. Choose the scroll bar to scroll down.
55. Choose Save changes.
56. Return to the Objects tab.
57. Select [Link].
58. Choose Delete.
59. In the Delete objects panel, enter delete to confirm that you want to remove this file.
Note: To record your entry, press Enter on your keyboard or choose any place outside the
entry field.
60. Choose Delete objects.
Notice that the [Link] file is listed in the Failed to delete pane.
This entry confirms that your policy is working and preventing the website's files from being
deleted.
61. Choose Close to return to the Objects tab.
Your bucket policy is now protecting your website files from being deleted.

Page | 34
Task 7: Updating the website
Although you have configured a policy to prevent deletion of website files, you can still
update the website. You can do so by editing the HTML file and uploading it to the S3 bucket
again.
Amazon S3 is an object storage service, so you must upload the whole file. This action
replaces the existing object in your bucket. You cannot edit the contents of an object; instead,
you must replace the whole object.
Next, you edit the existing [Link] file.
62. On your computer, load the [Link] file into a text editor (in this simulation, you
use Notepad). Follow these specific steps:
63. Open the context (right-click) menu for the [Link] file.
64. Choose Open with.
65. Choose Notepad.
66. Find the text Served from Amazon S3, and replace it with Created by Jane. Follow
these specific steps:
67. Choose the text Served from Amazon S3.
68. Enter Created by Jane.
Note: To record your entry, press Enter on your keyboard or choose any place outside the
entry field.
64. Save the file. Follow these specific steps:
65. Choose File from the Notepad menu.
66. Choose Save.
67. Return to the Amazon S3 console by selecting the Amazon S3 console window in the
background.
Now you review the current website version.
66. Choose the [Link] file name (choose the link, not the checkbox).
67. Choose the Object URL link.

Page | 35
Served from Amazon S3 should still be visible on your website page because you have not
yet uploaded the new version and made it public.
Next, you will upload the [Link] file that you edited and make it public.
68. Choose the Back arrow on your browser to return to the Amazon S3 console.
69. Choose the sim-website link from the navigation at the top of the page.
70. Upload the [Link] file that you just edited. Follow these specific steps:
71. Choose Upload.
72. Choose Add files.
73. Choose the Website files folder, and choose Open.
74. Choose the index file and choose Open.
75. Choose the scroll bar to scroll down.
76. Choose Upload.
77. Choose Close.
78. Select the [Link] checkbox, and in the Actions menu, choose the Make public
using ACL option again.
79. Choose Make public, and choose Close.
Now you verify that your website is updated with your edits.
73. Choose the [Link] file name (choose the link, not the checkbox).
74. Choose the Object URL link.
Created by Jane should now be on the page in place of Served from Amazon S3.
Your static website is now accessible on the internet. Because it is hosted on Amazon S3, the
website has high availability and can serve high volumes of traffic without using any servers.
75. Choose the Back arrow on your browser to return to the Amazon S3 console.
76. Choose the sim-website link from the navigation at the top of the page.

Task 8: Exploring file versions

Bucket versioning is turned off by default. When versioning is turned off, changes to objects
can't be undone. For example, if you upload a new version of a file, the old file is replaced
with the new one. The original file is lost. If you delete a file, it is permanently deleted, and
you can't get it back.
Page | 36
However, when versioning is turned on, changed and deleted versions of files are saved.
Previous versions of objects are not presented by default, but you can access them by using
the console or programmatically. Because you are keeping earlier versions of objects, you can
recover them if you need to.
It is important to remember that as soon as you turn on versioning, you cannot turn it off.
However, you can suspend versioning. For more information about bucket versioning, see
“Using versioning in S3 buckets” in the Amazon Simple Storage Service User Guide at:
[Link]
Recall that when you created your bucket, you turned on versioning. In this task, you view
the object versions available in your bucket.
77. Choose Show versions to see which files have multiple versions.
78. Choose the scroll bar to scroll down.
79. Review the list of objects in the bucket.
• Notice that each file has a Version ID. Amazon S3 automatically generates these IDs
when versioning is turned on.
• You should also find two versions of the [Link] file because you uploaded a new
version of the file. The current version is the file that you uploaded when you updated
your website.

Submitted By:
Manmohan Sethi
2201020890
Group: 3
CSE, 7th Sem

Page | 37