Available in Classic and VPC
A bucket created in Ncloud Storage is a space to store objects. Once you create at least 1 bucket, the Ncloud Storage subscription starts.
To create and manage buckets in the NAVER Cloud Platform console:
Create bucket.
To create a bucket in the Ncloud Storage service:
- From the NAVER Cloud Platform console, navigate to
> Services > Storage > Ncloud Storage > Bucket Management. - Click [Create bucket] in the Bucket Management interface.
- Enter the required information in the Enter basic information step.
- Region: Specify the Region where you will create the bucket.
- Bucket name: Enter the name of the bucket to create. (See Bucket name rules.)
- Once a bucket has been created, you cannot change its name or Region.
- Click [Next].
- Select whether to enable bucket versioning in the Manage settings step.
- Bucket versioning: Once enabled, you cannot disable it. You can only pause the feature when you are not using it.
- For more information about version management, see Bucket versioning guide.
- After confirming the information you entered, click [Create bucket].
- A bucket is created.
- You can create up to 100 buckets by Region.
If you need to increase the bucket creation limit, request as follows:
- Request through customer support: NAVER Cloud Platform portal > Customer Support > Contact Support
- Request through the console: Use Service Quota
Bucket name rules
The string rules for bucket names in Ncloud Storage are as follows:
- You must enter a unique name for each Region. If there is an identical bucket name, you cannot register it.
- You can enter between 3 and 63 characters.
- You can only use lowercase letters, numbers, and/or hyphens (-). It must start and end with a letter or a number.
- You cannot use the following prefixes: xn--, sthree-, sthree-configurator, and amzn-s3-demo-.
- You cannot use the following suffixes: -s3alias, --ol-s3, .mrap, and --x-s3.
You cannot change the name of the bucket you entered upon creation.
Manage bucket
You can set options or view details in the bucket management menu. To manage buckets:
- From the NAVER Cloud Platform console, navigate to
> Services > Storage > Ncloud Storage. - Select a bucket from the bucket list on the Bucket Management interface.
- View the bucket details, bucket versioning, lifecycle management, and encryption management status.
.png?sv=2022-11-02&spr=https&st=2026-03-10T12%3A27%3A14Z&se=2026-03-10T12%3A45%3A14Z&sr=c&sp=r&sig=0VZBT%2FPKDxIxIqo2oyf04%2B8ELvl7PJ1z2LCYoWfXt7Y%3D)
| Component | Description |
|---|---|
| ① Management menu | |
| ② View information | Bucket details. |
| ③ Version management | View whether the bucket versioning feature is enabled. |
| ④ Lifecycle management | View whether the lifecycle management feature is enabled. |
| ⑤ Encryption management | View whether the data encryption is enabled and its type. |
Delete bucket
To delete buckets:
- Select the bucket you want to delete from the bucket list and click [Delete bucket].
- Enter the bucket name in the Delete bucket popup, then click [OK].
- Check that the task is completed in the Delete popup and close the window.
When you delete a bucket, all objects stored in the bucket are deleted. Deleted objects cannot be recovered.
Cancel bucket deletion
During bucket deletion, the Cancel bucket deletion button is enabled so that you can cancel the deletion. To cancel bucket deletion, click [Save] in the Cancel bucket deletion popup.
Even if you cancel the deletion, you cannot recover objects that have already been deleted. Only objects that have not been deleted yet remain.
Details
The following are the bucket details you can view on the console:
- Bucket name: Name of the selected bucket.
- Size: Total size of objects stored in the selected bucket.
- Number of objects: Total number of objects stored in the selected bucket.
- Whether there are incomplete multipart uploads: If you upload large-scale objects using multipart upload, whether any incomplete multipart upload remain.
If incomplete multipart uploads remain, storage fees are incurred based on the size of the part already uploaded. Complete multipart uploads or cancel incomplete uploads to avoid incurring excessive fees.
Bucket versioning
Version management is a feature that stores multiple versions of a file for 1 object. When the bucket versioning feature is enabled, all versions of objects stored in the bucket are reserved and can be retrieved and restored. This allows you to easily restore an object to a previous version in case of unintended actions, like accidentally deleting it.
To enable bucket versioning feature:
Enable in the bucket creation step
In Step 2 of bucket creation, Select whether to enable bucket versioning under Manage settings > Bucket versioning.
Enable bucket versioning in the bucket list
- Select the bucket from the bucket list and click
in the Bucket versioning component. - Select Enable in the bucket versioning popup.
- Click [Apply].
- The bucket versioning feature is enabled.
- Once the bucket versioning feature is enabled, you cannot disable it again, but only pause it. Pausing the bucket versioning feature stops the creation of new versions of objects and reserves existing object versions.
- If you use the bucket versioning feature, the features to delete buckets and delete folders, including sub-objects, are limited in the console. To delete a bucket or folder, set the Show version button at the top of the object management list to ON, then manually delete all versions of the objects beneath it.
- For more information about how to manage version, see Manage object.
When you use the version management feature, storage fees are incurred for all versions of created objects.
Lifecycle management
Lifecycle management is a feature that allows you to use the storage cost efficiently by setting task rules for objects stored in the bucket to transfer the object to a lower-cost storage class or by automatically deleting the expired objects. You can set up to 1,000 rules per bucket. The same rules are applied to the objects stored after the rules are set.
- Objects deleted according to the expiration policy cannot be recovered.
Enable lifecycle management
To enable the lifecycle management feature:
- Select the bucket from the bucket list and click
in the Lifecycle management component. - In the Lifecycle management popup, select Add rules.
- In the Add rules popup, set detailed rules and click [Save]. For more information about performing tasks, see Lifecycle management tasks.
- The object transfer or expiration tasks are performed according to the rules you set. The same rules are applied to the objects stored after the rules are set.
- When new lifecycle rules are applied, paused, or deleted, it may take up to a few minutes for the lifecycle configuration to be fully applied.
- A delay of several days may occur between the time when the conditions for performing the lifecycle rules are met and the time when the actual task is completed.
Lifecycle management tasks
The types of tasks that can be performed through the lifecycle management settings are as follows:
- Switch the current version of the object: Move the latest version of an object to the specified storage class when the specified period or date is reached. However, the task is carried out only for objects larger than 128 KB.
- You can configure the specific date option only through the API or CLI, and rules with a date cannot be edited in the console.
- Switch the previous version of the object: After the latest version of the object is switched to the previous version (after it becomes the non-current version of the object), move the object to the designated storage class when the designated time arrives. If you specify how many previous versions to keep, all previous versions beyond that number are moved to the specified storage class. However, the task is carried out only for objects larger than 128 KB.
- Delete the current version of the object: When the designated time arrives, delete the latest version of the object and add the deletion marker. Through this, the latest version of the object is switched to the previous version, and the deletion marker becomes the latest version.
- Here, if the version of the object is more than 1 and the deletion marker is the latest version, the task is not carried out.
- Delete the previous version of the object: After the latest version of the object is switched to the previous version (after it becomes the non-current version of the object), permanently delete the previous version of the object when the designated time arrives. Objects deleted due to the deletion task can't be recovered.
- Delete the expired deletion marker: If the latest version of the object is the deletion marker and the previous version of the object doesn't exist (if the latest object is the only object version), you can delete the deletion marker.
If several lifecycle rules are set in 1 bucket, the priority of performing tasks is in the following order: Permanent deletion, switch, and deletion marker creation.
If a task with a specific date remains ON after the execution date, the action continues to run. Make sure to delete the rule after the date has passed.
Edit lifecycle management rules
You can edit the lifecycle rules you set.
- Select the rule you want to edit from the list of rules in the lifecycle management popup, and click [Edit].
- In the Edit rules popup, set detailed rules and click [OK].
Delete lifecycle management rules
You can delete the lifecycle rules you set.
- Select the rule you want to delete from the list of rules in the lifecycle management popup, and click [Delete].
- Check the instruction in the Delete popup and click [Delete].
Encryption management
Encryption management is a feature that encrypts and stores objects stored in the bucket. For all buckets created in Ncloud Storage, the server-side encryption using NCP-managed key (SSE-S3) is applied as the default encryption. If you want to use customer-provided keys for encryption (SSE-C), you can apply it through the API or CLI.
Objects encrypted with customer-provided keys (SSE-C) cannot be viewed in detail, uploaded, or updated in the console (including copy, changing storage classes, and adding metadata). However, you can access them by using the API or CLI with the customer-provided key.
Starting July 29, 2025, NCP-managed key encryption is automatically applied only to objects uploaded after that date. To encrypt a previously uploaded object, create a copy of the object.