Topic lessonTopic: S3: versions, retention, replication and cost
S3 Replication explained: CRR, SRR and what gets copied
S3 Replication asynchronously copies eligible objects to another bucket. CRR crosses Regions; SRR stays within one Region. Saving a configuration is different from confirming that the required data has been replicated.
Distinguish new and existing targets, versioning, permissions, encryption, deletes and Lifecycle; explain how to verify replication results.
Know Versioning, ACLs/policies and Lifecycle. The synthetic example is one-way replication from general purpose bucket A to B, both versioning-enabled. Its report is written after configuration and matches the rule. No AWS connection is made.
Match the source, selection rule and destination
- Source bucket A → Replication ruleSelect eligible versions written after configuration, not every earlier object.
- Replication rule → Destination BCopy when permissions and other conditions are met. Reverse replication and application failover are separate.
- Source bucket A
- Versioning enabled; a new eligible report version is stored.
- Replication rule
- Selects objects, destination and the role used by S3.
- Destination B
- Versioning enabled; copying is asynchronous. Check completion and read access.
| Name | Distinction |
|---|---|
| CRR | Live replication between buckets in different Regions |
| SRR | Live replication between buckets in the same Region |
| Batch Replication | An on-demand job for selected existing objects and other eligible targets |
Choose an option to see the result and explanation.
Separate the configurator’s permissions from the role S3 uses
The identity configuring replication differs from the role assumed by S3 to perform it. Review trust, source-version read permissions and destination replication permissions. Cross-account destinations also need permissions granted from their side.
| Item | What to review |
|---|---|
| Versioning | Enabled on both buckets; suspension at the destination causes failures |
| Selection | Match prefix/tags and distinguish pre-existing objects |
| Ownership | Review source read access, destination ownership and associated permissions |
| Protection | A source using Object Lock imposes destination requirements; review retention |
For cross-account copies, decide whether the destination owns the replica or source ownership is retained. Object Ownership settings such as Bucket owner enforced and owner override affect that choice. Arrival alone does not establish that the destination application can read it.
For KMS-encrypted versions, check explicit selection and key access
AWS Key Management Service (KMS) manages encryption keys. SSE-KMS uses KMS for server-side encryption; DSSE-KMS adds dual layers. Replicating these objects requires explicit opt-in. Review source decryption, destination encryption, key policies and Regions. S3 read permission alone does not establish KMS access.
Choose an option to see the result and explanation.
Different delete operations affect the destination differently
| Source change | Destination behavior |
|---|---|
| DELETE without version ID | Delete markers are not replicated by default; supported rules can explicitly enable this |
| Permanent deletion of a specific version | That deletion is not replicated to the destination |
| Delete marker created by Lifecycle | Not replicated, even with delete marker replication enabled |
| Change to bucket Lifecycle configuration | The configuration itself is not copied to the destination |
Delete marker replication does not support tag-based rules. Older V1 configurations behave differently, so inspect existing configurations before applying this table. A current replicated marker can hide an object from ordinary reads at the destination without removing its retained data versions.
Choose an option to see the result and explanation.
Match PENDING, COMPLETED and FAILED to the required version
| Status | Interpretation |
|---|---|
| PENDING | Not complete; a delay is not automatically a terminal failure |
| COMPLETED | The version completed replication; with several destinations review completion for all |
| FAILED | Investigate permissions/keys; fixing configuration alone does not resend every failed version |
| REPLICA | Identifies a replica; does not establish application failover |
For FAILED versions, fix the cause and consider reprocessing such as Batch Replication. PENDING/FAILED also affects source Lifecycle actions. Destination Lifecycle uses the original object creation time, not the replica’s arrival time, so review its retention independently.
- Define required data and recovery needs; separate Regions, accounts and existing objects.
- Review versioning, selection, S3 role, ownership and encryption on both sides.
- Verify version status and destinations; record causes and reprocessing targets.
- Design destination retention, deletion permissions, application reads/failover and costs separately.
Check, then explain in your own words
- Separate CRR/SRR and live/Batch.
- Review selection, versioning, permissions and encryption.
- Distinguish delete types and destination retention.
- Verify per-version completion and reprocessing targets.
Check your understanding: Does enabling replication automatically cover all existing data, deletes and recovery?
No. Review eligibility, delete behavior, permissions, retention and completion separately.
Replication is asynchronous copying of selected data. Reading and recovering the required version depend on destination design and verification too.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
Scope and conditionsCRR/SRR; live versus Batch; asynchronous copy; ownership and recovery are separate
Used in this lessonMatch the source, selection rule and destination Separate the configurator’s permissions from the role S3 uses
- Replication requirementsChecked:
Scope and conditionsBoth buckets versioning-enabled; ownership/Object Lock boundary; destination Lifecycle original age; Region transfer differences
Used in this lessonMatch the source, selection rule and destination Separate the configurator’s permissions from the role S3 uses Match PENDING, COMPLETED and FAILED to the required version
- Permissions for live replicationChecked:
Scope and conditionsConfigurator versus S3 role; trust and source/destination permissions; cross-account destination
Used in this lessonMatch the source, selection rule and destination Separate the configurator’s permissions from the role S3 uses
Scope and conditionsDefault new-bucket BOE; three modes; accepted upload ACLs; ownership is not public access
Used in this lessonSeparate the configurator’s permissions from the role S3 uses
- Replicating encrypted objectsChecked:
Scope and conditionsExplicit KMS opt-in; source/destination key permissions; valid destination-Region key; save success is not copy completion; Bucket Key boundary
Used in this lessonFor KMS-encrypted versions, check explicit selection and key access
- What S3 replicatesChecked:
Scope and conditionsVersion deletes/markers and Lifecycle configurations; current Filter-based versus legacy V1; encrypted details resolved using dedicated KMS documentation
Used in this lessonDifferent delete operations affect the destination differently
- Replicating delete markersChecked:
Scope and conditionsDefault and explicit current-format marker behavior; no tag-filter support; Lifecycle markers not copied
Used in this lessonDifferent delete operations affect the destination differently
Scope and conditionsPer-version source statuses and REPLICA; failures need reprocessing; multi-destination and Lifecycle interaction
Used in this lessonMatch PENDING, COMPLETED and FAILED to the required version