The names of these folders (such as home/ or home/common/) are called prefixes.īy the way, the slash (/) in a prefix like home/ isn’t a reserved character-you could name an object (using the Amazon S3 API) with prefixes like home:common:shared.txt or home-common-shared.txt. To give you an example, for an object that’s named home/common/shared.txt, the console will show the shared.txt file in the common folder that is in the home folder. ![]() For simplicity, you can think of an object’s name as the full path of a file in a traditional file system. Amazon S3 doesn’t have a hierarchy of sub-buckets or folders however, tools like the AWS Management Console can emulate a folder hierarchy to present folders in a bucket by using the names of objects (also known as keys). Here we'll be modifying this pattern specifically for SAML federated users with a specially crafted IAM policy.Ī brief lesson about Amazon S3 objects: Amazon S3 stores data in a flat structure you create a bucket, and the bucket stores objects. In this exercise, we will go over how to create a S3 bucket where every federated user has access to only his or her own "home directory." The inspiration for this advanced use case comes from a non-federation oriented example in the AWS documentation, Allow Users to Access a Personal "Home Directory" in Amazon S3. ![]() ![]() Choose Your Own SAML Adventure: A Self-Directed Journey to AWS Identity Federation Mastery Implement a SAML version of "Amazon S3 home directories"
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |