• When a server is deleted, the schedule of the associated backup is removed, but the backup itself remains intact and can be restored and utilized.

• Samsung Cloud Platform Sovereign will be offered after November 2026.

• If the OS disk size is 500 GB or larger, you cannot create a shared Image.

• Since the AIOS service has been discontinued, the AIOS integrated service (LLM Endpoint) has been removed from Virtual Server.

• Standard Image has been added. * (Window server 2016)

• When creating Block Storage, you can select the SSD_Provisioned disk type.
• You can set the maximum IOPS and Throughput.

• Standard Image has been added. * (Alma Linux 9.6, Oracle Linux 9.6, RHEL 9.6, Rocky Linux 9.6)

• Partition(Virtual Server and Block Storage distributed placement) policy has been added.

• When the server name is changed, the OS hostname remains unchanged, and only the information within the Samsung Cloud Platform Console is updated.

• You can monitor data through the ServiceWatch service.

• IP, Public NAT IP, Private NAT IP configuration feature has been added.
• An LLM Endpoint is provided for LLM usage.
• When creating a Virtual Server, you can select an OS Image subscribed from the Marketplace.
• The second-generation server type has been added.
  • Add a 2nd-generation (s2) server type based on the Intel 4th-generation (Sapphire Rapids) Processor. * For detailed information, see Virtual Server 서버 타입.

• qcow2 Image or shared Image can be newly created and shared.

• The NAT configuration feature has been added to Virtual Server.
• Additional OS Image provision
  • Standard Image has been added. * (Alma Linux 8.10, Alma Linux 9.4, Oracle Linux 8.10, Oracle Linux 9.4, RHEL 8.10, RHEL 9.4, Rocky Linux 8.10, Rocky Linux 9.4, Ubuntu 24.04)
  • An image for Kubernetes has been added. * You can create a Kubernetes Engine using an image for Kubernetes.
• Add second-generation server type
  • Add 2nd-generation (h2) server type based on Intel 4th-generation (Sapphire Rapids) Processor. * For detailed information, see Virtual Server 서버 타입.

• Account, IAM, and Service Home, tags, etc., have been updated to reflect common CX changes.

• When the server name is changed, the OS hostname remains unchanged, and only the information within the Samsung Cloud Platform Console is updated.

• You can monitor data through the ServiceWatch service.

• IP, Public NAT IP, Private NAT IP configuration feature has been added.
• An LLM Endpoint is provided for LLM usage.
• When creating a Virtual Server, you can select an OS Image subscribed from the Marketplace.
• The second-generation server type has been added.
  • Add a 2nd‑generation (s2) server type based on the Intel 4th‑generation (Sapphire Rapids) Processor. * For detailed information, see Virtual Server 서버 타입.

• qcow2 Image or shared Image can be newly created and shared.

• The NAT configuration feature has been added to Virtual Server.
• Additional OS Image provision
  • Standard Image has been added. * (Alma Linux 8.10, Alma Linux 9.4, Oracle Linux 8.10, Oracle Linux 9.4, RHEL 8.10, RHEL 9.4, Rocky Linux 8.10, Rocky Linux 9.4, Ubuntu 24.04)
  • An image for Kubernetes has been added. * You can create a Kubernetes Engine using an image for Kubernetes.
• Add second-generation server type
  • Add 2nd-generation (h2) server type based on Intel 4th-generation (Sapphire Rapids) Processor. * For detailed information, see Virtual Server 서버 타입.

• Account, IAM, and Service Home, tags, etc., have been updated to reflect common CX changes.

• Check the status of Virtual Server and Load Balancer and automatically replace servers that are in an Unhealthy state.

• When creating a Launch Configuration, you can attach up to five File Storage Volumes.

• When a Virtual Server is terminated, the Load Balancer is automatically detached.
• The desired number of servers remains unchanged, and scale-out is performed according to the desired check batch.

• You can add notification settings in the creation or detail screen of an Auto-Scaling Group.

• Additional: Memory Usage, Network In(bytes), Network Out(bytes), Network In(Packets), Network Out(Packets)

• It will be released in conjunction with the Load Balancer service launching in February 2025.
• NAT configuration functionality has been added to Auto-Scaling Group.

• Account, IAM, Service Home, tags, etc., have been updated to reflect common CX changes.

• You can select and use an OS image for the NPU.

• For detailed specifications, refer to 서버 타입.

• When a server is deleted, the schedule of the associated backup is removed, but the backup itself remains intact and can be restored and utilized.

• When creating a GPU server, you can select the Kubernetes image (Ubuntu).

• When creating Block Storage, you can select the SSD_Provisioned disk type.
• You can set the maximum IOPS and Throughput.

• You can monitor data through the ServiceWatch service.

• You can create a keypair for use or retrieve a public key and apply it.

• IP, Public NAT IP, Private NAT IP configuration feature has been added.
• An LLM Endpoint is provided for LLM usage.

• You can create a new Image for sharing.

