-
Notifications
You must be signed in to change notification settings - Fork 2
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
BYOVPC for AWS #12
BYOVPC for AWS #12
Conversation
✅ Deploy Preview for rp-cloud ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
modules/get-started/pages/cluster-types/byoc/create-byoc-cluster-aws.adoc
Outdated
Show resolved
Hide resolved
240cd4a
to
8e91306
Compare
Status 8/24/24: This should stay in private beta until we get feedback from another customer, per Praseed. |
modules/get-started/pages/cluster-types/byoc/AWS/vpc-byo-aws.adoc
Outdated
Show resolved
Hide resolved
modules/get-started/pages/cluster-types/byoc/AWS/vpc-byo-aws.adoc
Outdated
Show resolved
Hide resolved
modules/get-started/pages/cluster-types/byoc/AWS/vpc-byo-aws.adoc
Outdated
Show resolved
Hide resolved
== Limitations | ||
|
||
* You cannot move existing clusters to a customer-managed VPC. | ||
* You cannot change to a different VPC after creating a cluster with a customer-managed VPC. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So does this mean you can have one and only one customer-managed VPC amongst multiple clusters?
modules/get-started/pages/cluster-types/byoc/AWS/vpc-byo-aws.adoc
Outdated
Show resolved
Hide resolved
modules/get-started/pages/cluster-types/byoc/AWS/vpc-byo-aws.adoc
Outdated
Show resolved
Hide resolved
modules/get-started/pages/cluster-types/byoc/AWS/vpc-byo-aws.adoc
Outdated
Show resolved
Hide resolved
modules/get-started/pages/cluster-types/byoc/AWS/vpc-byo-aws.adoc
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See comments/suggestions
modules/get-started/pages/cluster-types/byoc/AWS/vpc-byo-aws.adoc
Outdated
Show resolved
Hide resolved
…er-aws.adoc Co-authored-by: Joyce Fee <[email protected]>
Co-authored-by: Joyce Fee <[email protected]>
Co-authored-by: Joyce Fee <[email protected]>
Co-authored-by: Joyce Fee <[email protected]>
Co-authored-by: Joyce Fee <[email protected]>
also add aliases & update links to new locations
Co-authored-by: Joyce Fee <[email protected]>
Co-authored-by: Joyce Fee <[email protected]>
Co-authored-by: Joyce Fee <[email protected]>
1. Remove redpanda_cloud_storage_manager_policy it is no longer used 2. Add "arn" prefix to connectors_node_group_instance_profile 3. Add permissions boundary field
ed4c5fa
to
7ca4ce7
Compare
# Conflicts: # modules/ROOT/nav.adoc # modules/get-started/pages/cluster-types/byoc/aws-1/create-byoc-cluster-aws.adoc # modules/get-started/pages/cluster-types/byoc/aws/create-byoc-cluster-aws.adoc # modules/get-started/pages/cluster-types/byoc/azure-1/create-byoc-cluster-azure.adoc # modules/get-started/pages/cluster-types/byoc/azure/create-byoc-cluster-azure.adoc # modules/get-started/pages/cluster-types/byoc/create-byoc-cluster-aws.adoc # modules/get-started/pages/cluster-types/byoc/create-byoc-cluster-azure.adoc # modules/get-started/pages/cluster-types/byoc/create-byoc-cluster-gcp.adoc # modules/get-started/pages/cluster-types/byoc/gcp-1/create-byoc-cluster-gcp.adoc # modules/get-started/pages/cluster-types/byoc/gcp-1/vpc-byo-gcp.adoc # modules/get-started/pages/cluster-types/byoc/gcp/create-byoc-cluster-gcp.adoc # modules/get-started/pages/cluster-types/byoc/gcp/vpc-byo-gcp.adoc # modules/get-started/pages/cluster-types/byoc/vpc-byo-gcp.adoc
# Conflicts: # modules/get-started/pages/cluster-types/byoc/aws/create-byoc-cluster-aws.adoc # modules/get-started/pages/whats-new-cloud.adoc
|
||
include::shared:partial$feature-flag.adoc[] | ||
|
||
With a standard BYOC cluster, Redpanda manages the VPC lifecycle. For additional security, you can deploy the Redpanda glossterm:data plane[] into your existing shared VPC and manage the VPC lifecycle yourself. When you create a BYOC cluster, you specify your VPC and service account. The Redpanda Cloud agent doesn't create any new resources or alter any settings in your account. With a *customer-managed* VPC: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Redpanda Cloud agent doesn't create any new resources or alter any settings in your account.
This feels a little off. We will create many resources, but we will not create VPC or network resources.
# Conflicts: # modules/get-started/pages/cloud-overview.adoc # modules/get-started/pages/cluster-types/byoc/gcp/create-byoc-cluster-gcp.adoc # modules/get-started/pages/whats-new-cloud.adoc
Adding notes from David:
|
Providing gist here of my working updates to commands in this doc. High level comments.
|
Going to add this as a follow-up improvement because this one has been open for so long and we need it for the 24.3 announcement tomorrow. |
Description
Resolves https://github.com/redpanda-data/documentation-private/issues/2359
Review deadline: Aug 6
Status: This is in private beta.
Because Cloud docs moved into a separate repo, I had to move redpanda-data/docs#550 into this new PR.
This also nests AWS, Azure, and GCP folders under Create BYOC in the side nav (+ adds aliases and updates links to the new file locations).
Page previews
Checks