Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Try it now and let us know what you think. Switch to the new look >>
You can return to the original look by selecting English in the language selector above.
Identity and Access Management in Amazon S3
By default, all Amazon S3 resources—buckets, objects, and related subresources (for
example,
lifecycle configuration and website configuration)—are
private: only the resource owner, an AWS account that created it, can access the
resource. The resource owner can optionally grant access permissions to others by
writing an
access policy.
Amazon S3 offers access policy options broadly categorized as resource-based policies and user policies. Access policies you attach to your resources (buckets and objects) are referred to as resource-based policies. For example, bucket policies and access control lists (ACLs) are resource-based policies. You can also attach access policies to users in your account. These are called user policies. You may choose to use resource-based policies, user policies, or some combination of these to manage permissions to your Amazon S3 resources. The introductory topics provide general guidelines for managing permissions.
We recommend you first review the access control overview topics. For more information, see Introduction to Managing Access Permissions to Your Amazon S3 Resources. Then for more information about specific access policy options, see the following topics:
