Manage buckets

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:

1. From the NAVER Cloud Platform console, navigate to Menu > Services > Storage > Ncloud Storage > Bucket Management.
2. Click [Create bucket] in the Bucket Management interface.
3. Enter the required information in the Enter basic information step.
   • Region: Specify the Region to create a bucket to.
   • 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.
4. Click [Next].
5. Select whether to manage bucket versions, if necessary.
   • Bucket version management: 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 version management guide.
6. Select the encryption type for the bucket, if necessary.
   • For all buckets created in Ncloud Storage, the server-side encryption using NCP-managed key (SSE-S3) is applied as the default encryption.
   • For more information about how to set encryption, see Encryption management.
7. After confirming the information you entered, click [Create bucket].
8. A bucket is created.
   • You can create up to 100 buckets by Region.

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 English 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.

Manage buckets

You can set options or view details in the bucket management menu. To manage buckets:

1. From the NAVER Cloud Platform console, navigate to Menu > Services > Storage > Ncloud Storage.
2. Select a bucket from the bucket list on the Bucket Management interface.
3. View the bucket details, bucket version management, lifecycle management, and encryption management status.

Delete bucket

To delete a bucket:

1. Select the bucket you want to delete from the bucket list and click [Delete bucket].
2. Enter the bucket name in the bucket deletion popup, then click [OK].
3. Check that the task is completed in the deletion popup and close it.

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.

Details

The following are the bucket details you can view from 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.

Bucket version management

Version management is a feature that stores multiple versions of a file for 1 object. When the bucket version management 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 version management feature:

Enable in the bucket creation step

In Step 2 of bucket creation, Select whether to enable bucket version management under Manage settings > Bucket version management.

Enable bucket version management in the bucket list

1. Select the bucket from the bucket list and click in the Bucket version management area.
2. Select Enable in the bucket version management popup.
3. Click [Apply].
4. The bucket version management feature is enabled.

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.

Enable lifecycle management

To enable the lifecycle management feature:

1. Select the bucket from the bucket list and click in the Lifecycle management component.
2. In the Lifecycle management popup, select Add rule.
3. In the rule addition popup, set detailed rules and click [Save]. For more information about performing tasks, see Lifecycle management tasks.
4. 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.

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 does not exist (if the latest object is the only object version), you can delete the deletion marker.

Edit lifecycle management rules

You can edit the lifecycle rules you set.

1. Select the rule you want to edit from the list of rules in the lifecycle management popup, and click [Edit].
2. In the Edit rules popup, set detailed rules and click [OK].

Delete lifecycle management rules

You can delete the lifecycle rules you set.

1. Select the rule you want to delete from the list of rules in the lifecycle management popup, and click [Delete].
2. 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. The encryption types provided in Ncloud Storage are as follows:

• NCP-managed key (SSE-S3): Data is automatically encrypted on the server using the encryption key managed by Ncloud Storage. You do not need to create or manage keys, as data is automatically encrypted upon storage and decrypted upon access. It is provided as the default encryption type. SSE-S3 is applied if you do not specify the encryption management type.
• KMS master key (SSE-KMS): Data is encrypted on the server using the keys managed by Key Management Service (KMS).

Set CORS

You can access objects in the current bucket from another domain’s web application using the CORS feature. You can control access by setting the origin, HTTP methods, and headers to allow resource requests. You can set up to 100 rules. To set CORS policy:

1. Select the bucket from the bucket list and click in the Set CORS area.
2. In the CORS setting popup, click Edit.
3. Enter a JSON-formatted policy in the CORS policy edition popup, and click [OK].
   • For more information about CORS configuration, see CORS components.
4. Check the content of the CORS setting popup, and click [OK].
   • If you do not click [OK] in the CORS setting popup, the policy you have written does not apply.

CORS components

The components of CORS are as follows: