Based on my research, I have found that this behaviour is observed for quotas that are not adjustable, when using
GetServiceQuota. You need to use
GetAWSDefaultServiceQuota instead. If this does not work either, try to see if this is observed on other languages as well.
I can confirm that this is an unexpected behaviour seen with SDK, and a known issue I've come across before where it works properly with CLI only. On a side note, although a rare possibility - I would suggest to see if there is perhaps anything wrong with the code as well. Because, if it works with the CLI it means that there is no issue with the API call being made.
- Accepted Answerasked 4 years ago
- Accepted Answerasked 2 months ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 5 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 3 years ago
- EXPERTpublished 3 months ago
- EXPERTpublished 4 months ago
Thanks for the reply, I will try out
GetAWSDefaultServiceQuota-- but I will say that we are not using the default quota for Classic Load Balancers. I have checked the code several times and have gotten others on my team to check it but it seems to be correct.
I will also try out other languages to see if it exists in those SDKs. Thanks for your reply, Shreyas.
Hey Shreyas, I checked and it seems that L-E9E9831D is adjustable in the console. Do you know when the bug for the AWS GO SDK will be addressed? We need a way to fetch the "Applied quota value" using the SDK. Thanks