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

ログインしていません。 ログイン 回答を投稿する。

優れた回答とは、質問に明確に答え、建設的なフィードバックを提供し、質問者の専門分野におけるスキルの向上を促すものです。

質問に答えるためのガイドライン

関連するコンテンツ