Any thoughts on adding support for control of Amazon EC2 virtual machine instances? It would be a similar set of functions like you have not for Hyper-V, etc., but would use the Amazon API with a particular set of credentials. The same could be done for Microsoft Azure and maybe one or two others (although EC2 would cover a lot of ground).

With that in mind, the set of functions for any "cloud" (or local VM system) is roughly the same (start a VM, stop a VM, reboot a VM, check status of a VM, etc.); maybe there would be a way to make these functions generic enough to target various back-end systems using the same tasks with different credentials?

Yes, we have some plans about EC2 but there are two many differences to combine it with other virtualizing Tasks - it will be own Tasks.

---

Any target dates for EC2 instance tasks? Also, will Elastic Load Balancer (ELB) control be included initially?

Hi,

here are the Tasks we plan to implement.

http://screencast.com/t/KwlGW16LEfA 

1. Does it cover what you need?
2. which Tasks are most important`?

---

Looks good. Some quick thoughts:
1) If there is any thought on "order of priorities", things that are generally done rarely (like creating a new keypair or a new security group) would be low priority in my mind, vs things that involve automated maintenance of existing EC2 resources (like rebooting or launching an instance).
2) Can/should the "create/end session" functionality not be done automatically (i.e. the session is automatically created on the first EC2 task and ended when the job ends)? Or maybe there is some other purpose you have in mind for these functions?

Not on this list, but to me, the most important "next up" things are:
1) Control of Elastic Load Balancers (list/add/remove instances)
2) Access to EC2 health checks

Looks good. Some quick thoughts:
1) If there is any thought on "order of priorities", things that are generally done rarely (like creating a new keypair or a new security group) would be low priority in my mind, vs things that involve automated maintenance of existing EC2 resources (like rebooting or launching an instance).
2) Can/should the "create/end session" functionality not be done automatically (i.e. the session is automatically created on the first EC2 task and ended when the job ends)? Or maybe there is some other purpose you have in mind for these functions?

Not on this list, but to me, the most important "next up" things are:
1) Control of Elastic Load Balancers (list/add/remove instances)
2) Access to EC2 health checks

1. thanks
2. this will not be a Task itself but built in, same as Connections are used in FTP Tasks for example. Probably, a new session will be auto-created for each Task rather than doing many things. Do you think there is a big need for doing many things at once?

About the other suggestions:

1. could you elaborate more on the properties and how it would like like in terms of UI and features
2. same here, + more details on what kind of result you expect from the Task

Here are more methods regarding ELB. Which ones are intresting?
http://docs.aws.amazon.c...d_Balancing_cmdlets.html 

---

Any feedback on last post?

---