Well, I don’t mean to just state the obvious, but the general idea is to push this complexity into the services managed by Amazon. So on the frontend, you would use Amazon Elastic Load Balancing (ELB) to provide highly available load balancing. On the rear end, you use Amazon Relational Database Service (hosted MySQL), SimpleDB, … Read more
An EBS-backed instance can be “stopped” as opposed to being “terminated”. You won’t pay server charges, just storage charges for the EBS boot volume. You can “start” the server again later and all boot volume data will still be there. If, however, the server had an Elastic IP associated with it, that association will be … Read more
No it is not. Elastic Load Balancers do not have a fixed IP address – it is possible that a single ELB is actually multiple appliances, so as to overcome the bottleneck that would otherwise occur with very high load (i.e. if all connections were passing through a single ELB). ELBs will scale up by … Read more
When using the environment type “Single instance”, you always get an EIP. From Beanstalk developer guide, Environment Types: A single-instance environment contains one Amazon EC2 instance with an Elastic IP address. Disabling the “Associate Public IP Address” option does not have any effect. Switch to “Load-balancing, Autoscaling” Environment to get by without an EIP.
You need a NAT. This configuration is commonly used to support private subnets in VPC, there’s quite a detailed guide here. Once your VPC is configured to use the NAT instance all the outbound traffic will be attributed to the EIP of the NAT instance. If so, does that instance need to be solely for … Read more