...
S3 has two primary entities called buckets and objects.
Buckets are the access points and objects are stored inside them.
Bucket names have to be globally unique irrespective of which region they are created in.
As buckets can be accessed using URLs, it is recommended that bucket names follow DNS naming conventions: all letters should be in lowercase and don’t contain special characters.
Objects are directories or files.
Basically, it works like you upload images and you want to differentiate it from other files, you can create a file for it and store it so that the logical address of the file would have the prefix ‘pictures.’
For example, pictures/hello.jpg that would differentiate it from images/hello.jpg.
'Users' are replaced with Access Keys and 'passwords' are replaced with Secret Keys.
Access keys consist of two parts: an access key ID (for example,
AKIAIOSFODNN7EXAMPLE
) and a secret access key (for example,wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
).Like a user name and password, you must use both the access key ID and secret access key together to authenticate your access to your buckets.
Manage your access keys as securely as you do your user name and password.
Access However, access keys are associated with a project, lab, or department and can not be associated with a specific UWYO user.
Permissions are functionally limited and are only supported for basic usage.
For example, granular access to a single folder or directory that is possible in a traditional storage system is not well supported in S3.
Typically multiple users are able to use the same single access key to buckets with nothing that distinguishes between them.
...