• Using Multi-instance GPU on GPU Server and Using NVSwitch on GPU Server added the guides.

• NAT configuration functionality has been added to the GPU Server.

• Account, IAM, and Service Home, tags, etc., have been updated to reflect common CX changes.

• Through the CPU setting options, you can activate only the desired number of CPU cores and adjust the number of threads per core.
• Even if you change the number of cores, the usage fee remains the same.

• When creating two or more servers, you can automatically generate names in the format server name + creation number.

• Bare Metal Server s4 and h4 server types have been added.
• Detailed information about the s4/h4 server type can be found in the s3/h3 server type.

• Now you can create and use up to 10 Local disk partitions.

• RHEL 8.10, Ubuntu 24.04

• Distribute servers belonging to the same Placement group across different racks.
• Additional OS images provided (RHEL 9.4, Rocky Linux 8.6, Rocky Linux 9.4)
• Add 3rd‑generation (s3/h3) server type based on Intel 4th‑generation (Sapphire Rapids) Processor. * For detailed information, refer to Bare Metal Server 서버 타입.

• Account, IAM, and Service Home, tags, etc., have been updated to reflect common CX changes.

• It must be a node that uses the same DataSet and Cluster Fabric.

• You can view key performance metrics in real time in Cloud Monitoring.

• We provide a service that offers physical GPU servers without virtualization for large-scale high-performance AI computing.

• When technical support ends, security patches and updates will no longer be applied to that Runtime version.
• Already created functions can be used continuously without any call time limit. * However, we do not guarantee bugs, errors, defects, or vulnerabilities that arise in Runtime versions for which support has ended.
• End of technical support scheduled The Runtime versions are as follows (For the full list of supported Runtime versions, see Rutime)
  • GO: 1.21, 1.23
  • Node.js: 18, 20
  • PHP 8.1
  • Python: 3.9
• Including runtime of additionally excluded functions

• Since the AIOS service has been discontinued, the AIOS integration service has been removed from Cloud Functions.

• Resource-based policies are policies applied directly to the function that permit external access.
• You can use resource-based policies to allow or deny actions on specific resources to specific principals.

• You can integrate Cloud Functions with AIOS to utilize LLMs.

• Through a Private connection (PrivateLink), you can establish internal connections between VPCs and between a VPC and a service on the Samsung Cloud Platform without traversing the Internet.

• You can import and configure a Java Runtime executable archive file (.jar/.zip) in Object Storage.

• It is a serverless computing‑based FaaS (Function as a Service) that lets you easily run function‑style applications without server provisioning.

• When the system is interrupted by various disaster scenarios and risk factors, it can be restored to normal operation in a short time.

• You can view monitoring information such as IOPS, latency, and throughput via the ServiceWatch service.

• To prevent accidentally deleting resources, you must verify the deletion information and enter Delete when deleting to proceed with the deletion operation.

• You can view IOPS, latency, and throughput information in Cloud Monitoring.

• HDD disk types have been added, allowing you to select the added type (HDD, HDD_MultiAttach, HDD_KMS) according to the purpose.

• Account, IAM, Service Home, tags, and other common CX changes have been reflected.

• When SSD_KMS is selected, encryption using KMS (Key Management Service) encryption keys is added.

• You can view monitoring information such as IOPS, Latency, and Throughput through the ServiceWatch service.

• To prevent accidentally deleting resources, you must verify the deletion information and enter Delete when deleting to proceed with the deletion operation.

• Max IOPS: 5,000 ~ 20,000
• Max Throughput: 250 ~ 1,000

• Volume expansion is possible only for the original volume that does not use snapshots.

• IOPS: 3,000 ~ 16,000
• Throughput: 125 ~ 1,000
• There is no separate charge during the preview period (billing is scheduled for the first half of 2026).

• A recovery copy is a separate volume created with the same capacity as the original, and it incurs additional costs.

• You can view IOPS, Latency, and Throughput information in Cloud Monitoring.

• A replication feature that allows Block Storage (BM) volumes to be replicated to another location has been added.
• The Volume Group feature has been added, allowing you to configure up to 16 Block Storage (BM) volumes as a group to create snapshots and replication at a consistent point in time.
• For detailed information, please refer to Block Storage(BM) 개요.

• Account, IAM, and Service Home, tags, etc., have been updated to reflect common CX changes.

• Single-AZ: You can select an Availability Zone.
• Multi-AZ: You can select the Active Zone.

• When using a volume dedicated to the SAP Account, the LIF (storage Mount IP) is automatically transferred when a failover occurs due to a fault.
• It can be used only with a SAP account.

• You can monitor data through the ServiceWatch service.

• SSD disk types have been added, allowing you to select a disk type based on your purpose.
• You can create an identical replica volume at a different location and set the data replication schedule.
• File Storage can be used from external networks via a VPC Endpoint connection.

• Account, IAM, and Service Home, tags, etc., have been updated to reflect common CX changes.

• You can restore from the most recently created snapshot.

