Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FAQ: Separate data environment #439

Merged
merged 1 commit into from
Jan 13, 2020
Merged

FAQ: Separate data environment #439

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions content/faq/separate-data-environment.md
View file
Open in desktop
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).