Set a depot location in Amazon S3 storage

Store depot data in Amazon S3–backed storage. Consider the following options:

Amazon S3, the Simple Storage Service of Amazon Web Services.
An S3-compatible API, such as that of MinIO.
A cloud provider's storage offering, such as:
- DigitalOcean's Space Object Storage
- Tencent Cloud Object Storage
- Google Cloud Storage
- 3Proxy for Microsoft Azure Blob Storage.

This feature is supported for depots of all types except remote depots. The central server The one server that is innermost in a multi-server deployment. In the server specification form field for Services, the central server might be specified as “standard” or “commit-server”. If edge servers are part of the multi-server deployment, the central server must be a commit server. See also 'upstream server'., each replica A P4 Server that automatically maintains a full or partial copy of the central server's metadata and that might contain related file content. The replica copies by using 'p4 pull' or 'p4 journalcopy'. A replica can be used as a backup server for disaster recovery., standby, and edge server A server that is part of a commit-edge environment that can independently support work in progress for locally-bound clients, thereby reducing the load on the commit server. must be able to resolve to the same S3 bucket that is defined in the depot spec.

Depending on factors such as network latency and bandwidth, you might not find S3 buckets to perform well enough to be practical.

You can create an S3 data source as a place to store files for a P4 Server depot. When using S3 for depot storage, specify the S3 connection details in the depot Map field.

Create a depot specification that sets the Address field to map to the S3 datasource. The location of the S3 bucket and the credentials are stored in the depot spec on a per-depot basis using the Address field.