You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in the *Amazon S3 User Guide*. For information about S3 replication on Outposts
1448
+
configuration, see [Replicating objects for Amazon Web Services Outposts](https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3OutpostsReplication.html)
1449
+
in the *Amazon S3 User Guide*.
1450
+
1451
+
It can take a while to propagate `PUT` or `DELETE` requests for a replication
1452
+
configuration to all S3 on Outposts systems. Therefore, the replication
1453
+
configuration that's returned by a `GET` request soon after a `PUT` or `DELETE`
1454
+
request might return a more recent result than what's on the Outpost. If an
1455
+
Outpost is offline, the delay in updating the replication configuration on that
1456
+
Outpost can be significant.
1457
+
1458
+
This action requires permissions for the
1459
+
`s3-outposts:GetReplicationConfiguration` action. The Outposts bucket owner has
1460
+
this permission by default and can grant it to others. For more information
1461
+
about permissions, see [Setting up IAM with S3 on Outposts](https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3OutpostsIAM.html)
1462
+
and [Managing access to S3 on Outposts bucket](https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3OutpostsBucketPolicy.html)
1463
+
in the *Amazon S3 User Guide*.
1464
+
1465
+
All Amazon S3 on Outposts REST API requests for this action require an
1466
+
additional parameter of `x-amz-outpost-id` to be passed with the request. In
1467
+
addition, you must use an S3 on Outposts endpoint hostname prefix instead of
1468
+
`s3-control`. For an example of the request syntax for Amazon S3 on Outposts
1469
+
that uses the S3 on Outposts endpoint hostname prefix and the `x-amz-outpost-id`
It can take a while to propagate `PUT` or `DELETE` requests for a replication
2454
+
configuration to all S3 on Outposts systems. Therefore, the replication
2455
+
configuration that's returned by a `GET` request soon after a `PUT` or `DELETE`
2456
+
request might return a more recent result than what's on the Outpost. If an
2457
+
Outpost is offline, the delay in updating the replication configuration on that
2458
+
Outpost can be significant.
2459
+
2460
+
Specify the replication configuration in the request body. In the replication
2461
+
configuration, you provide the following information:
2462
+
2463
+
* The name of the destination bucket or buckets where you want S3 on
2464
+
Outposts to replicate objects
2465
+
2466
+
* The Identity and Access Management (IAM) role that S3 on Outposts
2467
+
can assume to replicate objects on your behalf
2468
+
2469
+
* Other relevant information, such as replication rules
2470
+
2471
+
A replication configuration must include at least one rule and can contain a
2472
+
maximum of 100. Each rule identifies a subset of objects to replicate by
2473
+
filtering the objects in the source Outposts bucket. To choose additional
2474
+
subsets of objects to replicate, add a rule for each subset.
2475
+
2476
+
To specify a subset of the objects in the source Outposts bucket to apply a
2477
+
replication rule to, add the `Filter` element as a child of the `Rule` element.
2478
+
You can filter objects based on an object key prefix, one or more object tags,
2479
+
or both. When you add the `Filter` element in the configuration, you must also
2480
+
add the following elements: `DeleteMarkerReplication`, `Status`, and `Priority`.
2481
+
2482
+
Using `PutBucketReplication` on Outposts requires that both the source and
2483
+
destination buckets must have versioning enabled. For information about enabling
2484
+
versioning on a bucket, see [Managing S3 Versioning for your S3 on Outposts bucket](https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3OutpostsManagingVersioning.html).
2485
+
2486
+
For information about S3 on Outposts replication failure reasons, see
Outposts buckets are encrypted at all times. All the objects in the source
2493
+
Outposts bucket are encrypted and can be replicated. Also, all the replicas in
2494
+
the destination Outposts bucket are encrypted with the same encryption key as
2495
+
the objects in the source Outposts bucket.
2496
+
2497
+
## Permissions
2498
+
2499
+
To create a `PutBucketReplication` request, you must have
2500
+
`s3-outposts:PutReplicationConfiguration` permissions for the bucket. The
2501
+
Outposts bucket owner has this permission by default and can grant it to others.
2502
+
For more information about permissions, see [Setting up IAM with S3 on Outposts](https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3OutpostsIAM.html)
2503
+
and [Managing access to S3 on Outposts buckets](https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3OutpostsBucketPolicy.html).
2504
+
2505
+
To perform this operation, the user or role must also have the
2506
+
[iam:PassRole](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_passrole.html) permission.
2507
+
2508
+
All Amazon S3 on Outposts REST API requests for this action require an
2509
+
additional parameter of `x-amz-outpost-id` to be passed with the request. In
2510
+
addition, you must use an S3 on Outposts endpoint hostname prefix instead of
2511
+
`s3-control`. For an example of the request syntax for Amazon S3 on Outposts
2512
+
that uses the S3 on Outposts endpoint hostname prefix and the `x-amz-outpost-id`
0 commit comments