Skip to content

Commit 6e107d0

Browse files
committed
add doc on additional replication
1 parent c9a0a0e commit 6e107d0

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

data-exports/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ For customers with additional requirements, an enhanced architecture is availabl
4848
8. Some customers might need to store data exports to secondary destinations for archiving or reporting at a higher organizational level or to staging environment. You can specify a secondary bucket to receive the data in these cases.
4949

5050
### Using Secondary Replication Bucket
51-
In situations where customers need to replicate data exports to multiple destinations. One common scenario involves a Business Unit requiring exports for one or more AWS Organizations data while simultaneously allowing Headquarters to access these same exports data for a consolidated view across all business units.
51+
There can be various situations where customers need to replicate data exports to multiple destinations. One common scenario involves a Business Unit requiring exports for one or more AWS Organizations data while simultaneously allowing Headquarters to access these same exports data for a consolidated view across all business units.
5252

5353
To accomplish this, both the Headquarters and Business Unit can implement separate data export destination stacks. Business Unit administrators, working from their management account, can specify a target bucket located within the Headquarters stack, enabling seamless data replication to both locations.
5454

0 commit comments

Comments
 (0)