Skip to content

Work-around Route 53 API limit #13

Closed
cho00013 opened this issue Feb 22, 2022 · 2 comments
Closed

Work-around Route 53 API limit #13

cho00013 opened this issue Feb 22, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@cho00013
Copy link
Contributor

Route 53 has a API limit of 5 calls per second and it will throttle future calls. SDK (boto3 API) already has 5 retry logics built-in so it will retry, however, if there are multiple instances being spun up/torn down, then the probability of a failure increases. Currently the code tested successfully with 30 simultaneous launches.

Short-Term

  • Combine all records in one Private Hosted Zone (PHZ) into a single ChangeRecordSet API call.
  • Add a 1 second delay between API call to spread out the call per Instance

Long-Term

  • Leverage SQS to store/retry logic for any ChangeRecordSet API calls. This will ensure that records are created properly AND deleted properly
@cho00013 cho00013 added the enhancement New feature or request label Feb 22, 2022
@cho00013
Copy link
Contributor Author

cho00013 commented Mar 7, 2022

work-around added and in Pull Request.
#16

@cho00013
Copy link
Contributor Author

@badra001 - I think we can close this task...

Sign in to join this conversation on GitHub.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant