COLLECTED BY

Organization: Archive Team

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.

History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.

The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.

This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.

Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.

The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.

Collection: Archive Team: URLs

TIMESTAMPS

The Wayback Machine - https://web.archive.org/web/20250222021523/https://docs.aws.amazon.com/AmazonS3/latest/userguide/endpoint-directory-buckets-AZ.html

Regional and Zonal endpoints for directory buckets in an Availability Zone

To access your objects and directory buckets stored in S3 Express One Zone, you use gateway VPC endpoints. Directory buckets use Regional and Zonal API endpoints. Depending on the Amazon S3 API operation that you use, either a Regional or Zonal endpoint is required. There is no additional charge for using gateway endpoints.

Bucket-level (or control plane) API operations are available through Regional endpoints and are referred to as Regional endpoint API operations. Examples of Regional endpoint API operations are CreateBucket and DeleteBucket.

When you create directory buckets that are stored in S3 Express One Zone, you choose the Availability Zone where your bucket will be located. You can use Zonal endpoint API operations to upload and manage the objects in your directory bucket.

Object-level (or data plane) API operations are available through Zonal endpoints and are referred to as Zonal endpoint API operations. Examples of Zonal endpoint API operations are CreateSession and PutObject.

Region name	Region	Availability Zone IDs	Regional endpoint	Zonal endpoint
US East (N. Virginia)	`us-east-1`	`use1-az4` `use1-az5` `use1-az6`	`s3express-control.us-east-1.amazonaws.com`	`s3express-use1-az4.us-east-1.amazonaws.com` `s3express-use1-az5.us-east-1.amazonaws.com` `s3express-use1-az6.us-east-1.amazonaws.com`
US East (Ohio)	`us-east-2`	`use2-az1` `use2-az2`	`s3express-control.us-east-2.amazonaws.com`	`s3express-use2-az1.us-east-2.amazonaws.com` `s3express-use2-az2.us-east-2.amazonaws.com`
US West (Oregon)	`us-west-2`	`usw2-az1` `usw2-az3` `usw2-az4`	`s3express-control.us-west-2.amazonaws.com`	`s3express-usw2-az1.us-west-2.amazonaws.com` `s3express-usw2-az3.us-west-2.amazonaws.com` `s3express-usw2-az4.us-west-2.amazonaws.com`
Asia Pacific (Mumbai)	`ap-south-1`	`aps1-az1` `aps1-az3`	`s3express-control.ap-south-1.amazonaws.com`	`s3express-aps1-az1.ap-south-1.amazonaws.com` `s3express-aps1-az3.ap-south-1.amazonaws.com`
Asia Pacific (Tokyo)	`ap-northeast-1`	`apne1-az1` `apne1-az4`	`s3express-control.ap-northeast-1.amazonaws.com`	`s3express-apne1-az1.ap-northeast-1.amazonaws.com` `s3express-apne1-az4.ap-northeast-1.amazonaws.com`
Europe (Ireland)	`eu-west-1`	`euw1-az1` `euw1-az3`	`s3express-control.eu-west-1.amazonaws.com`	`s3express-euw1-az1.eu-west-1.amazonaws.com` `s3express-euw1-az3.eu-west-1.amazonaws.com`
Europe (Stockholm)	`eu-north-1`	`eun1-az1` `eun1-az2` `eun1-az3`	`s3express-control.eu-north-1.amazonaws.com`	`s3express-eun1-az1.eu-north-1.amazonaws.com` `s3express-eun1-az2.eu-north-1.amazonaws.com` `s3express-eun1-az3.eu-north-1.amazonaws.com`

Warning Javascript is disabled or is unavailable in your browser.

To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions.

Document Conventions

Creating directory buckets in an Availability Zone

Optimizing S3 Express One Zone performance

Jan	FEB	Mar
	22
2024	2025	2026