Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Rate limit prevention

See original GitHub issue

Hi,

I was trying to integrate this plugin into my CI pipeline for a project we’re doing using serverless. Although I noticed that If I call your domain creation everytime in the pipeline, after certain number of calls I get this

$ serverless create_domain

  Error --------------------------------------------------

  Error: 'my.custom.domain' was not created in Route53.
Throttling: Rate exceeded

     For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.

  Get Support --------------------------------------------
     Docs:          docs.serverless.com
     Bugs:          github.com/serverless/serverless/issues
     Issues:        forum.serverless.com

  Your Environment Information -----------------------------
     OS:                     linux
     Node Version:           8.11.3
     Serverless Version:     1.28.0

Is there a way to prevent the creation if the domain is already present? Can you maybe integrate the call into your plugin in order to prevent it?

Thank you in advance, Julian

Issue Analytics

State:
Created 5 years ago
Comments:6

Top GitHub Comments

2reactions

rddimoncommented, Apr 13, 2022

Hi there

Hope you are doing well and have found a solution for the current issue! The domain manager has the autoDomain option which you can use in the latest version. And a lot of changes were released and I believe this issue has been solved

Closing it as it’s no longer relevant

Feel free to reopen it in case of any further issues related to it

1reaction

tim-stassecommented, Aug 15, 2018

Having to run the create_domain command once, and only once, does present an issue with using this as part of a CI deployment pipeline. It would be even better if there was no create_domain command at all, and instead simply did everything using the deploy command.

Though that is a breaking change that might have to come later, and the mentioned enhancement would suffice.

Top Results From Across the Web

What Is Rate Limiting? | How to Use It - Akana

Rate limiting helps prevent a user from exhausting the system's resources. Without rate limiting, it's easier for a malicious party to ...

What is rate limiting? | Rate limiting and bots - Cloudflare

Rate limiting is a strategy for limiting network traffic. It puts a cap on how often someone can repeat an action within a...

Implement API rate limiting to reduce attack surfaces

Rate-limiting is used to prevent users overwhelming your API with requests, limiting denial of service threats. · Encryption ensures that data is kept ......

Rate-limiting strategies and techniques - Google Cloud

Rate limiting refers to preventing the frequency of an operation from exceeding some constraint. In large-scale systems, rate limiting is ...

Best Practices to Prevent Rate-Limiting | Marketing Cloud APIs ...

To keep API traffic flowing, Marketing Cloud rate-limits API requests to preserve system stability under unexpectedly high load.