• You can apply multiple replication policies by setting their priority.

• You can copy the original file to the target bucket as is, regardless of the replication policy settings.

• You can load a Training Script stored in Object Storage from the Simple AI Training service.

• You can monitor data using the ServiceWatch service.

• You can perform replication to buckets in a different location or the same location, and you can configure multiple replication policies.

• You can copy the desired file within the same bucket and folder.

• You can upload Java Runtime executable files in Cloud Functions.

• Multi-node GPU Cluster, PostgreSQL, MariaDB, MySQL, EPAS, Microsoft SQL Server

• You can download the file using a Presigned URL for the configured duration.

• Object Storage can be used from external networks via a VPC Endpoint connection.

• Account, IAM, Service Home, tags, and other common CX changes have been reflected.

• You can set a prefix to perform archiving on the relevant files.

• You can monitor data using the ServiceWatch service.

• Users can view archived folders or files by version and select the desired version to delete or restore.

• Now you can select one of Virtual Server, GPU Server, or Bare Metal Server.

• In the Backup detail page, you can view the original and replica information in the Clone tab.

• On the Backup detail page, you can download the Backup history, recovery targets, and recovery history list as an Excel file.

• When restoring from an agentless remote backup, you can select the restore location (target server or backup location).

• Agentless-based remote backup: You can back up and recover to a different location from the backup target server.
• Backup Agent feature added: You can back up the filesystem of a Bare Metal Server by configuring the Agent.

• Account, IAM, and Service Home, tags, etc., have been updated to reflect common CX changes.

• Supports Kubernetes v1.35.
• Provides a priority IP assignment feature for node pools.
• A meta area that includes user information has been added to the node pool detail screen, and the overall layout has been improved.
• Additional Block Storage CSI performance metric settings are provided for the node pool.
• Improved to allow deletion of nodes (Virtual Server product) associated with a Backup product.
• We have reflected compatible features according to the Multi-AZ implementation for basic products such as VPC, Storage, VM, and GPU VM.

• Supports Kubernetes v1.34.
• Provides a custom GPU VM image for the node pool.
• Provides EoTS management logic and display functionality for cluster and node pool Kubernetes versions and node pool OS versions.
• Provides an OS selection dropdown feature when upgrading a node pool.
• type: LB L7 listener idle-timeout addition and default session-duration-time change will be improved.
• Terraform does not provide the kubeconfig feature.

• Supports Kubernetes v1.33.
• Provides GPU driver version information on node pool GPU nodes.
• Provides the MNGC node in SR request configuration form.
• We provide the node pool OS’s maximum Block Storage capacity, changed from 1 TB to 12 TB to match the VM product.
• When creating or editing a node pool, we provide enhanced label key validation and add validation for unsupported GPU node pool server groups.

• Supports Kubernetes v1.32.
• Provides advanced node pool configuration features.
• Provides node pool server group (Affinity or Anti-affinity) configuration functionality.
• Provides a user Kubeconfig download feature following the admin Kubeconfig download button.
• When upgrading a node pool, we additionally provide upgrade logic that considers the OS version.
• Provides log collection functionality based on ServiceWatch integration.

• Supports Kubernetes v1.31.
• Provides the cluster’s public endpoint.
• The cluster’s private endpoint access control targets will now include the MNGC (Baremetal) and DevOps Service products.
• Provides node pool label and taint configuration functionality.
• Provides Block Storage CSI and kubectl login plugin functionality.
• The kubeconfig vulnerability has been addressed.

• Provides private endpoint and access control features.
• type: LoadBalancer provides this functionality.

• Supports Kubernetes v1.30.
• Provides the Kubernetes version upgrade feature for clusters and node pools.
• Provides Multi-Security Group functionality.
• Provides the ability to create Custom Image nodes and GPU nodes.

• Account, IAM, Service Home, tags, and other common CX changes have been reflected.

• Improved internal processes related to lifecycle management policies to enhance the convenience of the Image Tag deletion feature.
• We provide a Registry Endpoint‑based (CLI) vulnerability assessment lookup feature by improving internal storage and management methods.

• General-purpose Container Registry related OCI (Open Container Initiative) Distribution Spec. * Ensured v1.1.1 compatibility and improved the user Registry.
• Improved internal processes related to the Container Registry creation/deletion logic to enhance convenience.
• We improved usability by adding a refresh button where needed, just like with other products.

• OCI (Open Container Initiative) Distribution Spec related to Registry. * Ensured v1.1.1 compatibility and improved the user Registry.
• We expand the coverage by adding OS and language types to the container image vulnerability assessment targets.

• We additionally offer the image tag deletion policy feature based on count.
• We improve the validation of Public Endpoint access control IP input values according to the IP range constraints of the Firewall product.

• Provides a feature to enable the deletion policy setting for image tag deletion items.
• Provides log collection functionality based on ServiceWatch integration.

