Connection limit and Created new Failed Manifest

Hi, I have two kind of errors:

How I can make a way to reprocess automatically (not manually)?
I have the failureTopicARN but for this kind of error is not called right?
and I have the failedManifestKey that are saved in s3 bucket but the flow ends here.

```
Cluster Load Failure error: abort query on Cluster xxxxxx.amazonaws.com
...
error: abort query\n code: 1020\n context: system requested abort\n query: 10119908\n location: queryabort.hpp:62\n process: padbmaster [pid=32211]\n
...

Cluster Load Failure error: connection limit "500" exceeded for non-bootstrap users on Cluster xxxxxxx.redshift.amazonaws.com

end of lambda:
Created new Failed Manifest xxxxxx
{
"xxxxxxxxxx.redshift.amazonaws.com": {
"status": -1,
"error": {
"name": "error",
"length": 157,
"severity": "FATAL",
"code": "53300",
"file": "/home/ec2-user/padb/src/pg/src/backend/utils/init/postinit.c",
"line": "571",
"routine": "InitPostgres"
}
}
}

2019-06-04T06:06:15.613Z d4f668ac-7193-4a16-8123-0a50c4eff75c
{
"errorMessage": "error"
}
```

Inizia con il flusso di errore Lambda descritto nell’issue, inclusi failureTopicARN e failedManifestKey, e analizza gli errori connection-limit e Cluster Load Failure registrati. Determina se i manifesti non riusciti devono essere ritentati automaticamente e quale comportamento di completamento dovrebbe essere osservabile per il richiedente.

Scritto dal modello di indicizzazione a partire dal testo della issue.