Description
In the current implementation, the EC2Provider will create a Key file using the user's secret key and access key. This is happening at the Provider level. It will be very useful to the user, if he has the option of creating his own key and then start an instance of his AMI using that particular key. Then, the user can use that particular instance within his workflow.
Therefore, I think this will improve the usability of the EC2 components of Airavata.