GetServiceQuota not providing Quota Value about aws-cli HOT 4 CLOSED

Hi @nimble thanks for reaching out and for your patience here. The GetServiceQuota API is used in both the get-service-quota (CLI) and get_service_quota (Boto3) commands. So if there's an API issue here then we may need to escalate this to the Service Quotas team.

However, upon testing this command aws service-quotas get-service-quota --service-code 'connect' --quota-code 'L-20CD02F7', I do receive the following response:

{
    "Quota": {
        "ServiceCode": "connect",
        "ServiceName": "Amazon Connect",
        "QuotaArn": "arn:aws:servicequotas:us-west-2:<account-id>:connect/L-20CD02F7",
        "QuotaCode": "L-20CD02F7",
        "QuotaName": "Hours of operation per instance",
        "Value": 100.0,
        "Unit": "None",
        "Adjustable": true,
        "GlobalQuota": false,
        "QuotaAppliedAtLevel": "ACCOUNT",
        "QuotaContext": {
            "ContextScope": "RESOURCE",
            "ContextScopeType": "AWS::Connect::Instance",
            "ContextId": "*"
        }
    }
}

So I think the issue here may be specifically with the --context-id parameter used. When I passed my account ID as this parameter then the command also ran successfully.

I also noticed that you are using an older version of the CLI. We recommend using a more recent version in order to have access to the latest updates (which sometimes also helps resolve issues like these.) We recommend migrating to v2 of the CLI if you can, otherwise here is the v1 CHANGELOG where you can reference the latest versions in v1.

from aws-cli.

Hey @tim-finnigan,

Thanks for replying (I did end up updating my CLI; this cleared some few issues I was having). But anyways, I've proposed the following to Amazon:

I propose an enhancement to the Service Quotas API where, instead of immediately returning an error when a resource-specific quota isn't found, it could automatically fallback to return the next available quota value in the hierarchy (i.e., resource quota value, account quota value, and then AWS default quota value).

Thanks.

from aws-cli.

Thanks for following up and sharing your proposal. Changes to service API behavior are generally rare because of the need to retain backwards compatibility with existing scripts. That being said, maybe there's an opportunity to improve the documentation here regarding the curent behavior. In which case I'd recommend using the Provide feedback at the bottom of the API documentation page, and any documentation updates would automatically get reflected in the CLI docs. Otherwise if you'd like to expand on your proposed feature request further you can reach out through AWS Support or create an issue in our cross-SDK repository.

from aws-cli.

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

from aws-cli.