[DO NOT MERGE] BYOC on AWS draft documentation#37021
Open
val-materialize wants to merge 2 commits into
Open
Conversation
Added a draft guide for using Bring Your Own Cloud (BYOC) on AWS, detailing setup, provisioning, security, and observability.
Added a warning note indicating that this is an early draft for feedback on the BYOC on AWS MVP design.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
[RFC][DRAFT] docs: BYOC on AWS setup guide (early, for feedback)
Early draft of a customer-facing setup guide for Bring Your Own Cloud (BYOC) on AWS, shared for feedback on the proposed onboarding experience.
Status: Very early. This documents an in-progress MVP design, not a shipped feature. Flows, names, and details will change.
What this is: A first pass at the BYOC on AWS setup flow (cross-account IAM via CloudFormation, provisioning, PrivateLink, security model, observability). Intended to give a concrete artifact to react to.
What I'm looking for: First impressions on the setup flow and whether the model is clear and credible, especially from a customer's security and infra perspective. Not looking for copy edits yet.