Database Reference
In-Depth Information
Server-side error with status code 500
Lastly, we will see the errors that are caused on the server side due to some issues with the
server acting as the REST endpoint. For all the server-side errors, it is best practice to per-
form the operation again, that is, retry after some time.
InternalFailure and InternalServerError
This error will provide the
The server encountered an internal error
trying to fulfill the request
error message. This exception occurs on the
server side, about which the client doesn't have any information. But this error will be
thrown only if the server is up and running.
ServiceUnavailableException
This exception will be raised if the service (DynamoDB, S3, and so on) is not available for
use. The error message shown by this error is
The service is currently un-
available or busy
.
The sample response along with the exception message is shown in the following screen-
shot. In the event that an improper access key ID is provided, it will result in something
similar to the following screenshot:
From the previous screenshot, a few things are clear. The status response is 400 with the
UnrecognizedClientException
exception and it took 292 ms to respond to the re-
