DeleteLandingZone
Decommissions a landing zone. This API call starts an asynchronous operation that deletes AWS Control Tower resources deployed in accounts managed by AWS Control Tower.
Request Syntax
POST /delete-landingzone HTTP/1.1
Content-type: application/json
{
"landingZoneIdentifier": "string
"
}
URI Request Parameters
The request does not use any URI parameters.
Request Body
The request accepts the following data in JSON format.
- landingZoneIdentifier
-
The unique identifier of the landing zone.
Type: String
Required: Yes
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
"operationIdentifier": "string"
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
The following data is returned in JSON format by the service.
- operationIdentifier
-
>A unique identifier assigned to a
DeleteLandingZone
operation. You can use this identifier as an input parameter ofGetLandingZoneOperation
to check the operation's status.Type: String
Length Constraints: Fixed length of 36.
Pattern:
^[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}$
Errors
For information about the errors that are common to all actions, see Common Errors.
- AccessDeniedException
-
You do not have sufficient access to perform this action.
HTTP Status Code: 403
- ConflictException
-
Updating or deleting the resource can cause an inconsistent state.
HTTP Status Code: 409
- InternalServerException
-
An unexpected error occurred during processing of a request.
HTTP Status Code: 500
- ResourceNotFoundException
-
The request references a resource that does not exist.
HTTP Status Code: 404
- ThrottlingException
-
The request was denied due to request throttling.
HTTP Status Code: 429
- ValidationException
-
The input does not satisfy the constraints specified by an AWS service.
HTTP Status Code: 400
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following: