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 年前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则