As a Notify user, I need SMS to be sent within AWS rate limits
WHY are we building?
As currently configured, Notify will send SMS fragments up to a possible rate of 5500 / minute. Meanwhile, our rate limit with AWS is 3000 / minute. We recently had several celery errors) of the form An error occurred (Throttling) when calling the Publish operation (reached max retries: 4): Rate exceeded
Notify should not send over the allowed rate limit
WHAT are we building?
Some or all of:
more use of the short code for 2FA
get more long codes? (currently have 50)
scaling down SMS (ie lower max # pods)?
lower the max number of fragments services are allowed to send?
VALUE created by our solution
We will not go over our AWS rate limit. Note that during the recent episodes on Feb 5 we only had 27 SMS sends causing errors (and being retried 5 minutes later). This could be worse in the future, however.
Acceptance Criteria
Given some context, when (X) action occurs, then (Y) outcome is achieved.
[ ] Generate appropriate log messages so that executions of this feature can be tracked
[ ] Can misuse of this feature cause harm? If yes, create an alert
[ ] Update the status of related findings, insights, and hypotheses on the Research Airtable
[ ] Once change/fix/feature is implemented, link relevant Airtable records to design artifacts (Figma)
Privacy considerations
Security controls in place
Measuring success and metrics
QA Steps
[ ] Notify scales to max SMS sending capacity without triggering throttling errors.
Description
As a Notify user, I need SMS to be sent within AWS rate limits
WHY are we building?
As currently configured, Notify will send SMS fragments up to a possible rate of 5500 / minute. Meanwhile, our rate limit with AWS is 3000 / minute. We recently had several celery errors) of the form
An error occurred (Throttling) when calling the Publish operation (reached max retries: 4): Rate exceededNotify should not send over the allowed rate limit
WHAT are we building?
Some or all of:
VALUE created by our solution
We will not go over our AWS rate limit. Note that during the recent episodes on Feb 5 we only had 27 SMS sends causing errors (and being retried 5 minutes later). This could be worse in the future, however.
Acceptance Criteria
Given some context, when (X) action occurs, then (Y) outcome is achieved.
[ ] Generate appropriate log messages so that executions of this feature can be tracked
[ ] Can misuse of this feature cause harm? If yes, create an alert
[ ] Update the status of related findings, insights, and hypotheses on the Research Airtable
[ ] Once change/fix/feature is implemented, link relevant Airtable records to design artifacts (Figma)
Privacy considerations
Security controls in place
Measuring success and metrics
QA Steps