By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Service quotas applied by Support not reflected in Service Quotas

1

I am currently working on developing a microservice that monitors the quotas of AppStream instances. The main functionalities I require are the ability to retrieve the current service quotas and request an increase in case the value is not compliant. Recently, I programmatically requested two quota increases for the AppStream instances and these requests have already been approved by the Support team. However, when checking the status in the Service Quota, it still shows as 'Quota requested'.

The problem lies in the fact that the available quota value has not been updated in the Service Quota, and when making calls to ListServiceQuotas, it returns an empty list. This is the second time I have attempted to update the Applied quota value for the AppStream instances through Support, but the Applied quota value still shows as 'Not Available'. Despite this, I am still able to utilize the requested AppStream instances as intended.

I need guidance on how to properly reflect the Support-applied quotas in the Service Quotas, so that I can effectively monitor the current quotas.

Topics
End User Computing
Tags
Amazon AppStreamService Quotas
Language
English
rePost-User-5267178
asked 2 years ago1.4K views
2 Answers
1
Accepted Answer

The label "Not Available" means that the service has not implemented the feature to report the applied quota on the console. Unfortunately, for such services, it is not possible to get the applied quota value via Service Quotas [+]. Once the service is fully on boarded on to Service Quotas, you will be able to see the values.

[+] https://docs.aws.amazon.com/servicequotas/latest/userguide/gs-request-quota.html

GetServiceQuota API [+] retrieve the applied quota value for the specified quota. For some quotas, only the default values are available. If the applied quota value is not available for a quota, the quota is not retrieved.

[+] https://docs.aws.amazon.com/servicequotas/2019-06-24/apireference/API_GetServiceQuota.html

profile pictureAWS
EXPERT
Makendran G
answered 2 years ago
profile picture
EXPERT
Riku_Kobayashi
reviewed 2 years ago
profile picture
EXPERT
Hiroki Takahashi
reviewed 2 years ago
1

This is really annoying for large scaled workloads and make the limits/quota governance a huge and hard activity. This issue affects several services (e.g: S3, DynamoDB, AppStream and much others).

I hope AWS can focus on this and make quotas fully operational for all services they deploy.

Diogo Dantas
answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content