@pkamran - if you are using the server AMI it is only configured to launch the Windows AMI's and doesn't know about the Linux ones. I'll update the ec2 locations ini in Github in a bit and they'll show up as new locations.

@dbhatt Which options are you looking to configure specifically? Most of the options around device emulation and traffic-shaping are configured automatically based on the test parameters (enable mobile emulation for the WPT test and the same emulation carries into the lighthouse test).

Right now the --max-wait-for-load isn't being set but it makes sense to pass the WPT timeout setting through. Same goes for the WPT setting for additional chrome command-line switches.

The only other option that looks like you might want to tune would be which audits get run though I think it collects all of them by default.

Thank you Patrick for your response. Yes, I want to remove some audits which gets run while running light house. You are correct, as by default all the audits are there in the report. So, is there any way to configure the audit list i.e. to choose the audits we want to run?

Since the API can pull all of the individual checks from the JSON do you really need to turn off the checks at the time of testing? I certainly wouldn't add it as a UI option (API only) and I'm happy to accept a PR for the code but I probably won't be writing it.

The EC2 locations list has been updated in github so as long as your server is pulling updates it should get it within the next hour (-linux is added to each of the locations for the Linux variant).

We are running lighthouse from all ec2 location on our private instance and test are working fine, thanks for that.

But we are facing a problem with the basic Authenticated sites, whenever we run the test with lighthouse enable on Authenticated sites we are not getting Lighthouse results. Please can you let us how we can get those.

When I am trying to run the test from Linux machine, tester machines are not launching and we are getting the below error:
Error: Launching EC2 instance. Region: us-east-2, AMI: ami-95c9eef0, error: The requested configuration is currently not supported. Please check the documentation for supported configurations.