ApproveRfc
Marks the specified RFC as approved.
An RFC with a CT of "Execution mode: Manual" requires approval; rarely it requires
customer response, either approval or rejection. If your response is explicitly required,
the Approval Status: CustomerApproval Pending RFC status is in the RFC
execution output, but you receive no other notice. You must explicitly reject or approve
the RFC by running this operation or the RejectRfc operation.
Request Syntax
{
"RfcId": "string"
}Request Parameters
For information about the parameters that are common to all actions, see Common Parameters.
The request accepts the following data in JSON format.
- RfcId
-
The unique ID (UUID) of the RFC to approve.
Type: String
Required: Yes
Response Elements
If the action is successful, the service sends back an HTTP 200 response with an empty HTTP body.
Errors
For information about the errors that are common to all actions, see Common Errors.
- InternalServerError
-
An unspecified server error occurred.
HTTP Status Code: 500
- InvalidArgumentException
-
A specified argument is not valid.
HTTP Status Code: 400
- InvalidRfcStateException
-
The RFC is not in a state that allows the requested operation. Actual status code: 409
HTTP Status Code: 400
- ResourceNotFoundException
-
A specified resource could not be located. Actual status code: 404
HTTP Status Code: 400
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following:
