Skip to content

Commit 3af5332

Browse files
committed
add data exports readme
1 parent a93eb55 commit 3af5332

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

data-exports/README.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,10 @@ This readme contains description of solutions for AWS Data Exports and Legacy CU
1313

1414
## Data Exports
1515

16-
For deployment instructions, please refer to the documentation at: https://catalog.workshops.aws/awscid/data-exports
16+
For deployment instructions, please refer to the documentation at: https://catalog.workshops.aws/awscid/data-exports.
17+
18+
Check code here: [data-exports-aggregation.yaml](deploy/data-exports-aggregation.yaml)
19+
1720

1821
### Basic Architecture of Data Exports
1922
![Basic Architecture of Data Exports](/.images/architecture-data-exports.png "Basic Architecture of Data Exports")
@@ -49,6 +52,11 @@ Legacy AWS Cost and Usage Reports (Legacy CUR) can still be used for Cloud Intel
4952

5053
The CID project provides a CloudFormation template for Legacy CUR. Unlike the Data Exports CloudFormation template, it does not provide AWS Glue tables. You can use this template to replicate CUR and aggregate CUR from multiple source accounts (Management or Linked).
5154

55+
![Basic Architecture of CUR](/.images/architecture-legacy-cur.png "Basic Architecture of CUR")
56+
57+
58+
Check code here: [cur-aggregation.yaml](deploy/cur-aggregation.yaml)
59+
5260
## FAQ
5361

5462
### Why replicate data instead of providing cross-account access?

0 commit comments

Comments
 (0)