• Provides a Container Registry service based on Object Storage with self‑encryption and the S3 API compatibility issue patch applied.
• Provides public endpoints and access control features for the Registry.
• We additionally offer the Multi-Node GPU Cluster product among the private endpoint access control targets of the Registry.
• Provides a feature to set automatic deletion policies for repositories, stored images, and their individual tags (digests).

• Provides a lock feature for images stored in the Registry.
• Provides monitoring capabilities for the Registry in conjunction with the Cloud Monitoring product.
• Provides integration with VPC Endpoint.

• Account, IAM, and Service Home, tags, etc., have been updated to reflect common CX changes.

• The previously provided Subnet is classified as the Primary Subnet.

• The previously offered General type is changed to Public/Private, and the previously created General type is shown as Public.

• You can add a new IP range to the VPC for use.

• You can reserve a Virtual IP in a Subnet for use.

• You can also use Private NAT with Transit Gateway.

• Easily connect the customer’s network with the Samsung Cloud Platform network and serve as a connection hub for multiple VPCs within the cloud environment.

• You can communicate via IP over a 1:1 private route between VPCs.

• From Compute resources within a VPC, you can use Direct Connect to map the customer’s IP and establish a connection.

• Provides an Endpoint(entry point) that allows access to the Samsung Cloud Platform via a private connection from an external network connected to the VPC.

• Account, IAM, and Service Home, tags, etc., have been updated to reflect common CX changes.

• Improved the console to allow selecting multiple service ports when adding a rule.

• A feature allowing IP protocol input has been added.
• A feature to select Well-known protocols has been added.

• Account, IAM, Service Home, tags, and other common CX changes have been reflected.

• It has been changed to allow creating a Listener on the same service port for both TCP and UDP protocols.

• LB server group forwarding > Updated to allow users to add ‘/’ path in the URL path.
• LB server group forwarding > The matching method for the entered path in the URL path has changed from ‘Contains (including match)’ to ‘Starts with (starting part match)’.
• LB server group forwarding > A ‘Default(Default)’ condition has been added to the request host of the host header.

• You can select between member port and manual entry, and for manual entry, specify the port to use.
• The existing LB health check will be changed to the member port. * (Same as the current health check method)

• You can monitor the server TLS connection status.

• You can configure a TLS service based on TCP.

• Routing conditions allow you to configure branching by URL path or by host.

• By supporting SNI, you can register multiple certificates on a single Listener.

• You can create an LB health check to define the required health check method and attach it to an LB server group for use.

• Weighted Round Robin and Weighted Least Connection have been added to the load balancing options.
• You can set per-member weights to distribute server load.

• You can enable or disable members of the LB server group to select their activation status.

• Number of server error responses (unit: seconds)
• NXDOMAIN response count (unit: seconds)
• Number of queries not responding within 1 second (unit: seconds)
• Number of outgoing UDP queries (unit: seconds)
• Number of UDP-based data request processing (unit: seconds)

• In the KR WEST and KR EAST regions, you can enter the destination address in FQDN (Fully Qualified Domain Name) format.

• A feature to input IP protocols has been added.

• You can use Firewall in the Load Balancer service.

• Account, IAM, Service Home, tags, and other common CX changes have been reflected.

• Account, IAM, Service Home, tags, and other common CX changes have been reflected.

• Account, IAM, Service Home, tags, and other common CX changes have been applied.

• Check Global CDN status
• Check Global CDN processed data volume
  • Data from 30 minutes ago is displayed due to the processing time of external CDN network traffic.

• If additional data protection is needed, you can quickly create a backup using the instant backup feature.
• Through the Disk usage query feature, you can view the usage of each Block Storage type assigned to an instance.

• You can view CPU, memory, and DB performance monitoring information through the ServiceWatch service.

• The third-generation server type has been newly added. * For more details, please refer to the EPAS(DBaaS) 서버 타입.

• 2nd-generation server type addition
  • Add a 2nd‑generation (db2) server type based on the Intel 4th‑generation (Sapphire Rapids) Processor. * For more details, see EPAS(DBaaS) 서버 타입.
• DB user and access control management and Archive configuration feature added
  • For detailed information, refer to DB 사용자 관리, DB 접근 제어 관리, Archive 관리
• Export DB Audit Log feature added
  • For more details, see DB Log 내보내기.
• Backup Notification Feature provided
  • Provides notification functionality for backup success and failure. * For detailed information, refer to 알림 정책 생성하기.
• Migration feature added
  • Provides replication-based zero-downtime data migration functionality. * For more details, see Migration 구성하기.
• Add HDD, HDD_KMS type to the Block Storage type

• If additional data protection is needed, you can quickly create a backup using the instant backup feature.
• Through the Disk usage query feature, you can view the usage of each Block Storage type allocated to an instance.

• You can view CPU, memory, and DB performance monitoring information through the ServiceWatch service.

• The third-generation server type has been newly added. * For detailed information, refer to PostgreSQL(DBaaS) 서버 타입.

