Skip to content

Commit c0c0c68

Browse files
committed
add doc on additional replication
1 parent d40f80d commit c0c0c68

File tree

2 files changed

+10
-1
lines changed

2 files changed

+10
-1
lines changed
443 KB
Loading

data-exports/README.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,16 @@ For customers with additional requirements, an enhanced architecture is availabl
4545

4646
7. Athena's reading process can be affected by writing operations. When replication arrives, it might fail to update datasets, especially with high volumes of data. In such cases, consider scheduling temporary disabling and re-enabling of the Amazon S3 bucket policy that allows replication. Since exports typically arrive three times daily, this temporary deactivation has minimal side effects.
4747

48-
8. Some customers might need to store data exports to secondary destinations for archiving or reporting at a higher organizational level. You can specify a secondary bucket to receive the data in these cases.
48+
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.
49+
50+
### 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.
52+
53+
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.
54+
55+
Other scenario can be a replicating data to a staging environment.
56+
57+
![Secondary Replication Bucket](.images/architecture-data-export-replication-to-secondary.png)
4958

5059
## Legacy Cost and Usage Report
5160
Legacy AWS Cost and Usage Reports (Legacy CUR) can still be used for Cloud Intelligence Dashboards and other use cases.

0 commit comments

Comments
 (0)