1. Within Eclipse, you can do a subset of the stuff that ElasticFox does.
2. It can N instances of a Tomcat AMI along with an instance of a load balancer AMI automagically.
3. It can deploy a war file to all N instances simultaneously.
4. It can set-up remote debugging on all N instances so you don't have to worry about which machine the load balancer sent you to.
For me, I would find it convenient to have ElasticFox-like features inside Eclipse, but it's not a huge benefit. The "bring up lots of instances" stuff is nice, but most corporate operations groups would prefer to script such things rather than have ops people clicking buttons. And, the cases where I would want to debug in a cluster are rather limited -- cross machine concurrency issues (distributed cache invalidation/replication, session replication, etc.).
1. Within Eclipse, you can do a subset of the stuff that ElasticFox does.
2. It can N instances of a Tomcat AMI along with an instance of a load balancer AMI automagically.
3. It can deploy a war file to all N instances simultaneously.
4. It can set-up remote debugging on all N instances so you don't have to worry about which machine the load balancer sent you to.
For me, I would find it convenient to have ElasticFox-like features inside Eclipse, but it's not a huge benefit. The "bring up lots of instances" stuff is nice, but most corporate operations groups would prefer to script such things rather than have ops people clicking buttons. And, the cases where I would want to debug in a cluster are rather limited -- cross machine concurrency issues (distributed cache invalidation/replication, session replication, etc.).