CloseCase
Closes an existing case.
Request Syntax
POST /v1/cases/caseId/close-case HTTP/1.1
URI Request Parameters
The request uses the following URI parameters.
- caseId
-
Required element used in combination with CloseCase to identify the case ID to close.
Length Constraints: Minimum length of 10. Maximum length of 32.
Pattern:
\d{10,32}.*Required: Yes
Request Body
The request does not have a request body.
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
"caseStatus": "string",
"closedDate": number
}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.
- caseStatus
-
A response element providing responses for requests to CloseCase. This element responds
Closedif successful.Type: String
Valid Values:
Submitted | Acknowledged | Detection and Analysis | Containment, Eradication and Recovery | Post-incident Activities | Ready to Close | Closed - closedDate
-
A response element providing responses for requests to CloseCase. This element responds with the ISO-8601 formatted timestamp of the moment when the case was closed.
Type: Timestamp
Errors
For information about the errors that are common to all actions, see Common Errors.
- AccessDeniedException
-
HTTP Status Code: 403
- ConflictException
-
HTTP Status Code: 409
- InternalServerException
-
HTTP Status Code: 500
- InvalidTokenException
-
HTTP Status Code: 423
- ResourceNotFoundException
-
HTTP Status Code: 404
- SecurityIncidentResponseNotActiveException
-
HTTP Status Code: 400
- ServiceQuotaExceededException
-
HTTP Status Code: 402
- ThrottlingException
-
HTTP Status Code: 429
- ValidationException
-
HTTP Status Code: 400
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following:
