This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Overview

Service Overview

Object Storage is an object storage that allows users to easily store and use the data they want and can be accessed via URL, making data management very convenient. It enables searching and retrieving large-scale data, and you can leverage features such as encryption and version control. Provides public and private URLs, and the public URL can be accessed over the internet.

Features

  • Using S3 API: Through a Restful API, applications can access it easily and quickly, and because it is compatible with Amazon S3, it can be used effortlessly in applications integrated with Amazon S3.
  • Secure Use: Encryption (SSE‑S3), access control, and Public/Private access features are provided, making it suitable for safely storing user data or backup data for service recovery.
  • Cost Efficiency: Users do not predefine the bucket capacity and are provided storage space with an efficient pricing model that charges only for the amount used.
  • Replication: You can perform replication on a bucket in a different location or the same location. * You can configure multiple replication policies, and if the source bucket becomes unavailable due to a failure or disaster, you can provide service through the replica bucket.

Configuration diagram

Diagram
Figure. Object Storage diagram

Provided Features

Object Storage provides the following features.

  • Storage Management: Provides Object Storage creation, folder creation, folder deletion, file upload, file download, and file deletion functions.
  • Version control: When you use version control, all versions of uploaded files are managed. * You can easily download previous files by viewing the version list.
  • Encryption: If you enable encryption, encryption is provided using the SSE‑S3 method.
  • Access Control: Using access control, you can directly enter the public IPs allowed to access Object Storage, or select resources within the same account (Virtual Server, Bare Metal Server, VPC Endpoint, etc.) that are permitted to access it.
  • Replication: You can perform replication to a bucket in a different location or the same location.
    • Multiple replication policies can be configured
  • Permission Management: It is provided with Private permission by default, and offers Public permission and permission management features.
    • Private permission: Allow file access and download only to users who know the authentication key.
    • Public permission: If accessed via the file’s URL, the file is made public and downloadable to anyone worldwide.
  • Monitoring: You can view monitoring information such as total file count, data size (Bytes), and HTTP method request counts through the Cloud Monitoring service.
  • ServiceWatch Service Integration Provision: You can monitor data through the ServiceWatch service.

Component

authentication key

The authentication key is a required element that must be created in advance for using Object Storage.
The purpose of using the authentication key is as follows.

  • In the Samsung Cloud Platform Console, you need an authentication key to create and access the Object Storage service.
  • The API provided by Object Storage is compatible with Amazon S3, and you can use the same tools that leverage Amazon S3. * At this point, entering an authentication key is required, and it is used as a tool to identify whether the user has the appropriate permissions. For detailed instructions on creating and verifying authentication keys, see How-to guides > 인증키 생성하기.

Bucket

A bucket is the top-level folder, and all folders and files exist under the bucket. When you create an Object Storage service in the Samsung Cloud Platform Console, a bucket is created, and you can subsequently upload folders or files.
The bucket name creation rules are as follows.

  • Bucket names must be at least 3 characters and no more than 63 characters.
  • Bucket names can consist only of lowercase English letters, numbers, periods. and hyphens-.
  • Bucket names must start with a lowercase letter or a digit.
  • Bucket names must not contain two consecutive periods.
  • Bucket names cannot end with a period or hyphen.
  • Bucket names cannot have a period and hyphen adjacent to each other.
  • Bucket names do not use the IP address format (e.g., 192.168.x.x).
  • You cannot use admin as a bucket name.
  • The bucket name must be unique within an Account/Region.
  • The bucket name you previously used will be available in 1 hour.
Example of a valid bucket nameExample of an invalid bucket name
The following bucket names can be used
  • cpexamplebucket1
  • scp-example-bucket-01
  • my-scp-object-storage
The following bucket names cannot be used
  • scp_example_bucket(including underscore)
  • DocExampleBucket(including uppercase)
  • -scp-example-bucket(starts with hyphen)

Folder

Folder (Folder) is used to logically group files.
The folder name generation rules are as follows.

  • Folder names can consist of Korean characters, English letters, numbers, and special characters.
  • The special characters that cannot be entered are as follows.
Special characters that cannot be used in folder names
  • percentage sign%
  • ampersand&
  • question mark?
  • exclamation mark!
  • less-than sign<, greater-than sign>
  • slash/
  • equals sign=
  • plus sign+
  • dollar sign$
  • pound sign#
  • apostrophe’
  • caret^
  • vertical bar/pipe\

File

A file (File) refers to data stored in Object Storage and is the same as a regular file.
The filename generation rules are as follows.

  • Filenames can consist of Korean characters, English letters, numbers, and special characters.
  • The special characters that cannot be entered are listed below.
Special characters that cannot be used in file names
  • percentage sign%
  • ampersand&
  • question mark?
  • exclamation mark!
  • less-than sign<, greater-than sign>
  • slash/
  • equals sign=
  • plus sign+
  • dollar sign$
  • pound sign#
  • backslash\
  • apostrophe’
  • caret^
  • vertical bar/pipe\

Folder names and file names are separated by a slash/. The following are examples of valid folder names and file names.

Example of mixed use of folder and file names
  • 3scp-example
  • my.happy_photo-2024/20240101.jpg
  • video/2024/video01.wmv
Reference
The length of the path, including the folder name, file name, and separator (/), must be within 1,024 Bytes (UTF-8 encoding).

URL

You can access the Object Storage bucket via URL. By providing both public and private URLs, access is possible not only within the same Samsung Cloud Platform environment but also from external internet environments.
The URL structure is organized as follows.

URL without an Account IDURL that uses the Account ID
https://[대표URL]/[bucket명]/[폴더명]/[파일명]https://[대표URL]/[accountId]:[bucket명]/[폴더명]/[파일명]
CategoryExplanationExample
Main URLRepresentative URL can be found at the Object Storage 상세 정보 확인하기 URL
  • Representative URL includes the region name.
-
accountIdaccount ID
  • When accessing a file that allows Public Access without an authentication key (Access Key, Secret Key), entering the account ID is required; otherwise, you can connect without an account ID.
c2ef8be0481d4094af3c6d046e536d25
bucket nameUser-created bucket namebucketname
Folder nameFolder name where the file is locatedfolder/folder01/folder02/
filenameFile nameFilename02
Table. Object Storage URL components

The full URL information for the file can be found in 파일 정보 조회하기.

Constraints

The limitations of Object Storage are as follows.

CategoryExplanation
Number of creatable Object Storage servicesUp to 1,000 per region
File name length (including path)up to 1,024 Bytes
File upload size
  • Console: up to 3GB per uploaded file
  • Upload API: Single upload up to 5GB, multipart up to 5TB
