DeleteContainer
- Print
- PDF
DeleteContainer
- Print
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Overview
Deletes containers (buckets).
Statement
DELETE https://{endpoint}/swift/v1/{containerName}
Request
Request header
| Header name | Description |
|---|---|
| x-ncp-apigw-timestamp | This is the number of milliseconds that have elapsed since January 1, 1970 00:00:00 UTC. If the time difference compared to the API Gateway server is more than 5 minutes, then the request is considered invalid. |
| x-ncp-iam-access-key | This is the access key ID issued by the NCP portal or Sub Account. |
| x-ncp-apigw-signature-v2 | Signature used to encrypt the body of the above example with the SecretKey that maps with the access key ID. The HMAC encryption algorithm is HMACSHA256. |
| x-ncp-region_code | The region code of where the bucket of the data to be migrated from another cloud to NAVER Cloud is located |
Request parameter
| Parameter name | Requirement status | Type | Restrictions | Description |
|---|---|---|---|---|
| ContainerName | - | string | - | Name of the container to delete |
Response
Response header
| Name | In | Type | Description |
|---|---|---|---|
| Date | header | string | Response time of the request (UTC) |
Examples
Request examples (JSON)
curl -X DELETE " https://archivestorage.apigw.ntruss.com/swift/v1/{containerName}" -H "accept: application/json" -H "x-ncp-region-code: {regionCode}"
-H "x-ncp-iam-access-key: {AccessKey} "
-H "x-ncp-apigw-timestamp: {current timestamp}"
-H "x-ncp-apigw-signature-v2: {generated signature}"
Response examples
HTTP/1.1 204 No Content
Connection: keep-alive
Date: Wed, 12 Sep 2018 04:34:35 GMT
Keep-alive: timeout=60
Upon successful request, it returns the No Content (204) status code.
Was this article helpful?