By using AWS re:Post, you agree to the Terms of Use

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.

asked 2 months ago134 views
1 Answer
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.

answered 2 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions