You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -12,25 +11,24 @@ TIP: For more detailed information about the Redpanda platform, see xref:get-sta
12
11
== Redpanda Cloud cluster types
13
12
14
13
Redpanda offers four types of fully-managed cloud clusters. All products have access to unlimited storage and 280+ data connectors with xref:develop:connect/about.adoc[Redpanda Connect].
15
-
16
14
|===
17
-
| <<Serverless>> | <<Dedicated Cloud>> | <<Bring Your Own Cloud (BYOC)>>
18
-
19
-
| For starter projects and applications with low or variable traffic. | For production clusters requiring expert cloud hosting, higher throughput, and extra isolation. | For production clusters requiring data sovereignty, the highest throughput, and added security.
20
-
| Multi-tenant on AWS | Single-tenant on AWS, Azure, or GCP | In your cloud on AWS, Azure, or GCP
21
-
| 100 MB/s max write throughput | 400 MB/s max write throughput | 2 GB/s max write throughput
22
-
| 300 MB/s max read throughput | 800 MB/s max read throughput | 4 GB/s max read throughput
| <<Serverless>> | <<Bring Your Own Cloud (BYOC)>> | <<Dedicated>>
16
+
17
+
| For starter projects and applications with low or variable traffic. | For production clusters requiring data sovereignty, the highest throughput, and added security. | For production clusters requiring expert cloud hosting, higher throughput, and extra isolation.
18
+
| Multi-tenant in Redpanda Cloud on AWS | In your cloud on AWS, Azure, or GCP | Single-tenant in Redpanda Cloud on AWS, Azure, or GCP
19
+
| 100 MB/s max write throughput | 2 GB/s max write throughput | 400 MB/s max write throughput
20
+
| 300 MB/s max read throughput | 4 GB/s max read throughput | 800 MB/s max read throughput
With BYOC clusters, you deploy Redpanda in your own cloud (AWS, Azure, or GCP), and all data is
48
+
contained in your own environment. This provides an additional layer of security and isolation. (See <<BYOC architecture>>.) When you create a BYOC cluster, you select the supported xref:reference:tiers/byoc-tiers.adoc[tier] that meets your compute and storage needs. Redpanda handles provisioning, operations, and maintenance.
49
+
50
+
NOTE: With standard BYOC clusters, Redpanda manages security policies and resources for your VPC or VNet, including subnetworks, IAM roles, and storage buckets/accounts. A Bring Your Own Virtual Private Cloud (BYOVPC) cluster allows you to deploy the Redpanda glossterm:data plane[] into your existing VPC/VNet and take full control of managing the networking lifecycle. Compared to standard BYOC, BYOVPC provides more security, but the configuration is more complex. See <<Shared responsibility model>>.
51
+
52
+
The BYOC infrastructure that Redpanda manages should not be used to deploy any other workloads.
53
+
54
+
==== Sign up for BYOC
55
+
56
+
To start using BYOC, contact https://redpanda.com/try-redpanda?section=enterprise-trial[Redpanda sales^] to request a private offer with possible discounts. You are billed directly or through Google Cloud Marketplace or AWS Marketplace.
57
+
58
+
=== Dedicated
48
59
49
-
With Dedicated clusters, you host your data on Redpanda cloud resources (AWS, GCP, or Azure), and Redpanda handles provisioning, operations, and maintenance. Dedicated clusters are single-tenant deployments that support private networking (for example, VPC peering to talk over private IPs) for better data isolation.
60
+
With Dedicated clusters, you host your data on Redpanda Cloud resources (AWS, GCP, or Azure), and Redpanda handles provisioning, operations, and maintenance. Dedicated clusters are single-tenant deployments that support private networking (for example, VPC peering to talk over private IPs) for better data isolation.
50
61
When you create a Dedicated cluster, you select the supported xref:reference:tiers/dedicated-tiers.adoc[tier] that meets your compute and storage needs.
51
62
52
63
==== Sign up for Dedicated
@@ -69,76 +80,30 @@ Redpanda creates a cloud organization for you and sends you a welcome email.
69
80
--
70
81
=====
71
82
72
-
=== Bring Your Own Cloud (BYOC)
73
-
74
-
With BYOC clusters, you deploy Redpanda in your own cloud (AWS, Azure, or GCP), and all data is
75
-
contained in your own environment. This provides an additional layer of security and isolation. (See <<BYOC architecture>>.) When you create a BYOC cluster, you select the supported xref:reference:tiers/byoc-tiers.adoc[tier] that meets your compute and storage needs. Redpanda handles provisioning, operations, and maintenance.
76
-
77
-
NOTE: With standard BYOC clusters, Redpanda manages security policies and resources for your VPC or VNet, including subnetworks, IAM roles, and storage buckets/accounts. A Bring Your Own Virtual Private Cloud (BYOVPC) cluster allows you to deploy the Redpanda glossterm:data plane[] into your existing VPC/VNet and take full control of managing the networking lifecycle. Compared to standard BYOC, BYOVPC provides more security, but the configuration is more complex. See <<Shared responsibility model>>.
78
-
79
-
The BYOC infrastructure that Redpanda manages should not be used to deploy any other workloads.
80
-
81
-
==== Sign up for BYOC
82
-
83
-
To start using BYOC, contact https://redpanda.com/try-redpanda?section=enterprise-trial[Redpanda sales^] to request a private offer with possible discounts. You are billed directly or through Google Cloud Marketplace or AWS Marketplace.
84
-
85
-
== Serverless vs Dedicated/BYOC
83
+
== Serverless vs BYOC/Dedicated
86
84
87
85
Serverless clusters are a good fit for the following use cases:
88
86
89
87
* Starter and growing workloads
90
88
* Spiky workloads (that is, development environments, systems that only occasionally get busy, or workloads that come and go)
91
89
* Fast and dynamic cluster creation: you can use a Serverless cluster as an isolated container for topics
92
90
93
-
With Serverless (and for Dedicated when procured through the AWS Marketplace), you only pay for what you consume, without any commitment. A cluster is created instantly, so you can surface it in your applications (for example, for tenant isolation). If your workload increases, you can migrate it to a Dedicated or BYOC cluster.
91
+
With Serverless (and for Dedicated when procured through the AWS Marketplace), you only pay for what you consume, without any commitment. A cluster is created instantly, so you can surface it in your applications (for example, for tenant isolation). If your workload increases, you can migrate it to a BYOC or Dedicated cluster.
94
92
95
-
Consider Dedicated or BYOC if you need more control over the deployment or if you have workloads with consistently-high throughput. Dedicated and BYOC clusters offer the following features:
93
+
Consider BYOC or Dedicated if you need more control over the deployment or if you have workloads with consistently-high throughput. BYOC and Dedicated clusters offer the following features:
96
94
97
95
* Private networking
98
96
* Single-zone or multi-zone availability. A multi-zone cluster provides higher resiliency in the event of a failure in one of the zones.
99
97
* Ability to export metrics to a 3rd-party monitoring system
100
98
* Kafka Connect
101
-
* Higher limits and quotas. See xref:reference:tiers/dedicated-tiers.adoc[Dedicated usage tiers] and xref:reference:tiers/byoc-tiers.adoc[BYOC usage tiers] compared to xref:get-started:cluster-types/serverless.adoc#serverless-usage-limits[Serverless limits].
99
+
* Higher limits and quotas. See xref:reference:tiers/byoc-tiers.adoc[BYOC usage tiers] and xref:reference:tiers/dedicated-tiers.adoc[Dedicated usage tiers] compared to xref:get-started:cluster-types/serverless.adoc#serverless-usage-limits[Serverless limits].
102
100
103
101
== Shared responsibility model
104
102
105
103
The Redpanda Cloud shared responsibility model lists the security ownership areas for Redpanda and customers. Responsibilities depend on the type of deployment.
After you log in to https://cloud.redpanda.com[Redpanda Cloud^], you land on the *Clusters* page. This page lists all the clusters in your organization.
6
+
7
+
== Create a Dedicated cluster
8
+
9
+
. On the Clusters page, click *Create cluster*, then click *Create Dedicated cluster*.
10
+
+
11
+
Enter a cluster name, then select the resource group, cloud provider (AWS, GCP, or Azure), xref:reference:tiers/dedicated-tiers.adoc[region, tier], availability, and Redpanda version.
12
+
13
+
+
14
+
[NOTE]
15
+
====
16
+
* If you plan to create a private network in your own VPC, select the region where your VPC is located.
17
+
* Three availability zones provide two backups in case one availability zone goes down.
18
+
====
19
+
+
20
+
[IMPORTANT]
21
+
====
22
+
To unlock this feature for Azure, contact https://support.redpanda.com/hc/en-us/requests/new[Redpanda support^].
23
+
====
24
+
25
+
. Click *Next*.
26
+
. On the Network page, enter the connection type: *Public* or *Private*. For private networks:
27
+
** Your network name is used to identify this network.
28
+
** For a xref:networking:cidr-ranges.adoc[CIDR range], choose one that does not overlap with your existing VPCs or your Redpanda network.
29
+
+
30
+
Private networks require either a VPC peering connection or a private connectivity service, such as xref:networking:configure-privatelink-in-cloud-ui.adoc[AWS PrivateLink], xref:networking:configure-private-service-connect-in-cloud-ui.adoc[GCP Private Service Connect], or xref:networking:azure-private-link.adoc[Azure Private Link].
31
+
32
+
. Click *Create*.
33
+
34
+
After the cluster is created, you can select the cluster on the *Clusters* page to see the overview for it.
35
+
36
+
include::shared:partial$kafka-connect.adoc[]
37
+
38
+
== Start streaming: example
39
+
40
+
Use `rpk`, Redpanda's CLI, to build a basic streaming application that creates a topic, produces messages to it, and consumes messages from it. To learn about `rpk`, see the xref:manage:rpk/intro-to-rpk.adoc[].
41
+
42
+
. Login to Redpanda Cloud, and select your resource group using the interactive prompt.
43
+
+
44
+
```bash
45
+
rpk cloud login
46
+
```
47
+
48
+
. On the **Overview** page, copy your bootstrap server address and set it as an environment variable on your local machine:
0 commit comments