• Add 2nd-generation server type
  • Add a 2nd-generation (db2) server type based on Intel 4th-generation (Sapphire Rapids) Processor. * For more details, see PostgreSQL(DBaaS) 서버 타입.
• DB user and access control management and Archive configuration feature added
  • For more details, refer to DB 사용자 관리, DB 접근 제어 관리, Archive 관리.
• Export DB Audit Log feature added
  • For more details, refer to DB Log 내보내기.
• Backup Notification Feature provided
  • Provides notification functionality for backup success and failure. * For more details, refer to 알림 정책 생성하기.
• Migration feature addition
  • Provides replication-based zero-downtime data migration functionality. * For more details, refer to Migration 구성하기
• Add HDD, HDD_KMS type to Block Storage type

• Add new PostgreSQL versions: 13.16, 14.13, 15.8
• Add second-generation server type
  • Add a 2nd-generation (dbh2) server type based on Intel 4th-generation (Sapphire Rapids) Processor. * For detailed information, refer to PostgreSQL(DBaaS) 서버 타입.
• After creating the service, Block Storage capacity expansion is possible.
• Server-specific network IP configuration feature added allows either common or server-specific configuration depending on the usage purpose.

• Account, IAM, Service Home, tags, etc., have been updated to reflect common CX changes.

• If additional data protection is needed, you can quickly create a backup using the instant backup feature.
• Through the Disk usage query feature, you can view the usage of each Block Storage type assigned to an instance.
• Through the Major version upgrade feature, users can perform a Major version upgrade.

• The third-generation server type has been newly added. * Please refer to the MariaDB(DBaaS) 서버 타입 for more details.

• Add 2nd-generation server type
  • Add a second‑generation (db2) server type based on Intel 4th‑generation (Sapphire Rapids) processors. * For more details, refer to the MariaDB(DBaaS) server type.
• DB user and access control management and Archive configuration feature Add
  • For detailed information, refer to DB 사용자 관리, DB 접근 제어 관리, Archive 관리.
• DB Audit Log Export feature added
  • For detailed information, see DB Log 내보내기.
• Backup Notification Feature provided
  • Provides notification functionality for backup success and failure. * For more details, see 알림 정책 생성하기.
• Migration feature addition
  • Provides replication-based zero-downtime data migration functionality. * For more details, refer to Migration 구성하기.
• Add HDD, HDD_KMS type to Block Storage type

• Add second-generation server type
  • Add 2nd-generation (dbh2) server type based on Intel 4th-generation (Sapphire Rapids) Processor. * For more details, refer to MariaDB(DBaaS) 서버 타입.
• After creating the service, you can increase the configured Block Storage capacity.
• Server-specific network IP configuration feature added allows either common or server-specific settings depending on the usage purpose.

• Account, IAM, Service Home, tags, etc., have been updated to reflect common CX changes.

• If additional data protection is needed, you can quickly create a backup using the instant backup feature.
• Through the Disk usage query feature, you can view the usage of each Block Storage type allocated to an instance.
• Through the Major version upgrade feature, users can perform a Major version upgrade.

• The third-generation server type has been newly added. * For more details, please refer to MySQL(DBaaS) 서버 타입.

• Add 2nd-generation server type
  • Add a 2nd-generation (db2) server type based on Intel 4th-generation (Sapphire Rapids) Processor. * For detailed information, refer to MySQL(DBaaS) 서버 타입.
• Add DB user and access control management and Archive configuration feature
  • For more details, refer to DB 사용자 관리, DB 접근 제어 관리, Archive 관리
• Add Export DB Audit Log feature
  • For detailed information, see DB Log 내보내기.
• Backup Notification Feature Provided
  • Provides notification functionality for backup success and failure. * For detailed information, refer to 알림 정책 생성하기.
• Migration feature addition
  • Provides replication-based zero-downtime data migration functionality. * For more details, refer to Migration 구성하기
• Add HDD, HDD_KMS types to Block Storage

• Add second-generation server type
  • Add a 2nd-generation (dbh2) server type based on Intel 4th‑generation (Sapphire Rapids) Processor. * For detailed information, refer to mysql(DBaaS) 서버 타입
• After creating the service, you can expand the configured Block Storage capacity.
• Server-specific network IP configuration feature added allows either common or server-specific settings depending on the usage purpose.

• Common CX changes for Account, IAM, Service Home, tags, and other items have been applied.

• You can configure a disaster recovery Secondary using the Secondary configuration (Other Region) feature.
• Supports integration with the user‑built Active Directory(AD) environment.
• If additional data protection is needed, you can quickly create a backup using the instant backup feature.

• You can view CPU, memory, and DB performance monitoring information through the ServiceWatch service.

• The third-generation server type has been newly added. * For more details, see Microsoft SQL Server(DBaaS) 서버 타입.

• 2nd-generation server type Add
  • Add a 2nd‑generation (db2) server type based on the Intel 4th‑generation (Sapphire Rapids) Processor. * For more details, see Microsoft SQL Server(DBaaS) 서버 타입.
