Questions[amazon-beanstalk](server)

I am trying to install beanstalk for php using git. I am using a Windows Client machine. I am done with the prerequisite installations , credentials setup. I am following the link

http://docs.amazonwebservices.com/elasticbeanstalk/latest/dg/create_deploy_PHP.sdlc.html

The following step does not workout (i use git bash for git related commands)

From your Git repository directory, type the following command.

git aws.config

This gives the error

git : 'aws.config' is not a git command.

Please suggest how to deal with the issue.

My PHP5.3 application is currently running on a Windows 2003 server running XAMPP 1.7.7 I've decided it will be better if I can get it moved onto the cloud, and Amazon Elastic Beanstalk looks like the easiest way to go. I'm starting with a 64bit Amazon Linux running PHP 5.3 container. My next step is to limit access to the website with an htpasswd file. I'd rather not use .htaccess files. How do I configure Beanstalk Apache conf file settings (on Windows the settings are stored in httpd.conf)?

I can give a single instance an Elastic IP. No problem.

But I have an Elastic Beanstalk app. It can create and remove instances as needed. It has a load balancer. How can I get these features (Elastic IP and Elastic Beanstalk) to work together?

Ultimately, all I want to do is make calls to my server through my domain like this: mydomain.com/someApiCall and I don't want to worry about my Elastic IP becoming "detached."

I am using AWS Elastic Beanstalk, it is easy to start with deploying Java based web app, which is great.

However, I want to install Memcached on every instance locally so they can be used for caching, but seems it validated the principle of Elastic Beanstalk?

Is it possible to deploy memcached locally and automatically, together with Elastic Beanstalk's auto scale feature?

(I know I can use Elastic Cache but want to save some money but still take the advantage of auto scaling)

Thanks.

Is the 1.7 GB memory bottlenecked by the 32 bit processor in case of Small instance? Or does choosing 64 bit Micro instance give better performance because its 64bit? I am confused performance wise, and cant think straight. Even if there is no fixed answer, can anyone list out the points I should think about before selecting either? If it helps, this is my configuration:

1 Micro/Small Instance, running via Elastic Beanstalk. Hosts the webapp, created in GWT, and is a mongoDB slave.
1 Large DB-server, running as mongoDB master. The webapp queries the DB-Server for data, the slave is a read-only.

The webapp runs mongod, memcached, apache and tomcat.

PS: We need an amazon-beanstalk tag.