The incident was caused by a surge in traffic from job applications which resulted in a higher than usual processing. Our database connections were fully allocated, which led to requests timing out whenever the application requested database connections.
We have increased our instances to handle the increased load and have updated our configuration to optimize the number of threads and workers on each instance. This is now resolved and are continuing to monitor the results