• DB User and Access Control Management Add
  • For more details, refer to DB 사용자 관리, DB 접근 제어 관리
• DB Audit Log Export feature added
  • For more details, see DB Log Export.
• Backup Notification Feature provided
  • Provides notification functionality for backup success and failure. * For more details, refer to 알림 정책 생성하기.
• Add HDD, HDD_KMS type to the Block Storage type

• You can view CPU, memory, and DB performance monitoring information through the ServiceWatch service.

• The third-generation server type has been newly added. * For more details, see CacheStore(DBaaS) 서버 타입.

• 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
  • Provides notification functionality for backup success and failure. * For more details, refer to 알림 정책 생성하기.
• Add HDD, HDD_KMS type to the Block Storage type

• Account, IAM, Service Home, tags, and other common CX changes have been applied.

• Resource-based policies are policies applied directly to the API to allow external access.
• You can use resource-based policies to allow or deny actions on specific resources to specific principals.

• Content-based deduplication: Hash the message body content to remove duplicate messages.
• Duplicate removal scope setting: Set the scope (within the queue / per group) for removing duplicate messages.

• Provides Private Service link ID information.
• Message retention and data key reuse period setting units have been refined, and a CIDR‑based modification feature for allowed IP addresses has been added.

• You can select the resources for API calls and configure access control settings.

• When another product within the Samsung Cloud Platform encrypts using a KMS key, it can encrypt with a platform-managed key generated directly by the CSP without the user having to create a key in KMS.

• You can request a diagnosis using the generated resource and view the specified checklist and version information in the diagnostic results.

• You can register the Account (or other cloud account) to be diagnosed, enabling continuous diagnostics, and view the dashboard and detailed results in the Report.

• Account, IAM, Service Home, tags, and other common CX changes have been reflected.

• You can select a VM resource in Samsung Cloud Platform that stores secret security information and configure access control.

• AI agent registration and configuration features for authentication between the MCP server and MCP client have been added.
• The features for registering information, generating authentication key values, and retrieving information for AI agent authentication have been newly added.

• A TOTP authentication method registration/setting feature has been added to support 3rd Party Authenticators such as Google Authenticator and Microsoft Authenticator in the Admin Portal.
• A feature has been added that allows users to register or delete a 3rd Party TOTP Authenticator in the User Portal and MFA Portal.

• You can register and use the Infobank SMS service, an external SMS service provider.

• When no authentication method is available for identity verification, we have enhanced the system so that the admin authentication delegation feature can be applied when 1) registering an authentication method or 2) attempting to log in.
• You can register a list of authentication delegation administrators in the JWT Token.
• Enhanced to allow the authentication delegation manager list to be registered in SCP Cloud Object Storage and utilized.
• The detailed MFA SP configuration feature has been added in the Admin Portal.
  • Whether to perform delegated authentication at login
  • Whether to perform verification during registration when no authentication method is registered.
  • Use of SCP Cloud Object Storage
  • Select user information update method when running MFA
  • Select whether to automatically add Knox Messenger as an authentication factor when executing MFA.

• Personal information fields (name, email, mobile phone number) are now stored encrypted.
• In admin screens such as TAP, searching personal information fields (name, email, mobile phone number) has been changed from Like to Exact search, and the existing sorting function has been removed.

• When retrieving authentication methods for SingleID Authenticator, a feature to view detailed information (OS version, browser, and IP) has been added.
• The process has been improved so that when SingleID Authenticator information is deleted on the authentication server, the authentication server (tenant) information is also removed from the user app.
• The registration failure error that occurred when registering biometric data in PIN registration mode has been resolved.

• Support CSP for console access control has been expanded from the existing AWS, Azure, Samsung Cloud Platform (KR EAST1 region, KR WEST1 region) to GCP.

• Maintained overall UI/UX consistency of the Admin Portal/User Portal and improved usability.
• We improved it so that when a user accesses the SingleID service via a mobile device’s browser and authenticates, the appropriate mobile keypad (default, password, numeric, email keyboard) is automatically selected based on the attributes of the input data on the authentication screen.
• When creating or editing a SAML-type application, we removed the unnecessary input restriction (Issuer setting).
• Improved the usability and security of the CAM Portal.
  • Added a masking feature for sensitive information (Password, Key).
  • Users assigned the PM/PL role can now modify the IP/Port of registered resources, improving usability.
  • When resource registration fails, we have improved it to provide information about the failure status based on a checklist.
  • When registering resources, it has been improved to allow registering multiple resources at once and to support PEM key registration.
  • After the resource connection expires, we improved usability so that clicking the Rotation button allows you to easily refresh the expired OTP connection information.
  • Improved usability to display the Account ID information when submitting approval for a permission request to access resources.

• You can view and download console access logs.

• Support CSP for console access control has been expanded from the existing AWS to Azure and Samsung Cloud Platform (KR EAST1 region, KR WEST1 region).

• The feature that allows registering and managing notices per tenant has been improved.

