1 - Overview

Service Overview

CacheStore (DBaaS) is a service that provides the in‑memory data stores Redis OSS and Valkey. Samsung Cloud Platform provides an environment that automates the installation of Redis OSS and valkey through a web-based console and performs management functions for operation.

CacheStore(DBaaS) provides a Sentinel architecture composed of a Master server that performs read/write operations and read‑only Replica servers that replicate the Master data. Sentinel checks the status of DB servers where the engine is installed, and if a failure occurs on the Master server, it automatically fails over the Replica servers to the Master server. Additionally, to prepare for potential issues with the DB server or data, we provide a feature that automatically backs up at a user-specified time, allowing data recovery based on the backup point.

Architecture
Figure. CacheStore(DBaaS) Architecture

Provided features

CacheStore (DBaaS) provides the following features.

  • Auto Provisioning: UI allows installation and configuration of Database (DB), and a redundant configuration with a Sentinel-based Single Master server and Replica servers (1 or 2) is possible.
  • Operation Control Feature: Provides a function that controls the status of running servers. * In addition to start and stop, a restart is possible if there is a DB issue or to apply configuration changes. * When configured for high availability (HA), you can switch the Active-Standby servers using a switch‑over.
  • Backup and Recovery: Provides data backup functionality based on its own backup commands. * The backup time window and storage location can be set by the user, and additional charges are incurred based on the backup size. * It also provides a recovery function for backed‑up data, so when the user initiates a recovery, a separate database is created and the recovery proceeds to the point in time selected by the user.
  • Parameter Management: It is possible to modify DB configuration parameters related to performance improvement and security.
  • Service Status Query: Retrieves the final status of the current DB service.
  • Monitoring: CPU, memory, performance monitoring information can be viewed through Cloud Monitoring and Servicewatch.
  • Minor version upgrade: Minor version upgrades can be performed within the same Major version to apply some feature improvements and security patches.

Components

CacheStore (DBaaS) provides pre‑validated engine versions and various server types in accordance with its open‑source support policy. Users can select and use it according to the scale of the service they wish to configure.

Engine version

The engine versions supported by CacheStore (DBaaS) are as follows.

Technical support is available until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is halted is set to six months before the EoTS date.

Since the EOS and EoTS dates may change according to the supplier’s policy, please refer to the supplier’s license management policy page for details.

serviceProvided versionEoS Date (Samsung Cloud Plaform New Creation Stop Date)EoTS date (Community technical support end date)
Redis OSS Sentinel7.2.112026-07-162029-12-01
Redis OSS Sentinel7.2.142029-06 (예정)2029-12-01
valkey Sentinel8.1.42026-07-16TBD
valkey Sentinel8.1.8TBDTBD
valkey Sentinel9.0.4TBDTBD
Table. Engine versions provided by CacheStore (DBaaS)

Server type

The server types supported by CacheStore (DBaaS) are as follows.

For detailed information about the server types provided by CacheStore(DBaaS), see CacheStore(DBaaS) 서버 타입.

Standard redis1v2m4
CategoryexampleDetailed description
Server typeStandardProvided server type
  • Standard: Standard configuration (vCPU, Memory) commonly used
Server specificationsredis1Provided server specifications
  • redis1: Standard specifications (vCPU, Memory) commonly used
Server specificationsv2Number of vCores
  • v2: 2 virtual cores
Server specificationsm4Memory capacity
  • m4: 4GB Memory
Table. CacheStore (DBaaS) server type components

Preliminary Service

This is a list of services that must be pre‑configured before creating the service. For detailed information, please refer to the guide provided for each service and prepare in advance.

Service CategoryserviceDetailed description
NetworkingVPCA service that provides an isolated virtual network in a cloud environment
Table. CacheStore (DBaaS) Pre-service

1.1 - Server type

CacheStore(DBaaS) server type

CacheStore (DBaaS) offers server types configured with various combinations such as CPU, Memory, and Network Bandwidth. When creating a CacheStore (DBaaS), Redis is installed according to the server type selected for the intended purpose.

Reference
The server types offered may vary depending on the region and AZ.

The server types supported by CacheStore (DBaaS) are as follows.

Standard redis1v2m4
Category
exampleDetailed description
Server typeStandardProvided server type classification
  • Standard: composed of the commonly used standard specifications (vCPU, Memory)
Server specificationsredis1Provided server type classification and generation
  • redis: means a standard specification, and 1 indicates the generation
Server specificationsv2Number of vCores
  • v2: 2 virtual cores
Server specificationsm4Memory capacity
  • m4: 4GB Memory
Table. CacheStore (DBaaS) server type format

redis1 server type

