1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
Approved service limit increases (SLI) require time to batch and propagate. This was true both when SLI was approved by AWS personnel and also true via Service Quota automation tooling. There is no proactive notification for when propagation is complete.
Customers can self-service by directly querying the limit of interest via command line/SDK.
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 2 Jahren- AWS OFFICIALAktualisiert vor 6 Monaten
- AWS OFFICIALAktualisiert vor 3 Jahren
That is unfortunate, that is such a simple feature and I think would go a long way in improving service limit request experience just showing "not addressed", "in progress", "fulfilled" after approval to the customer. It has been over 4 days now and I don't think my issue has been fixed.
Specifically, I increased the API gateway timeout from 29000 ms (default) to 120000 after approval, but I have been trying to hit the same endpoint every day and now instead of a 504 gateway timeout error I get a 503 service unavailable error so I assume it is still not working since everything seems to work in my cloudwatch logs and works for requests under 30 seconds, but it just doesn't return the response over 30 seconds.