Conecting to Amazon AWS

It should not be any different from connecting to MySQL running on any other server. Make sure that MySQL is running on the server, enable remote access to MySQL and connect. Most likely you will need to use your server IP address as MySQL server address while connecting.
Please note that all this needs to be handled outside of PHPRunner and you may have better luck asking this question in AWS related forums.

Thanks for your reply but if you look at AWS you will see it is far more complex. I will try AWS forum but I thought it worth trying on here to see if any user had experience of it.

Thanks.

While AWS is a really complicated topic all PHPRunner needs to know is MySQL server address, username and password.
What I mean by saying this is not a PHPRunner question is that connection setup will be exactly the same when you connect to MySQL running on AWS from any other software like Navicat, SQLYog or DBForge.
Also, make sure you are not confusing Amazon AWS with Amazon RDS.

http://www.alexkorn.com/blog/2011/03/getting-php-mysql-running-amazon-ec2/
Though being an elder 2011 dated "HowTo", I think, nothing had been really changing when it comes to MAIN FRAME COMPUTING power sales to maybe users/clients like us. Say, the HowTo talks about "Elastic IP" and TWO instances to get installed ..., anyway, my own experience on a similar issue dates back to April 2014 where I had some trouble with another main frame computing power seller where it came to light that I could totally forget about e.g. CONNECTION SCRIPT to get installed, but WORST, when it comes to more than CRUD (Create, Retrieve, Update and Delete) operations, it came to light that a kind of "APPROVAL OF APPLIANCE" was needed first to then pave the way to experience more on how it could work or not. From my point of view, your client looks solely at the operational hosting cost rather than to see a hopefully MASTERPIECE of code to get hosted that way, later modifications/enhancements won't become a true night mare for APP makers like you by tons of extra hours to get paid on later APP HEALTH CARE cost. So..., I would recommend to explain to your client that he would be much better off to look at the MASTERPIECE of code AFTERMARKET cost here in first instance as of course, on the long run, enhancements would become a matter while my recent hosting price studies revealed that the monthly cost for 62 virtual machined workstations (of each only 200 Mhz, yet just as an example) under 120 GB storage place and tons of traffic included is not more than roughly $1,250/mo., so, a simple PHP/MySQL server with lots of RAM and GBs for storage, modular arrangeable by so and so many 200 Mhz units needs would certainly reveal that the AWS offer is not so competitive as expected, especially when you look at time investments to be done once changes on PHP Version, MySQL version, PHPR v8.0 oriented updates and subsequent apps enhancements would finally pile up by hourly rates at your end to get the client's app UP and RUNNING under client's latest requirements.