search

aws / aws-cdk

The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code
https://aws.amazon.com/cdk
Apache License 2.0
11.57k stars 3.88k forks source link

cdk deploy: [Error at /StackName] Request limit exceeded #21761

Closed farfaro closed 1 year ago

farfaro commented 2 years ago

Describe the bug

We have problems when we run deploy (this stack contains a ECS): image

Meanwhile, we also have this other stack, This contains several stacks of lambdas. But in this case it fails in the cdk synth: image

In this last case, we use this image "amazon/aws-sam-cli-build-image-nodejs14.x:latest" + typescript@4.7.4 + aws-cdk@2.38.1 in GitLab SaaS

The message are the same: "Request limit exceeded" This happens with new commits, and with old commits.

Expected Behavior

Update existing Stacks.

Current Behavior

[Error at /My-LambdaStack] Request limit exceeded.

Reproduction Steps

Just run "cdk deploy" and try to update/create a Lambda stack. The region is us-east-1 (N. Virginia)

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

aws-cdk@2.38.1

Framework Version

No response

Node.js Version

nodejs14

OS

Linux

Language

Typescript

Language Version

TypeScript (4.7.4)

Other information

No response

jsonpj3wt commented 2 years ago

I have also seen this and in our scenario, I limited the number of stacks being constructed to 3 (3 base stacks) and each call ec2.Vpc.fromLookup(...). This wasn't a problem yesterday but it does look like something is up because why would calling a lookup 3 times hit any type of request limit?

@farfaro the way I tracked down the exact call is to add verbose logging -v to my cdk cli command. IE: cdk deploy <whatever> -v

m00ki3 commented 2 years ago

I'm seeing the same "Request limit exceeded" error for all "cdk synth" executed against us-east-1 in all accounts in a client's org.

farfaro commented 2 years ago

It would seem that I no longer have this error. Are you the same? @jsonpj3wt @m00ki3

@madeline-k do you know if there are errors with the AWS API?

jsonpj3wt commented 2 years ago

@farfaro I am also seeing it stabilize.

@madeline-k can we get any kind of status to work with and inform our clients on deployments?

m00ki3 commented 2 years ago

hmm, seems to be stabilizing...HOWEVER, I was lured into that false sense of security earlier when it was intermittent. So, I'd like to hear something from AWS to KNOW this is fixed.

m00ki3 commented 2 years ago

I'm not seeing the issue on any of my pipelines any longer.

TheRealAmazonKendra commented 2 years ago

You should no longer be seeing this issue. Customers should AWS Health Dashboard for more information.

farfaro commented 2 years ago

@TheRealAmazonKendra It's the first thing I did. The board showed the healthy services, however the error was still reproduced.

Now it seems that everything is in order. ☺

peterwoodworth commented 1 year ago

There's not enough information to investigate with here. However it sounds like this has mostly been resolved. If you still run into this, please create a new issue. Thanks!

github-actions[bot] commented 1 year ago

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.