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.

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: Disallow prod ↔ staging communication #392

Merged
merged 6 commits into from
Jan 12, 2020
Merged
Changes from all commits
Commits
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
17 changes: 17 additions & 0 deletions content/faq/disallow-prod-staging-communication.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
---
title: "Should prod ↔ staging communication be disallowed?"
description: "Yes, we generally advocate disallowing all forms of connectivity between staging and production environments."
tags:
- production
- staging
- PCI
- SOC
---

## Question

Should we be strictly disallowing prod ↔ staging communication?

## Answer

Yes, generally advocate disallowing all forms of connectivity between staging and production environments. We achieve this by operating multiple AWS accounts and not using VPC peering between them. This is because we do not want to blur the lines between production and staging. It should be extremely difficult/cumbersome to move data out of production, plus this also makes compliance with PCI/SOC easier. Unfortunately we've seen it happen too many times where companies prematurely launch services that have dependencies on staging resources, which is a huge mistake. To avoid this from accidentally happening, make it impossible to connect between environments.