-
-
Notifications
You must be signed in to change notification settings - Fork 27
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add FAQ: Separate data environment (#439)
- Loading branch information
Showing
1 changed file
with
18 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
--- | ||
title: "Should we operate a separate data environment with special access to production resources?" | ||
description: "Yes, we recommend provisioning an additional AWS account for data processing and analytics." | ||
tags: | ||
- production | ||
- data environment | ||
- AWS | ||
- CDE | ||
--- | ||
|
||
## Question | ||
|
||
Should we consider operating a separate data environment that is granted special access to production resources? | ||
|
||
|
||
## Answer | ||
|
||
Yes, we recommend provisioning an additional AWS account for data processing and analytics. Ideally, some kind of ETL process scrubs the data before shipping it to a non-cardholder data environment (CDE). |