It states here of Elastic Beanstalk and CloudFormation that...
These services are designed to complement each other.
From my reading, I don't understand why you would want to use them together. The Elastic Beanstalk advantages seem to be nullified by CloudFormation, and vice versa, for example:
- Elastic beanstalk handles resourcing for your application, so why would I want to use CloudFormation to specify them?
- Elastic Beanstalk supports single command deployments, however these would not be possible if used with CloudFormation
- Elastic Beanstalk allows you to customise the deployment by way of .config files, do .config files work in tandem with CloudFormation templates?
- If I were using CloudFormation to specify my infrastructure, then what advantages does Elastic Beanstalk bring to the table?