The redis1 server type of CacheStore (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.

  • Intel 3rd Generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
  • Supports up to 16 vCPUs and 256 GB of memory
  • Maximum networking speed of 12.5 Gbps
CategoryServer typevCPUMemoryNetwork Bandwidth
Standardredis1v1m21 vCore2 GBUp to 10 Gbps
Standardredis1v2m42 vCore4 GBUp to 10 Gbps
Standardredis1v2m82 vCore8 GBUp to 10 Gbps
Standardredis1v2m162 vCore16 GBUp to 10 Gbps
Standardredis1v2m242 vCore24 GBUp to 10 Gbps
Standardredis1v4m84 vCore8 GBUp to 10 Gbps
Standardredis1v4m164 vCore16 GBUp to 10 Gbps
Standardredis1v4m324 vCore32 GBUp to 10 Gbps
Standardredis1v4m484 vCore48 GBUp to 10 Gbps
Standardredis1v4m644 vCore64 GBUp to 10 Gbps
Standardredis1v6m726 vCore72 GBUp to 10 Gbps
Standardredis1v6m966 vCore96 GBUp to 10 Gbps
Standardredis1v8m1288 vCore128 GBUp to 10 Gbps
Standardredis1v10m16010 vCore160 GBUp to 10 Gbps
Standardredis1v12m19212 vCore192 GBUp to 12.5 Gbps
Standardredis1v14m22414 vCore224 GBUp to 12.5 Gbps
Standardredis1v16m25616 vCore256 GBUp to 12.5 Gbps
Table. CacheStore (DBaaS) server type specifications - redis1 server type

redis2 server type

The redis2 server type of CacheStore (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.

  • Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
  • Supports up to 16 vCPUs and 256 GB of memory
  • Maximum networking speed of 12.5 Gbps
CategoryServer typevCPUMemoryNetwork Bandwidth
Standardredis2v1m21 vCore2 GBUp to 10 Gbps
Standardredis2v2m42 vCore4 GBUp to 10 Gbps
Standardredis2v2m82 vCore8 GBUp to 10 Gbps
Standardredis2v2m162 vCore16 GBUp to 10 Gbps
Standardredis2v2m242 vCore24 GBUp to 10 Gbps
Standardredis2v4m84 vCore8 GBUp to 10 Gbps
Standardredis2v4m164 vCore16 GBUp to 10 Gbps
Standardredis2v4m324 vCore32 GBUp to 10 Gbps
Standardredis2v4m484 vCore48 GBUp to 10 Gbps
Standardredis2v4m644 vCore64 GBUp to 10 Gbps
Standardredis2v6m726 vCore72 GBUp to 10 Gbps
Standardredis2v96m966 vCore96 GBUp to 10 Gbps
Standardredis2v8m1288 vCore128 GBUp to 10 Gbps
Standardredis2v10m16010 vCore160 GBUp to 10 Gbps
Standardredis2v12m19212 vCore192 GBUp to 12.5 Gbps
Standardredis2v14m22414 vCore224 GBUp to 12.5 Gbps
Standardredis2v16m25616 vCore256 GBUp to 12.5 Gbps
Table. CacheStore(DBaaS) server type specifications - redis2 server type

redis3 server type

The redis3 server type of CacheStore (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.

  • Intel 6th‑generation (Granite Rapids) Xeon 6737P Processor up to 4.0 GHz
  • Supports up to 16 vCPUs and 256 GB of memory
  • Maximum networking speed of 12.5 Gbps
CategoryServer typevCPUMemoryNetwork Bandwidth
Standardredis3v1m21 vCore2 GBUp to 10 Gbps
Standardredis3v2m42 vCore4 GBUp to 10 Gbps
Standardredis3v2m82 vCore8 GBUp to 10 Gbps
Standardredis3v162 vCore16 GBUp to 10 Gbps
Standardredis3v2m242 vCore24 GBUp to 10 Gbps
Standardredis3v4m84 vCore8 GBUp to 10 Gbps
Standardredis3v4m164 vCore16 GBUp to 10 Gbps
Standardredis3v4m324 vCore32 GBUp to 10 Gbps
Standardredis3v4m484 vCore48 GBUp to 10 Gbps
Standardredis3v4m644 vCore64 GBUp to 10 Gbps
Standardredis3v6m726 vCore72 GBUp to 10 Gbps
Standardredis3v6m966 vCore96 GBUp to 10 Gbps
Standardredis3v8m1288 vCore128 GBUp to 10 Gbps
Standardredis3v10m16010 vCore160 GBUp to 10 Gbps
Standardredis3v12m19212 vCore192 GBUp to 12.5 Gbps
Standardredis3v14m22414 vCore224 GBUp to 12.5 Gbps
Standardredis3v16m25616 vCore256 GBUp to 12.5 Gbps
Table. CacheStore (DBaaS) server type specifications - redis3 server type

css1 server type

The css1 server type of CacheStore (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.

  • Intel 3rd Generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
  • Supports up to 16 vCPUs and 256 GB of memory
  • Maximum networking speed of 12.5 Gbps
CategoryServer typevCPUMemoryNetwork Bandwidth
Standardcss1v1m21 vCore2 GBUp to 10 Gbps
Standardcss1v2m42 vCore4 GBUp to 10 Gbps
Standardcss1v2m82 vCore8 GBUp to 10 Gbps
Standardcss1v2m162 vCore16 GBUp to 10 Gbps
Standardcss1v2m242 vCore24 GBUp to 10 Gbps
Standardcss1v4m84 vCore8 GBUp to 10 Gbps
Standardcss1v4m164 vCore16 GBUp to 10 Gbps
Standardcss1v4m324 vCore32 GBUp to 10 Gbps
Standardcss1v4m484 vCore48 GBUp to 10 Gbps
Standardcss1v4m644 vCore64 GBUp to 10 Gbps
Standardcss1v6m726 vCore72 GBUp to 10 Gbps
Standardcss1v6m966 vCore96 GBUp to 10 Gbps
Standardcss1v8m1288 vCore128 GBUp to 10 Gbps
Standardcss1v10m16010 vCore160 GBUp to 10 Gbps
Standardcss1v12m19212 vCore192 GBUp to 12.5 Gbps
Standardcss1v14m22414 vCore224 GBUp to 12.5 Gbps
Standardcss1v16m25616 vCore256 GBUp to 12.5 Gbps
Table. CacheStore(DBaaS) server type specifications - css1 server type

css2 server type

CacheStore(DBaaS)’s css2 server type is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.

  • Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
  • Supports up to 16 vCPUs and 256 GB of memory
  • Maximum networking speed of 12.5 Gbps
CategoryServer typevCPUMemoryNetwork Bandwidth
Standardcss2v1m21 vCore2 GBUp to 10 Gbps
Standardcss2v2m42 vCore4 GBUp to 10 Gbps
Standardcss2v2m82 vCore8 GBUp to 10 Gbps
Standardcss2v2m162 vCore16 GBUp to 10 Gbps
Standardcss2v2m242 vCore24 GBUp to 10 Gbps
Standardcss2v4m84 vCore8 GBUp to 10 Gbps
Standardcss2v4m164 vCore16 GBUp to 10 Gbps
Standardcss2v4m324 vCore32 GBUp to 10 Gbps
Standardcss2v4m484 vCore48 GBUp to 10 Gbps
Standardcss2v4m644 vCore64 GBUp to 10 Gbps
Standardcss2v6m726 vCore72 GBUp to 10 Gbps
Standardcss2v6m966 vCore96 GBUp to 10 Gbps
Standardcss2v8m1288 vCore128 GBUp to 10 Gbps
Standardcss2v10m16010 vCore160 GBUp to 10 Gbps
Standardcss2v12m19212 vCore192 GBUp to 12.5 Gbps
Standardcss2v14m22414 vCore224 GBUp to 12.5 Gbps
Standardcss2v16m25616 vCore256 GBUp to 12.5 Gbps
Table. CacheStore(DBaaS) server type specifications - css2 server type

css3 server type

The css3 server type of CacheStore(DBaaS) is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.

  • Intel 6th‑generation (Granite Rapids) Xeon 6737P Processor up to 4.0 GHz
  • Supports up to 16 vCPUs and 256 GB of memory
  • Maximum networking speed of 12.5 Gbps
CategoryServer typevCPUMemoryNetwork Bandwidth
Standardcss3v1m21 vCore2 GBUp to 10 Gbps
Standardcss3v2m42 vCore4 GBUp to 10 Gbps
Standardcss3v2m82 vCore8 GBUp to 10 Gbps
Standardcss3v2m162 vCore16 GBUp to 10 Gbps
Standardcss3v2m242 vCore24 GBUp to 10 Gbps
Standardcss3v4m84 vCore8 GBUp to 10 Gbps
Standardcss3v4m164 vCore16 GBUp to 10 Gbps
Standardcss3v4m324 vCore32 GBUp to 10 Gbps
Standardcss3v4m484 vCore48 GBUp to 10 Gbps
Standardcss3v4m644 vCore64 GBUp to 10 Gbps
Standardcss3v6m726 vCore72 GBUp to 10 Gbps
Standardcss3v6m966 vCore96 GBUp to 10 Gbps
Standardcss3v8m1288 vCore128 GBUp to 10 Gbps
Standardcss3v10m16010 vCore160 GBUp to 10 Gbps
Standardcss3v12m19212 vCore192 GBUp to 12.5 Gbps
Standardcss3v14m22414 vCore224 GBUp to 12.5 Gbps
Standardcss3v16m25616 vCore256 GBUp to 12.5 Gbps
Table. CacheStore(DBaaS) server type specifications - css3 server type

1.2 - Monitoring metrics

Cloud Monitoring Service Termination Notice

According to the policy of Samsung Cloud Platform, the Cloud Monitoring service is scheduled to be terminated.

Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.

To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.

  1. Guide to Applying Monitoring Services by Resource

    • New Resources: Resources created after the service improvement work in July 2026 are monitored by default using the ServiceWatch service.
    • Existing resources: After the service improvement work in September 2026 We provide concurrent monitoring through Cloud Monitoring and ServiceWatch services.
    • During the parallel operation period, we must prepare for the Servicewatch transition. *
      Performance and log data backup, user-configured settings integrated with existing Cloud Monitoring (e. You need to review the event policies, etc., perform tasks such as resetting the ServiceWatch service, and complete them.
  2. Cloud Monitoring Service Phased Termination Schedule Notice

    • Console menu termination (September 2026 service improvement work)
      • You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
  • Service termination (service improvement work in November 2026)
    • All services of Cloud Monitoring, including the API, will be permanently discontinued.
      • After the service ends in November, Cloud Monitoring data cannot be accessed. * Be sure to complete the ServiceWatch migration within the parallel operation period**.

Detailed information about ServiceWatch can be found in the ServiceWatch 개요.

CacheStore(DBaaS) Monitoring Metrics

The table below shows the performance monitoring metrics for CacheStore (DBaaS) that can be viewed through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.

For CacheStore (DBaaS) server monitoring metrics, refer to the Virtual Server Monitoring Metrics guide.

Performance itemsDetailed descriptionunit
Active Defragmentation Keys [Hits]Number of keys after defragmentationcnt
Active Defragmentation Keys [Miss]Number of keys skipped in the active defragmentation removal processcnt
Active Defragmentationd [Hits]Number of value reallocations performed by the active defragmentation removal processcnt
Active Defragmentations [Miss]Count of value reallocations interrupted by the active defragmentation removal processcnt
Allocated Bytes [OS]Number of bytes allocated by CacheStore (DBaaS) and recognized by the operating system (resident set size)bytes
Allocated Bytes [Redis]Total bytes allocated by CacheStore (DBaaS)bytes
AOF Buffer SizeAOF buffer sizebytes
AOF File Size [Current]AOF current file sizebytes
AOF File Size [Lastest Startup]AOF file size on recent start or rewritebytes
AOF Rewrite Buffer SizeAOF rewrite buffer sizebytes
AOF Rewrite Current TimeIf applicable, the time of the ongoing AOF rewrite operationsec
AOF Rewrite Last TimeFinal AOF rewrite timesec
CallsNumber of calls that reached command execution (not rejected)cnt
Changes [Last Saved]Number of changes after the final dumpcnt
Client Output Buffer [MAX]Longest output list among current client connectionscnt
Clients [Sentinel]Number of client connections (Sentinel)cnt
Connected SlavesNumber of connected slavescnt
Connections [Blocked]Number of clients pending on blocking calls (BLPOP, BRPOP, BRPOPLPUSH)cnt
Connections [Current]Number of client connections (excluding slave connections)cnt
Copy On Write Allocated Size [AOF]COW allocation size during final RBD save operationbytes
Copy On Write Allocated Size [RDB]COW allocation size during the final RBD save operationbytes
CPU Time [Average]Average CPU time used per command executioncnt
CPU Time [Total]Total CPU time used by these commandsusec
CPU Usage [System Process]System CPU usage by background processes%
CPU Usage [System]System CPU usage on the CacheStore (DBaaS) server%
CPU Usage [User Process]User CPU usage used by background processes%
CPU Usage [User]System CPU usage by background processes%
Dataset UsedDataset sizebytes
Disk Useddatadir usageMB
Evicted KeysNumber of evicted keys caused by the maxmemory limitcnt
Fsyncs [Delayed]Delayed fsync countercnt
Fsyncs [Pending]Number of pending fsync operations in the background I/O queuecnt
Full ResyncsNumber of full resynchronizations with the slavecnt
Keys [Expired]Total number of key expiration eventscnt
Keys [Keyspace]Number of keys in the key spacecnt
Lastest Fork Duration TimeRecent fork (fork) operation timeusec
Lookup Keys [Hit]Number of successful key lookups in the dictionarycnt
Lookup Keys [Miss]Number of failed key lookups in the main dictionarycnt
Lua Engine Memory UsedMemory used by the Lua enginebytes
Master Last Interaction Time AgoTime elapsed since the final interaction with the mastersec
Master Last Interaction Time Ago [Sync]Time elapsed since the final interaction with the mastersec
Master OffsetCurrent replication offset of the serverpid
Master Second OffsetOffset until the replication ID is acceptedpid
Master Sync Left BytesRemaining bytes before synchronization completesbytes
Memory Fragmentation RateRatio of used_memory_rss to used_memory%
Memory Fragmentation Rate [Allocator]Fragmentation ratio%
Memory Fragmentation UsedBytes between used_memory_rss and used_memorybytes
Memory Fragmentation Used [Allocator]resident bytebytes
Memory Max ValueMemory limitbytes
Memory Resident [Allocator]resident memorybytes
Memory RSS Rate [Allocator]Resident ratio%
Memory Used [Active]Active memorybytes
Memory Used [Allocated]Allocated memorybytes
Memory Used [Resident]Resident bytebytes
Network In Bytes [Total]Total network input (bytes)bytes
Network Out Bytes [Total]Total network output (bytes)bytes
Network Read RateNetwork read speed (KB/sec)cnt
Network Write RateNetwork write speed (KB/sec)cnt
Partial Resync Requests [Accepted]Number of accepted partial resynchronization requestscnt
Partial Resync Requests [Denied]Number of rejected partial resynchronization requestscnt
Peak Memory ConsumedMaximum memory used by CacheStore (DBaaS)bytes
Processed CommandsNumber of commands processed per secondcnt
Processed Commands [Total]Total number of processed commandscnt
Pub/Sub ChannelsGlobal count of pub/sub channels with client subscriptionscnt
Pub/Sub PatternsGlobal count of publish/subscribe patterns with client subscriptionscnt
RDB Saved Duration Time [Current]If applicable, the time of the ongoing RDB save operationsec
RDB Saved Duration Time [Last]Final RDB save operation timesec
Received Connections [Total]Total number of received connectionscnt
Rejected Connections [Total]Total number of rejected connectionscnt
Replication Backlog Actove CountReplication backlog activation flagcnt
Replication Backlog Master OffsetMaster offset of the replication backlog buffercnt
Replication Backlog SizeData size of the replication backlog bufferbytes
Replication Backlog Size [Total]Total size of the replication backlog bufferbytes
Slave PriorityServer priority as a fault remediation targetcnt
Slave Replication OffsetReplication offset of the slave serverpid
Slow OperationsNumber of slow taskscnt
Sockets [MIGRATE]Number of sockets opened for migrationcnt
Tracked Keys [Expiry]Number of keys tracked for expiration (applicable only to writable slaves)cnt
Instance Status [PID]redis-server process PIDpid
Sentinel Status [PID]sentinel process PIDpid
Table. CacheStore (DBaaS) Monitoring Metrics

1.3 - ServiceWatch metric

CacheStore (DBaaS) sends metrics to ServiceWatch. The metrics provided by basic monitoring are data collected at 1‑minute intervals.

Reference
For instructions on how to view metrics in ServiceWatch, refer to the ServiceWatch guide.

Basic Metrics

The following are the basic metrics for the namespace CacheStore(DBaaS).

The indicators whose names are shown in bold below are the key metrics selected from the basic metrics provided by CacheStore(DBaaS). The key metrics are used to build service dashboards that are automatically created for each service in ServiceWatch.

Each metric provides guidance in the user guide on which statistical values are meaningful when viewing that metric, and among the meaningful statistics, the values shown in bold are the primary statistics. In the service dashboard, you can view key metrics through primary statistical values.

OS Basic Metrics

Classification
Performance itemsunitDetailed descriptionmeaningful statistics
CPUCPU UsagePercentCPU usage
  • Total
  • Average
  • Maximum
  • Minimum
DiskDisk UsagePercentDisk usage
  • Total
  • Average
  • Maximum
  • Minimum
DiskDisk Write BytesBytes/SecondWrite capacity (bytes/second) on block device
  • Total
  • Average
  • Maximum
  • Minimum
DiskDisk Read BytesBytes/SecondRead throughput from block device (bytes/second)
  • Total
  • Average
  • Maximum
  • Minimum
DiskDisk Write RequestsCount/SecondNumber of write requests on block device (requests per second)
  • Total
  • Average
  • Maximum
  • Minimum
DiskDisk Read RequestsCount/SecondNumber of read requests on block device (requests per second)
  • Total
  • Average
  • Maximum
  • Minimum
DiskAverage Disk I/O Queue SizeNoneAverage queue length of requests issued to the block device
  • Total
  • Average
  • Maximum
  • Minimum
DiskDisk I/O UtilizationPercentThe proportion of time the block device actually spent processing I/O operations
  • Total
  • Average
  • Maximum
  • Minimum
MemoryMemory UsagePercentMemory usage
  • Total
  • Average
  • Maximum
  • Minimum
MemorySwap Out BytesBytes/SecondAmount of data exported from memory to swap area (bytes/second)
  • Total
  • Average
  • Maximum
  • Minimum
MemorySwap Used BytesBytesCurrent swap space size
  • Total
  • Average
  • Maximum
  • Minimum
MemorySwap Cached UsagePercentCached swap usage rate
  • Total
  • Average
  • Maximum
  • Minimum
MemorySwap Total BytesBytesTotal swap space size configured on the system
  • Total
  • Average
  • Maximum
  • Minimum
MemorySwap In BytesBytes/SecondAmount read from swap area into memory (bytes/second)
  • Total
  • Average
  • Maximum
  • Minimum
MemorySwap UsagePercentCurrent usage ratio relative to total swap space
  • Total
  • Average
  • Maximum
  • Minimum
MemorySwap Cached BytesBytesSize of pages that have been restored to memory but still have a copy in the swap area
  • Total
  • Average
  • Maximum
  • Minimum
MemorySwap Free BytesBytesSize of unused remaining swap space
  • Total
  • Average
  • Maximum
  • Minimum
NetworkNetwork In BytesBytes/SecondReceived capacity (bytes/second) on the network interface
  • Total
  • Average
  • Maximum
  • Minimum
NetworkNetwork Out BytesBytes/SecondTransmitted capacity (bytes/second) on the network interface
  • Total
  • Average
  • Maximum
  • Minimum
NetworkTCP ConnectionsCount/SecondTotal number of TCP connections currently properly established
  • Total
  • Average
  • Maximum
  • Minimum
NetworkNetwork In PacketsCountNumber of packets received on the network interface
  • Total
  • Average
  • Maximum
  • Minimum
NetworkNetwork Out PacketsCountNumber of packets transmitted on the network interface
  • Total
  • Average
  • Maximum
  • Minimum
NetworkNetwork In DroppedCountNumber of packet drops received on the network interface
  • Total
  • Average
  • Maximum
  • Minimum
NetworkNetwork Out DroppedCountNumber of packet drops transmitted from the network interface
  • Total
  • Average
  • Maximum
  • Minimum
NetworkNetwork In ErrorsCountNumber of packet errors received on the network interface
  • Total
  • Average
  • Maximum
  • Minimum
NetworkNetwork Out ErrorsCountNumber of packet errors transmitted from the network interface
  • Total
  • Average
  • Maximum
  • Minimum
OSOS UptimeSecondsTime elapsed (seconds) since the system was last booted
  • Total
  • Average
  • Maximum
  • Minimum
Table. OS basic metrics

CacheStore(DBaaS) basic metrics

Classification
Performance itemsunitDetailed descriptionmeaningful statistics
Clientblocked clientsCountclient waiting due to a blocking call
  • Total
  • Average
  • Maximum
  • Minimum
Clientconnected clientsCountclients connected to Redis
  • Total
  • Average
  • Max
  • Min
Clientconnected replicasCountNumber of Replicas connected to the Master
  • Total
  • Average
  • Maximum
  • Minimum
Commandaverage command countsCount/MinuteAverage number of Redis commands processed per minute
  • Total
  • Average
  • Maximum
  • Minimum
keyskeys per dbCountNumber of registered keys per DB
  • Total
  • Average
  • Maximum
  • Minimum
keysexpired keys per dbCountNumber of expired keys registered per DB
  • Total
  • Average
  • Maximum
  • Minimum
keysevicted keysCount/MinuteNumber of evicted keys per minute in Redis memory
  • Total
  • Average
  • Maximum
  • Minimum
Memorykeyspace hits on memoryCount/MinuteNumber of keys retrieved from Redis memory per minute
  • Total
  • Average
  • Maximum
  • Minimum
Memorykeyspace_misses on memoryCount/MinuteNumber of keys that failed to be retrieved from Redis memory per minute
  • Total
  • Average
  • Maximum
  • Minimum
Memorymemory max bytesCountMaximum memory bytes available in Redis
  • Total
  • Average
  • Maximum
  • Minimum
Memorycurrent redis memory used bytesCountCurrent memory bytes used by Redis
  • Total
  • Average
  • Maximum
  • Minimum
Memorycurrent allocated redis memoryCountCurrent OS-allocated Redis memory size
  • Total
  • Average
  • Maximum
  • Minimum
Memoryredis_upCountRedis process On/Off
  • Total
  • Average
  • Maximum
  • Minimum
Memorymaster replication offsetCountReplication offset location for the Replica target within the Master server
  • Total
  • Average
  • Maximum
  • Minimum
Memoryaof buffer bytesCountThe buffer size that Redis allocates to the AOF
  • Total
  • Average
  • Max
  • Min
MemoryTotal client memory sizeCountTotal size of the input/output buffer allocated to the client
  • Total
  • Average
  • Maximum
  • Minimum
MemoryTotal replication buffer bytesCountTotal buffer bytes allocated to Replication
  • Total
  • Average
  • Maximum
  • Minimum
Memorydataset bytesCountmemory bytes used for user data
  • Total
  • Average
  • Maximum
  • Minimum
Memorymemory peak bytesCountMaximum memory usage of the Redis process, in bytes
  • Total
  • Average
  • Maximum
  • Minimum
Memorynetwork input bytesCount/MinuteNetwork bytes received by redis in 1 minute
  • Total
  • Average
  • Maximum
  • Minimum
Memorynetwork output bytesCount/MinuteNetwork bytes transmitted by redis in 1 minute
  • Total
  • Average
  • Maximum
  • Minimum
Memorycached script numberCountNumber of cached scripts
  • Total
  • Average
  • Maximum
  • Minimum
Memoryfunction numberCountNumber of cached functions
  • Total
  • Average
  • Maximum
  • Minimum
Memorylibrary numberCountNumber of cached libraries
  • Total
  • Average
  • Maximum
  • Minimum
Memorylast bgsave durationCountTime taken to create the last bgsave
  • Total
  • Average
  • Maximum
  • Minimum
Memoryslowlog queue lengthCountNumber of logs stored in the slowlog queue
  • Total
  • Average
  • Maximum
  • Minimum
Table. CacheStore (DBaaS) Basic Metrics

2 - How-to guides

Users can create the service by entering the required information for CacheStore(DBaaS) and selecting detailed options through the Samsung Cloud Platform Console.

Cloud Monitoring 서비스 종료 안내

According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be discontinued.

Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.

To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.

  1. Resource-specific Monitoring Service Application Guide

    • New Resources: Resources created after the service improvement work in July 2026 are provided with monitoring using the ServiceWatch service by default.
    • Existing resources: After the service improvement work in September 2026 We provide monitoring concurrently through the Cloud Monitoring service and the ServiceWatch service.
    • During the parallel operation period, we must prepare for the Servicewatch transition *
      Performance and log data backup, settings configured by users linked with existing Cloud Monitoring (e.g. You must verify the event policy, etc., and perform tasks such as resetting the ServiceWatch service, and then complete them.
  2. Cloud Monitoring Service Phased Termination Schedule Notice

    • Console menu termination (September 2026 service improvement work)
      • You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
  • Service termination (November 2026 service improvement work)
    • All services of Cloud Monitoring, including the API, will be permanently discontinued.
      • After the service ends in November, Cloud Monitoring data cannot be viewed. * Be sure to complete the ServiceWatch migration within the parallel operation period**

Detailed information about ServiceWatch can be found in the ServiceWatch 개요.

CacheStore(DBaaS) Create

You can create and use the CacheStore (DBaaS) service in the Samsung Cloud Platform Console.

안내
  • Before creating the service, configure the VPC’s Subnet type as General.
    • If the subnet type is Local, the creation of the corresponding Database service is not possible.
  • When loading more than 2 TB of large data, backups may take a long time or the database’s performance may degrade. * To prevent this, it is necessary to consider operational aspects such as cleaning up unnecessary data or migrating old data to a statistical collection environment.
  • This service is provided on a Single-AZ basis.

To create a CacheStore (DBaaS), follow the steps below.

  1. All Services > Database > CacheStore(DBaaS) Click the menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
  2. Click the Create CacheStore(DBaaS) button on the Service Home page. 2. Go to the Create CacheStore (DBaaS) page.
  3. On the Create CacheStore (DBaaS) page, enter the information required to create the service and select detailed options.
    • Select the required information in the Image and version selection area.
      Category
      Required status
      Detailed description
      Image versionRequiredProvide version list of CacheStore (DBaaS)
      Table. CacheStore (DBaaS) Image and version selection items
    • Enter or select the required information in the Service Information Input area.
      Category
      required status
      Detailed description
      Server name PrefixRequiredServer name where Redis/Valkey will be installed
      • must start with a lowercase English letter and be entered using lowercase letters, numbers, and special characters(-) with a length of 3 to 13 characters
      • Based on the server name, a postfix such as 001, 002 is appended to generate the actual server name
      Cluster nameRequiredCluster name where Redis/Valkey is installed
      • Enter using English letters, 3 to 20 characters
      • A cluster is a unit that groups multiple servers
      Service Type > Server TypeRequiredServer type for installing Redis/Valkey
      • Standard: the commonly used standard specification
      Service Type > Planned ComputeRequiredStatus of resources with Planned Compute set
      • In Use: Number of resources with Planned Compute that are currently in use
      • Configured: Number of resources with Planned Compute set
      • Coverage Preview: Amount applied per resource by Planned Compute
      Service Type > Block StorageRequiredBlock Storage settings used by the DB according to purpose
      • Basic OS: Area where the DB engine is installed
      • DATA: Storage area for table data, archive files, etc.
        • Select the storage type and then enter the capacity (see Block Storage 생성하기 for details on each Block Storage type)
          • SSD: High‑performance general volume
          • HDD: General volume
          • SSD_KMS, HDD_KMS: Additional encrypted volumes that use Samsung Cloud Platform KMS (Key Management System) encryption keys
        • The configured storage type is also applied to additional storage
        • Enter the capacity as a multiple of 8 within the range 16 to 5,120
      High availabilitySelectionHigh Availability (HA) configuration option
      • When High Availability (HA) is enabled, it is provided as a Master-Replica configuration, and the Replica can be configured with 1 or 2 instances
      • Sentinel Port number: The port used for connecting to Sentinel
        • Enter a port for Master-Replica communication within the range 1200 to 65535
      • Replica count: Number of Replicas to configure
        • If 1 is selected, it is configured as Master-Replica-Sentinel
        • If 2 is selected, it is configured as Master-Replica-Replica, and Sentinel is automatically installed on the server where Redis is installed
        • Set the server type for Sentinel to the minimum specification
      Network > Common SettingsRequiredNetwork settings for servers created by the service
      • Select when you want to apply the same settings to all installed servers
      • Select a pre‑created VPC and Subnet
      • Each server’s IP is generated automatically
      Network > Server-specific SettingsRequiredNetwork settings where servers generated by the service are installed
      • Select when you want to apply different settings for each installed server
      • Select a pre‑created VPC, Subnet, IP, and Public NAT
        • Enter the IP for each server
        • The Public NAT feature is available only when the VPC is connected to an Internet Gateway. Use when checked, you can select from reserved IPs in the VPC product’s Public IP. For more information, refer to Public IP 생성하기
      IP access controlSelectionService Access Policy Configuration
      • Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy.
      • Enter the IP in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.0/24, 192.168.10.1/32), and click the Add button.
      • To delete an entered IP, click the x button next to the IP.
      Maintenance PeriodSelectionCacheStore(DBaaS) maintenance window
      • If you select Use, you can set the day, start time, and duration
      • The maintenance window is a feature that allows the user to set the time slot for performing patch operations, and any patch work within that period must be performed directly by the user.
      • We ask you to set a maintenance window for the stable operation of the system, and we are not responsible for any issues arising from not setting it or from failure to perform tasks within the window.
      Table. CacheStore (DBaaS) Service Configuration Items
    • Enter required database configuration information In this area, enter or select the required information.
      Category
      Required status
      Detailed description
      BackupSelectionBackup usage
      • If you select Use, you can set the backup file retention period and backup start time
      • Backup files incur additional charges based on size
        • The file retention period can be set from 7 days to 35 days
      • The minute(s) when the backup runs is set randomly, and the backup end time cannot be set
      Redis/Valkey Port numberRequiredPort number required for connecting to Redis/Valkey
      • Enter a port within the range 1200 ~ 65535
      Redis/Valkey passwordRequiredPassword required when connecting to Redis/Valkey
      • Enter 8 ~ 30 characters, including English letters, numbers, and special characters ($ excluded)
      Check Redis/Valkey passwordRequiredRe-enter the same password
      ServiceWatch log collectionSelectionServiceWatch log collection status
      • Select Use to configure the ServiceWatch log collection feature
      • Provided free up to 5 GB for all services within the Account, and charges apply based on storage size for usage exceeding 5 GB.
      • When collected, log groups and log streams are created automatically, and they cannot be deleted until the resource is removed.
      • To prevent exceeding 5 GB, direct deletion of log data or shortening the retention period is recommended.
      ParameterRequiredParameters to use with Redis/Valkey
      • View button to view detailed information of the parameters
      • Parameters can be modified after creation is complete, and a DB restart is required after any modifications
      time zoneRequiredTime zone where the database will be used
      Table. CacheStore(DBaaS) Database configuration items
    • In the Additional Information Input area, enter or select the required information.
      Required status
      Detailed description
      tagSelectionAdd Tag
      • Up to 50 can be added per resource
      • After clicking the Add Tag button, input or select Key, Value values
      Table. CacheStore (DBaaS) additional information input fields
  4. Summary Verify the detailed information and estimated charges generated in the panel, then click the Create button.
    • When creation is complete, check the created resource on the Resource List page.

Check detailed information of CacheStore (DBaaS)

The CacheStore (DBaaS) service allows you to view and edit the full list of resources and detailed information. CacheStore(DBaaS) Details page consists of Detail Information, Tags, Activity History tabs.

Follow the steps below to view detailed information about the CacheStore (DBaaS) service.

  1. All Services > Database > CacheStore(DBaaS) Click the menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
  2. On the Service Home page, click the CacheStore(DBaaS) menu. 2. CacheStore(DBaaS) List Navigate to the page.
  3. CacheStore(DBaaS) List page, click the resource to view detailed information. 3. CacheStore(DBaaS) Details Go to the page.
    • CacheStore(DBaaS) Details At the top of the page, status information and additional feature details are displayed.
      Detailed description
      Cluster statusCluster status with Redis installed
      • Creating: Cluster is being created
      • Editing: Cluster is changing to an operational state
      • Error: Cluster encountered an error during operation
        • If it occurs continuously, contact the administrator
      • Failed: Cluster failed during creation
      • Restarting: Cluster is restarting
      • Running: Cluster is operating normally
      • Starting: Cluster is starting
      • Stopped: Cluster is stopped
      • Stopping: Cluster is stopping
      • Synchronizing: Cluster is synchronizing
      • Terminating: Cluster is being terminated
      • Unknown: Cluster status is unknown
        • If it occurs continuously, contact the administrator
      Cluster controlButtons that can change the cluster state
      • Start: Start a stopped cluster
      • Stop: Stop a running cluster
      • Restart: Restart a running cluster
      • Switch-Over: Switch a replica cluster to Master
      View more featuresCluster-related management buttons
      • Service status synchronization: Real-time Redis/Valkey service status lookup
      • Backup history: When backup is configured, check whether the backup runs correctly and view its history
      • Database recovery: Recover the DB based on a specific point in time
      • Parameter management: Ability to view and modify Redis/Valkey configuration parameters
      • Rename-Command: Change the name of a Redis/Valkey command
      Service cancellationCancel Service button
      Table. CacheStore (DBaaS) status information and additional features

Detailed Information

CacheStore(DBaaS) List page lets you view detailed information of the selected resource and modify it if needed.

Detailed description
Server InformationServer information configured in this cluster
  • Category: Server type (Master, Replica, Sentinel)
  • Server name: Server name
  • IP Port: Server IP and port
  • Availability Zone: Server creation location
  • Status: Server status
serviceService name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In the DB service, it refers to the cluster SRN
Resource NameResource name
  • In the DB service, it means the cluster name
Resource IDUnique resource ID in the service
ConstructorUser who created the service
Creation Date/TimeService creation date and time
ModifierUser who edited the service information
Modification date and timeDate and time the service information was modified
Image versionInstalled Redis/Valkey image and version information
  • If a Minor version upgrade is required, click the Edit icon to configure
Cluster nameCluster name of the configured Redis/Valkey servers
Planned ComputeResource status with Planned Compute configured
Maintenance periodDB patch work period setting status
  • If you need to set the maintenance period, click the Edit icon to configure
ServiceWatch log collectionServiceWatch Log Collection Configuration Status
  • If log collection configuration is required, click the Edit icon next to Log Collection to configure
BackupBackup Configuration Status
  • If backup configuration is required, click the Edit icon to set it
Redis/Valkey Port numberPort number required for connecting to Redis/Valkey
Time zoneRedis/Valkey time zone
Sentinel Port numberPort number for communication between Master and Replica
VIPVirtual IP information
  • can be checked only when high availability is configured
NetworkNetwork information (VPC, Subnet) where CacheStore (DBaaS) is installed
IP access controlService access policy settings
  • If you need to add or delete IPs, click the Edit icon to configure
Master & ReplicaMaster, Replica server type, default OS, additional Disk information
  • If you need to modify the server type, click the Edit icon next to the server type to configure
  • Modifying the server type requires a server reboot
  • Changes to the specifications may require software license updates or software configuration adjustments, which need to be verified separately
SentinelSentinel server type, basic OS information
  • When configuring HA, it is possible to verify when selecting one Replica
Table. CacheStore (DBaaS) Database detailed information items

tag

CacheStore(DBaaS) List page lets you view the tag information of the selected resource, and you can add, modify, or delete it.

Detailed description
Tag listTag list
  • You can view the Key and Value information of the tag
  • Up to 50 tags can be added per resource
  • When entering a tag, you can search and select from the existing list of created Keys and Values
Table. CacheStore (DBaaS) tag tab item

Job History

CacheStore(DBaaS) List page allows you to view the operation history of the selected resource.

Detailed description
Task: 1. Open the file, 2. Read the data, 3. Close the file.Resource Change History
  • You can view the operation timestamp, resource ID, resource name, operation details, event topic, operation result, and operator information
  • To perform an advanced search, click the Advanced Search button
Table. CacheStore (DBaaS) Operation History Tab Detailed Information Items

CacheStore(DBaaS) Managing Resources

If you need to change or restore the existing configuration options of a created CacheStore (DBaaS) resource, or modify commands, you can perform the work on the CacheStore(DBaaS) Details page.

Operation Control

If changes occur to a running CacheStore (DBaaS) resource, you can start, stop, or restart it. Also, when HA is configured, you can switch the Master-Replica servers via a switch‑over.

To control the operation of CacheStore(DBaaS), follow these steps.

  1. All Services > Database > CacheStore(DBaaS) Click the menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
  2. On the Service Home page, click the CacheStore(DBaaS) menu. 2. CacheStore(DBaaS) List Navigate to the page.
  3. On the CacheStore(DBaaS) List page, click the resource you want to control. 3. Go to the CacheStore(DBaaS) Details page.
  4. Check the CacheStore status and complete the change using the control button below.
    • Start: the server where the CacheStore service is installed and the CacheStore service is running (Running).
    • Stop: The server on which the CacheStore service is installed and the CacheStore service can be stopped (Stopped).
    • Restart: Only the CacheStore service can be restarted.
    • Switch Over: You can switch the Master server and the Replica server.

Synchronize service status

You can synchronize the real-time service status of CacheStore(DBaaS).

To view the service status of CacheStore (DBaaS), follow the steps below.

  1. All Services > Database > CacheStore(DBaaS) Click the menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
  2. On the Service Home page, click the CacheStore(DBaaS) menu. 2. Navigate to the CacheStore(DBaaS) List page.
  3. CacheStore(DBaaS) List page, click the resource to view the service status. 3. Navigate to the CacheStore(DBaaS) Details page.
  4. Click the Service status synchronization button. 4. While it is being queried, the cluster changes to Synchronizing state.
  5. When the query completes, the status in the server information item is updated, and the cluster changes to Running status.

Change Server Type

You can change the configured server type.

Caution
If you modify the server type, a server restart is required. Please verify separately any software license modifications or software settings and their implementation due to server specification changes.

To change the server type, follow these steps.

  1. All Services > Database > CacheStore(DBaaS) Click the menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
  2. On the Service Home page, click the CacheStore(DBaaS) menu. 2. CacheStore(DBaaS) List Navigate to the page.
  3. On the CacheStore(DBaaS) List page, click the resource to change the server type. 3. CacheStore(DBaaS) Details Go to the page.
  4. Click the Edit icon of the server type you want to change at the bottom of the detailed information. 4. Edit Server Type The popup window opens.
  5. Server Type Edit In the popup window, after selecting the server type, click the Confirm button.

Cancel CacheStore(DBaaS)

You can reduce operating costs by terminating unused CacheStore (DBaaS). However, if you terminate the service, the running service may be discontinued immediately, so you should proceed with the termination only after fully considering the impact of the service interruption.

To cancel CacheStore (DBaaS), follow the steps below.

  1. All Services > Database > CacheStore(DBaaS) Click the menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
  2. On the Service Home page, click the CacheStore(DBaaS) menu. 2. Go to the CacheStore(DBaaS) List page.
  3. On the CacheStore(DBaaS) List page, select the resource to cancel, and click the Cancel Service button.
  4. When the termination is complete, verify on the CacheStore(DBaaS) list page whether the resource has been terminated.

2.1 - Managing the CacheStore Service

Users can manage CacheStore (DBaaS) through the Samsung Cloud Platform Console.

Parameter Management

Provides a feature that allows you to easily view and modify database configuration parameters.

View Parameters

To view configuration parameters, follow these steps.

  1. Click the All Services > Database > CacheStore(DBaaS) menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
  2. On the Service Home page, click the CacheStore(DBaaS) menu. 2. Go to the CacheStore(DBaaS) List page.
  3. On the CacheStore(DBaaS) List page, click the resource whose parameters you want to view or modify. 3. CacheStore(DBaaS) Details Go to the page.
  4. Click the More button, then click the Parameter Management button. 4. Parameter Management The popup window opens.
  5. Parameter Management In the popup window, click the Search button. 5. Lookup notification popup opens.
  6. When the View Notification popup opens, click the Confirm button. 6. Retrieving may take a short amount of time.

Edit Parameter

To modify the configuration parameters, follow the steps below.

  1. All Services > Database > CacheStore(DBaaS) Click the menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
  2. On the Service Home page, click the CacheStore(DBaaS) menu. 2. CacheStore(DBaaS) List Navigate to the page.
  3. On the CacheStore(DBaaS) List page, click the resource whose parameters you want to view or modify. 3. Go to the CacheStore(DBaaS) Details page.
  4. Click the More button, then click the Parameter management button. 4. Parameter Management The popup window opens.
  5. Parameter Management In the popup window, click the Search button. 5. View Notification The popup window opens.
  6. When the View Notification popup appears, click the Confirm button. 6. Retrieving may take a short amount of time.
  7. If editing is required, click the Edit button and enter the changes in the custom value field of the Parameter to be edited.
  8. When the input is complete, click the Complete button.

Rename Command

Caution
When applying the Rename-Command, the service will be interrupted due to a CacheStore (DBaaS) restart.

Provides Redis OSS/Valkey command lookup and command name editing functionality. To view commands and rename a command, follow these steps.

  1. All Services > Database > CacheStore(DBaaS) Click the menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
  2. Click the CacheStore(DBaaS) menu on the Service Home page. 2. Go to the CacheStore(DBaaS) List page.
  3. CacheStore(DBaaS) List On the page, click the resource to edit the Command name. 3. CacheStore(DBaaS) Details Go to the page.
  4. Click the More button and then click the Rename-Command button. 4. Rename-Command go to the page.
  5. On the Rename-Command page, click the Search button. 5. lookup notification popup opens.
  6. When the View Notification popup appears, click the Confirm button. 6. Retrieving may take a short amount of time.
  7. If you need to make changes, click the Edit button and enter the modifications in the custom value field of the Command you wish to edit.
  8. When the input is complete, click the Done button.

Minor version upgrade

Provides version upgrade functionality resulting from feature enhancements and security patches. Only minor version upgrades are supported within the same major version.

Caution
First retrieve the service status via service status synchronization, then proceed with the version upgrade.

To upgrade the Minor version, follow these steps.

  1. All Services > Database > CacheStore(DBaaS) Click the menu. 1. Go to the Service Home page of CacheStore (DBaaS).
  2. On the Service Home page, click the CacheStore(DBaaS) menu. 2. CacheStore(DBaaS) List Navigate to the page.
  3. CacheStore(DBaaS) List page, click the resource to upgrade the version. 3. CacheStore(DBaaS) Details Go to the page.
  4. Click the Edit icon of the Image version item. 4. Version Upgrade A popup window opens.
  5. In the Version Upgrade popup, after selecting the updated version, click the Confirm button.
  6. Version Upgrade Notification in the popup window, click the Confirm button.

2.2 - Backing up and restoring CacheStore

Users can configure backups for CacheStore (DBaaS) via the Samsung Cloud Platform Console and restore using the backed‑up files.

CacheStore(DBaaS) Backup

CacheStore(DBaaS) provides a data backup feature based on its own backup commands. Additionally, it provides an optimized backup environment for data protection and management through backup history verification and backup file deletion features.

Configure Backup

For backup configuration of CacheStore(DBaaS), refer to CacheStore(DBaaS) 생성하기.

To modify the backup settings of a created resource, follow these steps.

Caution

If a backup is configured, it runs at the specified time after the set time, and additional fees are incurred based on the backup size.

  • If you change the backup setting to Unset, backup execution will stop immediately, and the stored backup data will be deleted and can no longer be used.
  1. All Services > Database > CacheStore(DBaaS) Click the menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
  2. On the Service Home page, click the CacheStore(DBaaS) menu. 2. Navigate to the CacheStore(DBaaS) List page.
  3. CacheStore(DBaaS) List on the page, click the resource to configure backup. 3. Go to the CacheStore(DBaaS) Details page.
  4. Click the Edit icon of the backup item. 4. Backup Settings The popup window opens.
  5. When configuring a backup, click Use in the Backup Settings popup, select the retention period, backup start time, and Archive backup interval, then click the Confirm button.
    • If you stop the backup setting, uncheck Use in the Backup Setting popup window and click the Confirm button.

Check backup history

안내
To set notifications for backup success and failure, you can configure them through the Notification Manager product. For a detailed usage guide on configuring notification policies, see 알림 정책 생성하기.

To check the backup history, follow these steps.

  1. Click the All Services > Database > CacheStore(DBaaS) menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
  2. On the Service Home page, click the CacheStore(DBaaS) menu. 2. Navigate to the CacheStore(DBaaS) List page.
  3. CacheStore(DBaaS) List page, click the resource to view the backup history. 3. CacheStore(DBaaS) Details Go to the page.
  4. Click the Backup History button. 4. Backup History The popup window opens.
  5. Backup History In the popup window, you can view the backup status, version, backup start time, backup completion time, and size.

Delete backup file

To delete the backup history, follow these steps.

Caution
Backup files cannot be restored after deletion. Please be sure to confirm that the data is unnecessary before deleting it.
  1. Click the All Services > Database > CacheStore(DBaaS) menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
  2. On the Service Home page, click the CacheStore(DBaaS) menu. 2. Go to the CacheStore(DBaaS) List page.
  3. CacheStore(DBaaS) List page, click the resource to view the backup history. 3. CacheStore(DBaaS) Details Go to the page.
  4. Click the Backup History button. 4. Backup History The popup window opens.
  5. Backup History popup, after checking the file you want to delete, click the Delete button.

Recover CachStore(DBaaS)

If a failure or data loss requires restoration from a backup file, recovery can be performed based on a specific point in time using the recovery feature.

To restore CacheStore (DBaaS), follow these steps.

  1. All Services > Database > CacheStore(DBaaS) Click the menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
  2. On the Service Home page, click the CacheStore(DBaaS) menu. 2. CacheStore(DBaaS) List Navigate to the page.
  3. On the CacheStore(DBaaS) List page, click the resource you want to recover. 3. CacheStore(DBaaS) Details Navigate to the page.
  4. Click the Database Recovery button. 4. Go to the Database Recovery page.
  5. After entering information in the Database recovery configuration area, click the Complete button.
    required status
    Detailed description
    Recovery typeRequiredSet the point in time the user wants to recover
    • Recover based on the backup file, and select from the list of timestamps displayed for the backup file
    Server name prefixRequiredRecovery DB server name
    • Start with a lowercase English letter and use lowercase letters, numbers, and special characters (-) to enter 3 to 16 characters
    • A postfix such as 001, 002 is appended based on the server name to generate the actual server name
    Cluster nameRequiredCluster name of the recovery DB
    • Enter using English letters, 3 ~ 20 characters
    • A cluster is a unit that groups multiple servers
    Service Type > Server TypeRequiredServer type where the recovery DB will be installed
    • Standard: Standard specifications commonly used
    • High Capacity: Large-capacity server with 24vCore or more (to be provided later)
    Service Type > Planned ComputeSelectionStatus of resources with Planned Compute set
    • In Use: Number of resources with Planned Compute set that are currently in use
    • Configured: Number of resources with Planned Compute set
    • Coverage Preview: Amount applied per resource by Planned Compute
    Service Type > Block StorageRequiredBlock Storage settings used by the recovery DB
    • Basic OS: The area where the DB engine is installed
    • DATA: The area where AOF (Append Only File) and RDB (Redis Database) files, etc., are stored
      • Apply the same Storage type as set in the original cluster
      • Capacity can be entered in multiples of 8 within the range 56–5,120
    Redis/Valkey Port numberRequiredRedis/Valkey port number configured in the source DB
    IP access controlSelectionService Access Policy Configuration
    • Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy.
    • Enter in jIP format (example: 192.168.10.1) or CIDR format (example: 192.168.10.0/24, 192.168.10.1/32) and click the Add button
    • To delete an entered IP, click the x button next to the IP
    Maintenance periodSelectionCacheStore(DBaaS) DB maintenance period
    • If you select Use, you can set the day, start time, and duration
    • The maintenance period is a feature that allows the user to set the time window for performing patch operations, and any patch work within that window is performed directly by the user.
    • We ask you to set a maintenance period for the stable operation of the system; we are not responsible for any issues arising from not setting it or from failure to perform tasks within the period.
    tagSelectionAdd Tag
    • Add Tag after clicking the button, enter or select Key, Value
    Table. CacheStore (DBaaS) recovery configuration items

2.3 - CacheStore(DBaaS) server connection

Scenario Overview

Connecting to CacheStore(DBaaS) The scenario creates a Bastion host (Virtual Server) and a Database service, and accesses the DB service through the Bastion host. To reliably access CacheStore (DBaaS) in the Samsung Cloud Platform environment, you need to create a Bastion host and establish a network connection using it. To maintain stability and a high level of security, we recommend configuring the Database service in a Private Subnet environment and setting up the Bastion host in a restricted Public Subnet environment.

This scenario primarily describes creating a Bastion host and Database service, configuring the network environment for Bastion host and Database access, and connecting through a DB client.

Architecture
Figure. CacheStore(DBaaS) server connection architecture

Scenario components

You can build the scenario using the following services.

Service group
service
Detailed description
NetworkingVPCA service that provides an isolated virtual network in a cloud environment
NetworkingVPC > SubnetA service that lets users segment the network within a VPC to match their purpose and scale
NetworkingVPC > Public IPA service that reserves a public IP and allocates and releases it to Compute resources.
NetworkingVPC > Internet GatewayA service that connects VPC resources to the Internet
NetworkingSecurity GroupVirtual firewall that controls server traffic
DatabaseCacheStore(DBaaS)A service that easily creates and manages CacheStore in a web environment
ComputeVirtual ServerVirtual server optimized for cloud computing
ComputeVirtual Server > KeypairEncryption file used to connect to the Virtual Server
Table. Scenario component list
Reference
  • Since the default policy of the Security Group is Deny All, you must register only the allowed IPs.
  • The In/Outbound All Open(Any IP, Any Port) policy can expose cloud resources directly to external threats.
    • By specifying the required IP and Port and setting a policy, you can strengthen security.

Scenario setup method

Create the services needed to build the scenario by following the procedure below.

1. ## Configure Network

Explains the process of configuring the network environment for accessing the Bastion Host and Database services.

1-1. ### Create VPC

For detailed creation instructions, refer to the Networking > VPC > How-to guides guide.
  1. All Services > Networking > VPC Click the menu. 1. Navigate to the VPC’s Service Home page.
  2. On the Service Home page, click the Create VPC button. 2. Navigate to the Create VPC page.
  3. On the VPC creation page, enter the information required to create the service.
    • Enter the IP range as 192.168.x.0/16.
  4. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • When creation is complete, check the created resources on the VPC List page.

1-2. ### Create Subnet

For detailed creation steps, refer to the Networking > VPC > How-to guides > Subnet guide.
  1. All Services > Networking > VPC Click the menu. 1. Navigate to the VPC’s Service Home page.
  2. On the Service Home page, click the Subnet menu. 2. Navigate to the Subnet list page.
  3. Create Subnet Click the button. 3. Go to the Subnet Creation page.
  4. On the Subnet Creation page, enter the information required to create the service.
    • Select the Subnet type as General.
    • Select a pre‑created VPC.
    • Enter the IP range as 192.168.x.0/24.
  5. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • After creation is complete, check the created resources on the Subnet List page.

1-3. ### Create Internet Gateway

For detailed creation instructions, refer to the Networking > VPC > How-to guides > Internet Gateway guide.
  1. All Services > Networking > VPC Click the menu. 1. Navigate to the VPC’s Service Home page.
  2. On the Service Home page, click the Internet Gateway menu. 2. Internet Gateway List Navigate to the page.
  3. Internet Gateway creation Click the button. 3. Navigate to the Create Internet Gateway page.
  4. On the Internet Gateway Creation page, enter the required information needed to create the service.
    • Select a pre‑created VPC.
    • In the Firewall usage option, select Use.
  5. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • Once creation is complete, check the created resource on the Internet Gateway List page.

1-4. ### Create Public IP

For detailed creation instructions, refer to the Networking > VPC > How-to guides > Public IP guide.
  1. All Services > Networking > VPC Click the menu. 1. Navigate to the VPC’s Service Home page.
  2. On the Service Home page, click the Public IP menu. 2. Go to the Public IP List page.
  3. Public IP reservation Click the button. 3. Go to the Public IP reservation page.
  4. On the Public IP reservation page, enter the required information for service reservation.
  5. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • After creation is complete, check the created resources on the Public IP List page.

1-5. ### Create Security Group

For detailed creation instructions, refer to the Networking > Security Group > How-to guides guide.
  1. Click the All Services > Networking > Security Group menu. 1. Go to the Service Home page of the Security Group.
  2. On the Service Home page, click the Create Security Group button. 2. Go to the Security Group Creation page.
  3. On the Security Group creation page, enter the required information to create the service.
  4. Check the input information and click the Done button.
    • After creation is complete, verify the created resources on the Security Group List page.

2. ## Create Bastion host

Explains the process of configuring a Bastion Host that requires the Database access client to be installed.

2-1. ### Create Server Keypair

For detailed creation instructions, see the Compute > Virtual Server > How-to guides > Keypair guide.
  1. All Services > Compute > Virtual Server Click the menu. 1. Navigate to the Service Home page of the Virtual Server.
  2. On the Service Home page, click the Keypair menu. 2. Go to the Keypair List page.
  3. Create Keypair button, click it. 3. Go to the Keypair creation page.
  4. On the Keypair Creation page, enter the required information needed to create the service.
  5. Verify the creation information and click the Complete button.
    • The key can be downloaded only for the first time, and reissuance is not provided.
    • Please store the downloaded key in a secure location.

2-2. ### Create Bastion host

For detailed creation steps, please refer to the Compute > Virtual Server > How-to guides guide.
  1. Click the All Services > Compute > Virtual Server menu. 1. Navigate to the Service Home page of the Virtual Server.
  2. On the Service Home page, click the Create Virtual Server button. 2. Go to the Create Virtual Server page.
  3. On the Virtual Server Creation page, enter the required essential information needed to create the service.
  4. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • When creation is complete, check the created resources on the Virtual Server list page.

2-3. ### Check Bastion host login ID and PW

  1. All Services > Compute > Virtual Server Click the menu. 1. Navigate to the Service Home page of the Virtual Server.
  2. On the Service Home page, click the Virtual Server menu. 2. Go to the Virtual Server List page.
  3. Virtual Serve List page, click the resource you created in 2-2. Bastion host 생성하기. 3. Go to the detailed information page for the resource.
  4. Click the RDP password view button in the Keypair name field on the detail information page. 4. RDP password lookup A popup window opens.
  5. RDP password lookup popup window, attach the keypair file downloaded from 2-1. 서버 Keypair 생성하기.
  6. After attaching, click the Password verification button. 6. The ID and password required to access the resource are displayed.

3. ## Create Database

Describes the process of creating a Database service.

3-1. ### CacheStore(DBaaS) Create Service

For detailed creation instructions, refer to the Database > CacheStore(DBaaS) > How-to guides guide.
  1. All Services > Database > CacheStore(DBaaS) Click the menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
  2. On the Service Home page, click the Create CacheStore (DBaaS) button. 2. Create CacheStore(DBaaS) Navigate to the page.
  3. On the Create CacheStore (DBaaS) page, enter the required information to create the service.
    • Select the pre‑created VPC and Subnet and connect them.
    • Enter database-related creation information on the required information input screen.
    • Add the Bastion host IP in the IP access control item.
    • The database port defaults to 2866, but users can also specify a different one.
  4. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • After creation is complete, check the created resource on the CacheStore(DBaaS) list page.

4. ## Configure Rules

Describes the process of setting rules for a user to connect to the Bastion host and rules for connecting to the Database from the Bastion host.

4-1. ### Security Group Add security rule

For detailed creation instructions, see the Networking > Security Group > How-to guides guide.
  1. Click the All Services > Networking > Security Group menu. 1. Go to the Service Home page of the Security Group.
  2. On the Service Home page, click the Security Group menu. 2. Navigate to the Security Group List page.
  3. **1-5. 3. Select the Security Group resource created in Security Group Create. 3. Go to the detailed information page for the resource.
  4. On the detail information page, click the Rules tab. 4. Go to the Rules tab.
  5. Click the Add Rule button on the Rule tab. 5. Add Rule Navigate to the popup window.
  6. Add Rule In the popup window, enter the rule below, and click the Confirm button.
    DirectionRemoteTarget addressProtocolPortExplanation
    InboundCIDRUser PC IPTCP3389 (RDP)Bastion access PC → Bastion host
    OutboundCIDRDB IPTCPDatabase Port (manual entry)Bastion host → Database
    Table. Security Group rules that need to be added

4-2. ### Add IGW Firewall rule

For detailed creation instructions, refer to the Networking > Firewall > How-to guides guide.
  1. Click the All Services > Networking > Firewall menu. 1. Navigate to the Firewall’s Service Home page.
  2. On the Service Home page, click the Firewall menu. 2. Go to the Firewall List page.
  3. On the Firewall List page, select the Internet Gateway resource name created in 1-3. Internet Gateway 생성하기. 3. Go to the detailed information page for the resource.
  4. On the detail information page, click the Rules tab. 4. Go to the Rules tab.
  5. Click the Add Rule button on the Rule tab. 5. Add Rule Navigate to the popup window.
  6. Add Rule In the popup window, enter the rule below, and click the Confirm button.
    Origin addressDestination addressProtocolPortOperationDirectionExplanation
    Bastion connection PC IPBastion host IPTCP3389(RDP)AllowInboundUser PC → Bastion host
    Table. Internet Gateway Firewall rules to be added

5. ## Database Connect

Describes the process of a user connecting to a database through a DB client program.

This guide explains how to connect using Another Redis Desktop Manager. Database client programs and CLI utilities are diverse, so you can install and use the tool that best suits your needs.

5-1. ### Connecting to Bastion host

  1. In the Windows environment of the PC that will connect to the Bastion host, run Remote Desktop Connection, then enter the NAT IP of the Bastion Host and click the Connect button.
  2. When the remote desktop connection succeeds, user credential input window opens. 2. Enter the ID and Password verified in 2-3. Bastion host 접속 ID 및 PW 확인하기 and click the Confirm button.

5-2. ### Install the DB access client program (Another Redis Desktop Manager) on the Bastion host

  1. Download the Another Redis Desktop Manager program.
  2. Connect the user’s PC hard drive to upload the file to the Bastion host.
  3. Click the Details button of the Local devices and resources item on the Local Resources tab of the Remote Desktop Connection.
  4. Select the local disk of the location where the file was downloaded on the drive, and click the Confirm button.
  5. Copy the downloaded file, upload it to the Bastion Host, and click the pgAdmin installer to install it.

5-3. ### Connect to the database using the DB client program (Another Redis Desktop Manager)

  1. Run Another Redis Desktop Manager and click New Connection. 1. New Connection A popup window appears.
  2. In the New Connection popup, enter the Database server information created in 3-1. CacheStore(DBaaS) 서비스 생성하기 and click the OK button.
    Required input element iteminput value
    HostDatabase server IP
    PortDatabase Port
    PasswordDatabase password
    Connection NameCustom (ex. service name)
    Table DB connection client program input fields
  3. After connecting, you can check basic Redis information, manage data, and perform CRUD operations on keys.

3 - API Reference

API Reference

4 - CLI Reference

CLI Reference

5 - Release Note

CacheStore(DBaaS)

2026.07.16
FEATURE ServiceWatch service integration and addition of third-generation server type
  • ServiceWatch service integration
    • You can view CPU, memory, and DB performance monitoring information through the ServiceWatch service.
  • Add third-generation server type
2026.03.19
FEATURE Add minor version upgrade feature
  • Provides stable service continuity through the minor version upgrade feature.
2025.07.01
FEATURE User (access control) management, add DB Audit Log export feature, provide backup notification feature
  • Add CacheStore (DBaaS) feature
    • CacheStore(DBaaS) Add New Image
      • Open-source Valkey image support, developed by forking Redis OSS
    • Add 2nd-generation server type
      • Add a 2nd‑generation (db2) server type based on the Intel 4th‑generation (Sapphire Rapids) Processor. * For more details, see CacheStore(DBaaS) 서버 타입.
    • Backup Notification Feature provided
    • Add HDD, HDD_KMS type to the Block Storage type
2025.02.27
FEATURE Common feature change
  • Samsung Cloud Platform Common Feature Change
    • Account, IAM, Service Home, tags, and other common CX changes have been applied.
2024.10.01
NEW CacheStore(DBaaS) service official version release
  • Change the service name to CacheStore(DBaaS).
  • A volume-encrypted storage selection option has been added to the Block Storage type.
  • The Role Switch (Active ↔ Standby) feature for the Active DB and Standby DB configured with redundancy has been added.
  • By integrating with the monitoring services provided by the cloud, you can visualize CPU usage, memory usage, disk I/O, and network traffic in real time, set alerts, and when thresholds are exceeded, trigger auto-scaling or automatically collect·analyze·forward logs for troubleshooting through a unified monitoring pipeline. Additionally, by linking security logs and audit logs to a centralized log management system, you strengthen compliance and security monitoring, and by providing performance and capacity monitoring for databases and storage, you support resource optimization and cost reduction. Such unified monitoring enhances system availability, improves operational efficiency, and ensures business continuity.
  • Depending on the server type selected by the customer, Planned Compute policy can be configured.
2024.07.02
NEW Beta version release
  • A Redis (DBaaS) service that enables easy creation and management of Redis OSS in a web environment has been launched.