Anyone tried to run lots of

sst deploys

in parallel--and hit AWS RATE LIMITS?

Hey @Drew, can you give this retry option a try?

logRetentionRetryOptions: {
      base: Duration.millis(500),
      maxRetries: 15,
    },

Yes! I’ll try that now

We are thinking to make this the default

I was just thinking about that too

Nice 👍

https://github.com/serverless-stack/serverless-stack/issues/749 -- @Drew There is an open issue for this. I'll ty to fix it for eveyrone, then.

Oh, extra nice! That’d be great @JP (junaway) …however, be aware this didn’t fix all our rate limit issues. There are other sections which might also fail immediately without retry

@Frank Any thoughts ?

@Drew do you mean you also got this rate exceeded error for other resources (beside log retention)?

Yep — we ran describeStacks too much (I’m not 100% on which calls, but we had something else that’s angry too) We’re going to be less aggressive with running this

Hey @Drew, are you running a lot of `sst deploy`s in parallel, or are you deploy a lot of stacks in an

sst deploy

?

Lots of

sst deploy

in parallel. We run the parallel deploys on another system. We don’t hit this problem on SEED.

Ah I see. Do you have a screenshot by any chance? I think I have a quick fix for this. Just wanted to look at the screenshot and make sure.