Hi Ian and Stian,

We actually have an enactor on an Amazon cloud. It works :-)  We use it strictly for ourselves at the moment though and the virtual machine is not always on.

I'm not so afraid of the 'delete-all' workflow. The dykes of Holland have a >0% chance of flooding, but I feel quite safe ;-)

Would most harm not be limited to the local machine? That may actually plea for cloud virtual machines: easy to setup and destroy again.

Cheers,
Marco.

Stian Soiland-Reyes wrote:
2009/3/31 Ian Dunlop <[email protected]>:

  
Not sure about 'griddy', maybe more 'cloudy'.  Remote enactor/Taverna
platform on EC2?  What about an instance of Taverna on the cloud that you
can get whenever you need it.
    

You would need to include some kind of authorisation (so only people
you 'trust' can run worklfows) or limit which workflows can run (only
trusted workflows). Remember that a workflow can include various
untrusted beanshell scripts and local commands. I could make one now
that deletes all your files, for instance..

I doubt Amazon will find it funny if someone runs an evil workflow
that does various spamming or network attacks - and you as the
customer would be the one to blame, as you would be the one opening up
the machine for abuse..

Another alternative is to somehow limit the possible services in a
workflow, but then one could only include (manually) pre-approved
beanshell scripts and local workers. I guess WSDL services should be
OK, but perhaps one would also need to put a limit on the number of
calls, otherwise someone could make a workflow that generates 100000
strings and sends them to the 'web service' at
http://sitetotakedown.com/  - although this wouldn't be a web service
there would still be 100k invalid request for sitetotakedown to
handle, that might take down the web site in a denial of service
attack.

  

-- 

Marco Roos
Faculty of Science
University of Amsterdam
Kruislaan 403, room F1.02
1098 SJ Amsterdam
tel. +31 (0) 20 525 7522
http://home.medewerker.uva.nl/m.roos1 (includes links to social networks)
Note the change of e-mail address to [email protected]
------------------------------------------------------------------------------
_______________________________________________
taverna-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/taverna-users
Documentation: http://www.mygrid.org.uk/usermanual1.7/
FAQ: http://www.mygrid.org.uk/wiki/Mygrid/TavernaFaq
Biological Services: http://www.mygrid.org.uk/wiki/Mygrid/BiologicalWebServices

Reply via email to