Private Instance AWS still requires api key

[e14nielson]

my problem was that i was hitting the public URL not my private agent.

new issue:

now i have my EC2 instance autoscaling and working very very well through the interface. i still cannot drive it via command line/API

calling on the server :
webpagetest test https://www.yahoo.com/ -k <My_API_Key> -s "http://ec2-35-163-162-98.us-west-2.compute.amazonaws.com/"

returns:
{
"statusCode": 200,
"statusText": "Ok",
"data": {
"testId": "161123_RN_1",
"ownerKey": "d2bd2078616a8e6393695733d33c02a64851e3bd",
"jsonUrl": "http://ec2-35-163-162-98.us-west-2.compute.amazonaws.com/jsonResult.php?test=161123_RN_1",
"xmlUrl": "http://ec2-35-163-162-98.us-west-2.compute.amazonaws.com/xmlResult/161123_RN_1/",
"userUrl": "http://ec2-35-163-162-98.us-west-2.compute.amazonaws.com/result/161123_RN_1/",
"summaryCSV": "http://ec2-35-163-162-98.us-west-2.compute.amazonaws.com/result/161123_RN_1/page_data.csv",
"detailCSV": "http://ec2-35-163-162-98.us-west-2.compute.amazonaws.com/result/161123_RN_1/requests.csv"
}

but when i try to find status : webpagetest status 161123_RN_1
{
"statusCode": 400,
"statusText": "Test not found",
"data": {
"statusCode": 400,
"statusText": "Test not found",
"id": "161123_RN_1"
}
}

Thanks,

---

Found my issue:

when calling for status --server is required for a private instance

This worked:

webpagetest status 161123_RN_1 -s "ec2-35-163-162-98.us-west-2.compute.amazonaws.com"