• We added a self‑managed approval system feature to the existing approval function based on the Knox approval system.

• The batch scheduler management feature has been enhanced to allow viewing execution results and details, and to enable immediate execution.

• The CAM system has been improved to allow creating, listing, viewing, and detailing user roles for the system itself.

• The system-wide variable management functionality for the CAM system itself has been improved.

• PM/PL authorized users can change the IP of an already enrolled resource (no need to re‑enroll the resource).
• Improved the multi-select functionality when searching User, Role, and Policy (preserves previously added items during multiple selections).
• Improved to allow navigation to the detailed pages for Role/Policy/Account from the Console Access menu.
• The Manual, Release Note, and FAQ URLs have been changed to the SCP Documentation URL.

• A feature has been added that allows delegating identity verification to an administrator. * This feature is available only for MFA products.

• A feature has been added to the dashboard that allows managing users’ approval requests and statuses.

• A feature has been added to the dashboard that allows managing users’ sign‑up status.

• A campaign feature that recommends registering additional authentication methods has been added when only one user authentication method is registered.

• Added features for dormant user settings, alarm dispatch configuration, exception user registration, long-term dormant users, and dormant self-recovery settings.

• During sign-up and user registration, features for setting user defaults, configuring user account expiration periods, and defining approval policies have been added.

• A feature has been added that allows changing the top and bottom logos, key visual images, and text in the Admin Portal.
• Redirection functionality for the sign‑up page settings, bottom privacy policy, terms of service, and similar items has been added.

• Mobile Passkey, security key, and Windows PIN code have been added as convenient authentication methods for easy login.

• A conditional authentication policy feature has been added that requires additional identity verification when only one authentication method is used for an extended period.

• You can further expand and apply the user’s personal information attributes.

• Synchronize application permissions to manage application access for users and groups.

• Improved the process when the authentication session timeout expires.
• Improved the app access process in the mobile app.
• We have improved the screen for mobile app download.
• Improved the application registration/edit screen (field modifications, mapping screen enhancements, etc.).
• Improved the Identity Providers registration/edit screen (added/modified fields)
• Added a user mobile app (device) reset feature.
• Added a feature to set a prefix text when sending SMS.
• Improved the image upload screen and process.

• On the result management screen of the detection guardrail, you can view the diagnostic request result information.

• For accounts within the default organizational unit, Config Inspection diagnostics are run automatically every day.
• You can easily view diagnostic results even within the Cloud Control service.

• You can continuously perform resource monitoring by utilizing the new alternative service, ServiceWatch, which was launched in October 2025. * ServiceWatch provides more modern and powerful features, replacing Cloud Monitoring to deliver a seamless monitoring environment.
  • With the termination of the Cloud Monitoring service, the data and settings you were using are no longer accessible. * Therefore, if you need performance and log data from services integrated with the existing Cloud Monitoring, please download it in advance and store it separately.
  • The existing Cloud Monitoring dashboard should be migrated to the ServiceWatch dashboard, and Cloud Monitoring events should be converted to ServiceWatch alert policies.

• Additional integrated services: Compute(Multi-node GPU Cluster [Cluster Fabric], Multi-node GPU Clutser [Node]), Storage(Block Storage(BM), Block Storage(VM)), Networking(Cloud WAN, Global CDN), Database(Valkey), Data Analytics(Opensearch, Vertica(DBaaS))

• Additional integrated services: Container (Container Registry), Database (EPAS, Microsoft SQL Server), Data Analytics (Event Streams, Search Engine), Networking (Load Balancer, Load Balancer Listener, Load Balancer Server Group, VPN)

• When creating or modifying an IAM user, you can copy and import policies that are attached to another user’s group or directly attached.

• You can manage IAM user access key creation records.
• You can configure the visibility of the AI recommendation floating guide displayed at the bottom of the screen.
• When viewing the IAM user list, you can click the user group to navigate to the detail page.

• When password entry is required, such as changing the password or updating the mobile phone number, you will be automatically logged out after five or more incorrect attempts.

• Users can switch from their own account to a different role to access the Account.

• You can create a credential provider and access the Account resource in the Console through the created credential provider.

• Added user group and user functions, and policy creation functionality.
• We provide a unified authentication key by consolidating the app authentication key and the storage authentication key.

• Implemented common CX changes, including Account, Service Home, and tags.

• Provide user authentication and authorization management.
• Access control policy management provided

• Provide user authentication and authorization management.
• Provides access control policy management

• Client AD Management: Manage passwords in the client AD
• ID Center Management: Users manage passwords directly in the Access Portal

• We have changed the procedure so that the Access Portal URL, which was previously requested through a service request, is now provided together when applying for the ID Center.
• After completing the ID Center application, you can view the Access Portal connection URL on the ID Center settings screen.

• Using AD (Active Directory), users can directly manage credential sources.

• You can create permission policies for each service and assign accounts and policies linked to the Organization service to users, enabling management of tasks according to each user’s permissions.
• You can strengthen security so that only authorized ID Center users can access through the Access Portal.

