Create a Redis database
Select a Redis version, region, and resource plan.
Before you begin
Select the intended workspace and project. Ensure an active billing account with positive, unexpired credits is linked to the project. Plan where client applications will run so they can reach the private endpoint.
Create the instance
- Open Memory Database and select Create memory database.
- Enter a Memory database name.
- Select an available Redis version and Region.
- Choose a Plan and review its capacity and price.
- Review Summary (on the right on wide screens, or below the form on smaller screens) and select Create memory database.
- Open the new resource and wait for provisioning and startup to complete.
The instance is private by default. Available versions and plans come from the Console's current catalog rather than a fixed list in this guide.
Usable memory
RDC Cloud sets Redis's usable memory limit to 75% of the instance memory included in your plan to reduce the risk of the database stopping because it runs out of memory. The remaining 25% provides operating headroom for memory overhead, client buffers, and background work.
For example, a 512 MiB instance has a 384 MiB Redis memory limit. This limit includes Redis memory overhead, so the amount of application data you can store may be lower. See Memory allocation and limits for how the limit is enforced.
Summary updates as you edit the name, version, region, and plan. It shows the selected project, CPU, instance memory, and hourly price before you submit.
Verify and continue
Check Overview for runtime status, then open Connection to retrieve the managed customer credential. Follow Connect to Redis to verify a response.
Plan availability
Plans are specific to Memory Database. A plan with the same name in another RDC Cloud product can have different capacity or pricing. Review the plan offered for the selected region. If a previously selected plan is no longer available, refresh the creation page and select an available plan again.
Storage availability
Storage allowances for newly created databases are monitored, not enforced as a hard disk quota. Creation or data import can be temporarily unavailable when storage capacity is low. If this happens, contact support with the resource ID, if available, and the displayed error. Existing databases are not automatically stopped when they exceed their allowance.
Workspace availability
The selected workspace determines which regions, plans, and database engine versions you can choose. A plan must also be available in the selected region. If an option disappears before you submit, refresh the page and choose an available option. Contact support if your workspace needs access to an unavailable option.
Changes to availability do not delete existing resources or prevent you from viewing, stopping, or deleting them.