Glue: Testing connection triggers "Task allocated capacity exceeded limit" error

0

We have a Glue connection that was running successfully. Now, though, even when testing the connection we get a "Task allocated capacity exceeded limit" error. We have checked the max DPUs and concurrency quotas. They're fine. The connection is going though a VPC, but that was working a couple of days ago. No CloudWatch logs are being written, so it's impossible to know what service / quota limit is triggering the error.

已提問 2 年前檢視次數 358 次
1 個回答
0

I'll answer my own question :)

For some reason, AWS kept resetting my DPU quota to 0 after increasing it to 1000. So I just requested more than 1000 and now it's sticking.

已回答 2 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南