Number of files in the bucket200 million or fewer
Table. Object Storage constraints
Caution
  • It is recommended to store up to 200 million files per bucket. * If the number exceeds 200 million, performance may degrade sharply, so manage the file count.
  • S3 Backend Filesystem solution (ex. * When using s3fs, objectivefs, etc., we recommend not employing version control. * Performance degradation may occur when using version control.
Reference
  • After changing IAM permissions, performing an Amazon S3 API call may take up to 30 seconds.
  • Object Storage cannot be used for file upload and download when the IAM policy uses a temporary authentication type.
Reference
Access between Object Storage and SCP resources is supported only through the access control on the Object Storage detail screen.
Please note that when IP access control is used in IAM policies, access between Object Storage and SCP resources is not possible.
To use the service, you must set the IAM policy to ‘Applied IP: All IPs, Excluded IP: Not used’.
Reference
  • South Korea (kr-south3) region constraints
    • File upload and download functions via the Samsung Cloud Platform Console are restricted.
    • Use of the S3 API/CLI via a public URL is restricted.
    • However, accessing a Private URL via resources (e.g., Virtual Server) created in the Samsung Cloud Platform Console is possible.
  • Korea South 1 (kr-south1), Korea South 2 (kr-south2) region constraints

Preliminary Service

Object Storage has no prerequisite services.

1 - Amazon S3 Usage Guide

Object Storage provides functions such as creating services, viewing lists, retrieving folder lists, creating folders, uploading files, and downloading files through the Samsung Cloud Platform Console. These features are also provided via an API compatible with Amazon S3. Therefore, tools that utilize Amazon S3 can be used in the same way.
Using Amazon S3’s utility tools requires generating and verifying an authentication key. For detailed information, please refer to 인증키 생성하기.

Amazon S3 API

The list of Amazon S3 APIs supported by the Samsung Cloud Platform Object Storage service is as follows.

Reference
For detailed information about the Amazon S3 API, see the Amazon S3 API Guide.
CategoryDetailed description
head-bucketView bucket information
list-bucketsView bucket list
get-bucket-versioningBucket version management lookup
put-bucket-versioningBucket version control modification
get-bucket-encryptionView bucket encryption settings
put-bucket-encryptionApply bucket encryption settings
delete-bucket-encryptionDelete bucket encryption settings
copy-objectCopy, move, and rename objects
put-objectObject creation
get-objectObject download
list-objectsObject List Retrieval
head-objectObject Detail Lookup
get-object-aclObject ACL lookup
delete-objectDelete object
  • If versioning is enabled, deleting a file adds a Delete Marker to the file, and the Delete Marker becomes the latest version
  • To permanently delete a file, specify the version ID for deletion
list-object-versionsRetrieve object version list
delete-objectDelete object version
presignIssue a Presigned URL for PUT object
get-bucket-aclCheck bucket public permissions
create-bucketCreate bucket
delete-bucketDelete bucket
get-bucket-corsCheck bucket CORS (Cross OriginResources) configuration
put-bucket-corsCreate bucket CORS (PUT)
delete-bucket-corsDelete bucket CORS
put-bucket-taggingCreate bucket tagging
get-bucket-taggingBucket tagging lookup
delete-bucket-taggingDelete bucket tagging
put-bucket-websiteCreate bucket website
get-bucket-websiteView bucket website
delete-bucket-websiteDelete bucket website
get-bucket-policy-statusCheck bucket policy status
put-bucket-aclCreate bucket ACL
create-multipart-uploadCreate multipart upload
upload-partPerform multipart upload
complete-multipart-uploadMultipart upload completed
list-multipart-uploadsMultipart upload list
abort-multipart-uploadDelete incomplete Multipart upload
put-object-taggingObject tagging creation
get-object-taggingObject tagging lookup
delete-object-taggingDelete object tagging
list-objects-V2Object Lookup (v2)
put-object-aclCreate object ACL
list-partsParts lookup
put-public-access-blockCreate public access block
get-public-access-blockpublic access block lookup
delete-public-access-blockDelete public access block
put-bucket-lifecycleCreate bucket Lifecycle (only Expiration rule can be used)
get-bucket-lifecycleView bucket lifecycle
delete-bucket-lifecycleDelete bucket lifecycle
put-bucket-policyCreate bucket policy
get-bucket-policyView bucket policy
delete-bucket-policyDelete bucket policy
put-bucket-replicationModify bucket replication policy
get-bucket-replicationView bucket replication policy
delete-bucket-replicationDelete bucket replication policy
Table. Amazon S3 Supported API List

Bucket policy creation example

When using put-bucket-policy, refer to the following example to write the JSON file.

Color mode
{
    "Statement": [
        {
            "Action": "s3:*"
            "Condition": {
                "IpAddress": {
                    "scp:SourceIp": []
                },
                "Resource": {
                    "scp:SourceDBaaSId": [],
                    "scp:SourceResourceId": [],
                    "scp:SourceVpcEndpointId": []
                },
                "Service": {
                    "scp:ServiceAiTraining": "true",
                    "scp:ServiceScf": "false"
                }
            },
            "Effect": "Allow"
            "Principal": "*"
            "Resource": [
                srn:e::1234:kr-west1::objectstorage:bucket/bucketname
                srn:e::1234:kr-west1::objectstorage:bucket/bucketname/*
            ]
        }
    ],
    "Version": "2012-10-17"
}
{
    "Statement": [
        {
            "Action": "s3:*"
            "Condition": {
                "IpAddress": {
                    "scp:SourceIp": []
                },
                "Resource": {
                    "scp:SourceDBaaSId": [],
                    "scp:SourceResourceId": [],
                    "scp:SourceVpcEndpointId": []
                },
                "Service": {
                    "scp:ServiceAiTraining": "true",
                    "scp:ServiceScf": "false"
                }
            },
            "Effect": "Allow"
            "Principal": "*"
            "Resource": [
                srn:e::1234:kr-west1::objectstorage:bucket/bucketname
                srn:e::1234:kr-west1::objectstorage:bucket/bucketname/*
            ]
        }
    ],
    "Version": "2012-10-17"
}
Example of writing a JSON file when using put-bucket-policy

  • Action, Effect, Principal cannot be modified.
  • Enter the Object Storage SRN and Object Storage SRN/* in Resource.
  • Condition’s IpAddress, Resource, Service can be modified as follows.
    • IpAddress: Enter a single IP or CIDR format.
    • Resource: Enter each resource ID.
    • Service: Enter false or true.
    • For detailed information about permissible targets, refer to Setting Access Control.

Bucket replication policy creation example

put-bucket-replication, when using it, refer to the following example to create the JSON file.

Color mode
{
    "Role": "srn:e::1234:::iam:user/abc3d3442"
    "Rules": [
        {
            "ID": "replication-policy-1"
            "Status": "Enabled",
            "Priority": 1,
            "DeleteMarkerReplication": {
                "Status": "Enabled"
            },
            "Filter": {
                "Prefix": ""
            },
            "Destination": {
                "Bucket": "srn:e::1234:kr-west1::objectstorage:bucket/bucketname"
            }
        }
    ]
}
{
    "Role": "srn:e::1234:::iam:user/abc3d3442"
    "Rules": [
        {
            "ID": "replication-policy-1"
            "Status": "Enabled",
            "Priority": 1,
            "DeleteMarkerReplication": {
                "Status": "Enabled"
            },
            "Filter": {
                "Prefix": ""
            },
            "Destination": {
                "Bucket": "srn:e::1234:kr-west1::objectstorage:bucket/bucketname"
            }
        }
    ]
}
Example of writing a JSON file when using put-bucket-replication

  • Role: Enter the IAM SRN.
  • Rules > Destination’s Bucket: Please enter the Bucket SRN.
  • If you do not provide the ID of Rule, it will be automatically generated with a random value.
  • If you change the ID of Rule, a new policy is created and the existing policy is deleted.

Amazon S3 CLI

To use Amazon S3 with the AWS CLI, refer to the Amazon S3 CLI Guide.

Amazon S3 SDK for Java

To use the Amazon S3 SDK for Java, refer to the Amazon S3 SDK Guide.

Reference
For SDK guides and Rest API guides for other languages, see the AWS official website.
Reference
  • Use the region parameter required for using the Amazon S3 SDK as referenced below.
    • In case of Korea West (kr-west1): kr-west
    • In the case of South Korea 1,2,3 (kr-south1,2,3): kr-south
  • The region parameter is for reference only, and the actual region is determined based on the URL.
Reference
  • Korea South 3 (kr-south3) region constraints
    • File upload and download functions are limited through the Samsung Cloud Platform Console.
    • Using the S3 API/CLI with a public URL is restricted.
    • However, accessing a Private URL through resources (such as Virtual Server) created in the Samsung Cloud Platform Console is possible.
  • Korea South 1 (kr-south1), Korea South 2 (kr-south2) region constraints

2 - Monitoring Metrics

Cloud Monitoring service termination notice

According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be discontinued.
Accordingly, after the September 2026 release, resource monitoring of the Samsung Cloud Platform via Cloud Monitoring will no longer be possible.

With the new alternative service, you can continuously perform resource monitoring by using ServiceWatch, released in October 2025.
ServiceWatch provides more modern and powerful features, replacing Cloud Monitoring to deliver a smooth monitoring environment.

Detailed information about ServiceWatch is available in the ServiceWatch Overview.

Object Storage Monitoring Metrics

The table below shows the monitoring metrics for Object Storage that can be viewed through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.

Performance Item NameExplanationunit
ObjectsNumber of objects stored in the bucketcnt
Bucket UsedAmount of data stored in the bucket (bytes)bytes
Requests [Upload Avg]Upload usage per bucketbytes
Requests [Download Avg]Download usage per bucketbytes
Requests [Total]Total number of HTTP requests executed in the bucketcnt
Requests [Get]Number of HTTP GET requests executed on objects in the bucketcnt
Requests [Head]Number of HTTP HEAD requests executed for objects in the bucketcnt
Requests [List]Number of LIST requests executed for objects in the bucketcnt
Requests [Post]Number of HTTP POST requests executed on objects in the bucketcnt
Requests [Put]Number of HTTP PUT requests executed on objects in the bucketcnt
Requests [Delete]Number of HTTP DELETE requests executed on objects within the bucketcnt
Table. Object Storage Monitoring Metrics

3 - ServiceWatch metric

Object Storage sends metrics to ServiceWatch. The metrics provided by basic monitoring are data collected at 5‑minute intervals. In Object Storage, you can view replication metrics for each replication policy in ServiceWatch by enabling replication metrics per bucket.

Refer to How-to guides > Object Storage 복제 지표 활성화하기 for how to enable ServiceWatch replication metrics.

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

Basic Metrics

The following are basic metrics for the Object Storage namespace.

The indicators whose names are displayed in bold below are the indicators selected as key among the basic metrics provided by Object Storage. 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 querying that metric, and among the meaningful statistics, the values displayed in bold are the primary statistics. In the service dashboard, you can view key metrics through primary statistical values.

Performance itemsDetailed descriptionunitmeaningful statistics
object_countNumber of objects stored in the bucketCount
  • average
object_byteAmount of data stored in the bucketBytes
  • average
upload_bytesUpload usage per bucketbytes
  • Total
download_bytesDownload usage per bucketbytes
  • Total
all_requestsTotal number of HTTP requests executed in the bucketcnt
  • Total
get_requestsNumber of HTTP GET requests executed for objects in the bucketcnt
  • Total
head_requestsNumber of HTTP HEAD requests made for objects in the bucketcnt
  • Total
list_requestsNumber of LIST requests executed for objects in the bucketcnt
  • Total
post_requestsNumber of HTTP POST requests executed on objects in the bucketcnt
  • Total
put_requestsNumber of HTTP PUT requests executed on objects in the bucketcnt
  • Total
delete_requestsNumber of HTTP DELETE requests executed on objects within the bucketcnt
  • Total
Table. Object Storage Basic Metrics

Replication metric

The following are replication metrics. Replication metrics are collected per replication policy. Replication metrics are collected only when ServiceWatch replication metrics are enabled for each bucket. The replication metrics are as follows.

Performance itemsDetailed descriptionunitmeaningful statistics
replication_total_countTotal number of objects to be transferredCount
  • maximum
replication_transferred_countNumber of objects transmittedCount
  • total
replication_progress_countNumber of objects being transferredCount
  • maximum
replication_queued_countNumber of objects pending transmissionCount
  • maximum
replication_pending_countNumber of objects with transmission delayCount
  • maximum
replication_failure_countNumber of failed transmission objectsCount
  • Total
replication_total_bytesTotal transmission target sizeBytes
  • maximum
replication_transferred_bytesTransferred data sizeBytes
  • Total
replication_max_processing_timeMaximum processing timeSeconds
  • maximum
replication_avg_processing_timeAverage processing timeSeconds
  • average
Table. Object Storage Replication Metrics