• Configure the Trail logs to be sent to a ServiceWatch log group, allowing you to monitor them through ServiceWatch and receive alerts when specific activities occur.

• API Gateway, Archive Storage, Backup Agent, Cloud Functions, Cloud LAN-Datacenter, Cloud WAN, CloudML, Cost Savings, GSLB, Global CDN, IAM > role, Load Balancer > LB Health Check, Marketplace, Organization, Private DNS, Private NAT, Public Domain Name, Quick Query, Secret Vault, SingleID, Support Plan, Transit Gateway, VPC Peering, Vertica

• Data Flow, Data Ops

• AI&MLOps Platform, Multi-node GPU Cluster, VPN, Cloud LAN-Campus, KMS, Event Streams, Serch Engine, EPAS, Microsoft SQL Server

• Account, IAM, Service Home, tags, and other common CX changes have been reflected.

• You can register up to 500 external recipient emails.

• Deletable Accounts are limited to those directly created in the Organization.

• Managed: Alarm policies generated by other services such as Auto-Scaling Group
• User: Alert policy created directly by the user

• You can select a specific period to compare when viewing the chart of metric comparison results by date.

• You can enter a specific alarm name (or ID) or view the list of recent alarms.

• We provide a service dashboard composed of key metrics for each service.
• When the service’s resources are created and metric data is collected by ServiceWatch, the service dashboard is automatically generated and can be viewed.

• Improve the indicator search to allow checking results even when the search term is included.
• When searching for an indicator, you can specify a period for a specific indicator to see how the indicator’s data changes over multiple periods.

• You can create a log pattern to filter the log data collected in ServiceWatch that matches the pattern.
• For more details, see the 로그 패턴.

• Collecting custom metrics via ServiceWatch Agent
• Collecting custom metrics via the ServiceWatch API

• Collecting custom metrics via ServiceWatch Agent

• For more details, see 경보 평가 시 누락 데이터 처리 방법.

• Now you can view the Support Plan you are currently using on the Service Home page.

• Depending on the user’s situation, you can select and use the Standard, Proserv Plan tier.

• You can manually request services that cannot be applied through the system from the Console.
• You can ask questions about any issues while using it, and receive technical support if problems arise.

• You can set tags on the Quota Service to use it.

• By using the organization quota template, you can automatically request a quota change when creating a new account in the organization.
• The organization quota template feature is available only in the Management Account.

• You can manage the maximum number of resources, tasks, or items (quotas) set for each service within an account.

• You can apply tags to cost data, enabling you to view and analyze by tag in usage, billing details, and cost analysis.
• By using billing tags, you can categorize and manage costs based on various criteria such as projects, services, departments, and environments.

• KRW: Only integer values can be entered according to each service’s criteria.
• USD: You can enter an integer or a decimal (up to two decimal places) according to each service’s criteria.

• When registering an EDP, you can set discount rates by adding the type of GPU Server, Multi-node GPU Cluster, and the contract term.

• If the usage amount changes by 100% or more compared to the day before yesterday versus yesterday, a notification will be sent.
• Weekends are excluded from the control group.
• New resources are excluded from detection for two weeks.
• The default alarm sender is set to the Root user.
• To add notification policies and notification groups, add [Billing System] Anomlay Detection Notification as a notification in the Samsung Cloud Platform notification settings.

• When creating a budget, you can specify the month when the budget application starts.
• You can set it to limit the creation of new services when the budget consumption rate reaches that point.

• Cost Savings: You can reduce usage costs by setting a time commitment for the Compute services of the Samsung Cloud Platform Console.
• Carbon Emissions: You can view the carbon emissions generated when using services on the Samsung Cloud Platform Console.

• Provides usage and billing details, cost analysis, and Credit management features.
• You can set and manage budgets, and it provides Account and payment method information.

• You can begin applying the agreement from the day after the application date by selecting your preferred date.

• Data Catalog, Vertica(DBaaS)

• When creating a DevOps Service, you can add members who will perform the Admin role.

• We have incorporated common CX changes, such as Account, IAM, Service Home, and tags.

• Manage and authenticate users using DevOps IDP.

• You can verify the installed Jenkins version, the installation status and version information of recommended plugins, and perform installation and updates.

A supported Helm chart repository has been added.

• You can now use the OCI standard Helm chart repository.

The pipeline feature has been added.

• Supports creating multi-branch pipelines.
• Note: Multibranch Pipeline

Other changes

• A new item that can be viewed on the dashboard has been added.

• Deployment target(K8S cluster, namespace, VM server group) now has a permission request/approval feature added.
• Note: Permission Request

• It has been improved to allow the transfer of the organization that manages tools and templates (tenants, project groups).

• The supported versions of the image registry tool Harbor have been expanded. (~2.10)
• It is no longer possible to create a Job directly in Jenkins. (Jobs can only be created through the DevOps Service)

• Kubeflow 1.9