Kabeer's questions

I have claimed an additional Elastic IP address and associated with an running instance. It is also tied up with a secondary Private IP Address.

I am unable to ping the new Elastic IP address.

Further, do I need to create a separate Security Group for every Elastic IP address associated with an EC2 instance, given that I wish to expose different ports on different IP addresses? How do I do so?

I have been able to open port 80 for inbound HTTP traffic on my medium AWS instance running Windows 2008 R2 with IIS 7.5

I want to be able to open another port (say 8000) for inbound HTTP traffic. I'm unable to find a way to do so (at least from the AWS console)

I have a medium EC2 instance that runs Windows 2008 R2. I have installed the web role in order to run IIS on it. I am able to see the default website locally but not from the internet using the Public DNS. I get the message "Cannot connect to Website"

I'm planning a development environment on the cloud. My target platform is Microsoft .Net and preferred cloud id Amazon AWS (although I'm open for suggestions).

I'm planning to purchase a High-Memory On-Demand Instance and deploy one guest VM per developer within it. Here are my queries:

• Is this topology advisable?
• How would a developer directly login and work with the guest VMs?
• Besides having a good broadband Internet connection (and also a backup connection), what other care need to be taken at developer end?
• How will I be able to manage resources on my development environment? Any tools? Services?

Thanks.

I am a freelancer and plan to work with other freelancers in the coming time. Since I would be owning the project(s), I want to own the development environment as well. We all will be working out of our respective locations. I have been contemplating using Amazon's EC2 service for the purpose of erecting a development environment and giving desired access to the others involved.

With the above in mind, I have several queries:

1. Is this a good idea in the first place? Is it better to have VMs created and distributed (physically) to the members of the team? Of course I lose control in this case and data is vulnerable.
2. Should I just buy a Large instance, install all desired tools, create users and provide them access as per role?
3. Should I just buy a Large / Extra Large instance, build VMs inside the instance, one each for every role and instantiate instances per user? I am not sure right now how the access would work out. How one would be able to directly access a VM instance running inside the EC2 instance.
4. There are tools that help in managing the EC2 instances w.r.t. the EC2 APIs. However, w.r.t. what I have explained above (specially point # 3), are there tools that can help in the management / monitoring of instances and VMs within?

There may be many more complexities that I cannot think of at this point. Will appreciate inputs / directions in case someone has been through this already.

This is about hosting a web portal. Earlier my topology was entirely based on Amazon AWS but the price factor (especially for EC2) now makes me re-think.

I'll now quickly come to what I have finally arrived at. I'll launch the portal that'll be hosted on Godaddy (unlimited plan on Windows). The portal uses SimpleDB for storing metadata and S3 for blobs. Locally available MySQL will be used for the ASP.Net provider services.

Once the portal is profitable, I intent to move to Amazon in totality.

Now considering the proximity between Godaddy & Amazon, would I face 'substantial' performance problems? Are there any suggestions to improve upon my topology.