I'm thinking in using CloudFront for dynamic content in combination with an Elastic Beanstalk application.
I like the features that Elastic Beanstalk offers (git deployments, automatic capacity provisioning, load balancing, auto-scaling, and application health monitoring) and I also like the new features that CloudFront introduced last week ( http://bitly.com/aws-cloudfront-dynamic ), so I was thinking on using CloudFront on front of my Elastic Beanstalk application.
What you think?
Is that a good approach? (see a simple diagram here: http://d.pr/i/f6sa )
or should I use normal EC2 instances and LoadBalancer (Maybe using a CloudFormation setup)?
If I use CloudFront in combination with Elastic Beanstalk, should I point the CloudFront origin to the Elastic LoadBalancer that Beanstalk automatically created for my application (ie: awseb-My-Environment-00000.us-east-1.elb.amazonaws.com) that I believe it could change if an environment fails and it automatically it creates a new one or should I point the origin to the app URL (ie: http://myapp.elasticbeanstalk.com ) that should always be the same?
Recommendations welcome!
Thanks!