Additional considerations

Amazon S3 also supports bucket configurations for the following:

• Versioning – For more information, see Using versioning in S3 buckets.

• Website hosting – For more information, see Hosting a static website using Amazon S3.

• Bucket access through a bucket policy or access control list (ACL) — For more information, see Bucket policies and user policies and see Access control list (ACL) overview.

• Log storage – For more information, Logging requests using server access logging.

• Lifecycle management for objects in a bucket – For more information, see Managing your storage lifecycle.

This topic explains how bucket replication configuration affects the behavior of these bucket configurations.

Lifecycle configuration and object replicas

The time it takes for Amazon S3 to replicate an object depends on the size of the object. For large objects, it can take several hours. Although it might take a while before a replica is available in the destination, it takes the same amount of time to create the replica as it took to create the corresponding object in the source bucket. If a lifecycle policy is enabled on a destination bucket, the lifecycle rules honor the original creation time of the object, not when the replica became available in the destination bucket.

Replication configuration requires the bucket to be versioning-enabled. When you enable versioning on a bucket, keep the following in mind:

• If you have an object Expiration lifecycle policy, after you enable versioning, add a NonCurrentVersionExpiration policy to maintain the same permanent delete behavior as before you enabled versioning.

• If you have a Transition lifecycle policy, after you enable versioning, consider adding a NonCurrentVersionTransition policy.

Versioning configuration and replication configuration

Both the source and destination buckets must be versioning-enabled when you configure replication on a bucket. After you enable versioning on both the source and destination buckets and configure replication on the source bucket, you will encounter the following issues:

• If you attempt to disable versioning on the source bucket, Amazon S3 returns an error. You must remove the replication configuration before you can disable versioning on the source bucket.

• If you disable versioning on the destination bucket, replication fails. The source object has the replication status FAILED.

Logging configuration and replication configuration

If Amazon S3 delivers logs to a bucket that has replication enabled, it replicates the log objects.

If server access logs (Logging requests using server access logging) or AWS CloudTrail logs ( Logging Amazon S3 API calls using AWS CloudTrail) are enabled on your source or destination bucket, Amazon S3 includes replication-related requests in the logs. For example, Amazon S3 logs each object that it replicates.

CRR and the destination Region

Amazon S3 Cross-Region Replication (CRR) is used to copy objects across S3 buckets in different AWS Regions. You might choose the Region for your destination bucket based on either your business needs or cost considerations. For example, inter-Region data transfer charges vary depending on the Regions that you choose.

Suppose that you chose US East (N. Virginia) (us-east-1) as the Region for your source bucket. If you choose US West (Oregon) (us-west-2) as the Region for your destination buckets, you pay more than if you choose the US East (Ohio) (us-east-2) Region. For pricing information, see "Data Transfer Pricing" in Amazon S3 pricing.

There are no data transfer charges associated with Same-Region Replication (SRR).

Pausing replication

To temporarily pause replication, disable the relevant rule in the replication configuration.

If replication is enabled and you remove the IAM role that grants Amazon S3 the required permissions, replication fails. Amazon S3 reports the replication status for affected objects as FAILED.