Just found this out – you have to hard code ‘–region us-east-1` when run aws support trusted advisor relevant commands. I guess this is caused by the same reason that I explained in my previous blog IAM dependency.
Here is my conclusion: whenever AWS says the service is global which does not require a region selection, it generally means the service is most likely hosted in the Northern Virginia (us-east-1 region).
$ aws support describe-trusted-advisor-checks --language en You must specify a region. You can also configure your region by running "aws configure". $ aws --region ap-southeast-2 support describe-trusted-advisor-checks --language en Could not connect to the endpoint URL: "https://support.ap-southeast-2.amazonaws.com/" $ aws --region us-east-1 support describe-trusted-advisor-checks --language en { "checks": [ { "category": "cost_optimizing", "description": "Checks the Amazon Elastic Compute Cloud (Amazon EC2) instances that were running at any time during the last 14 days and alerts you if the daily CPU utilization ...