In Elastic Beanstalk, there's support for automatically configuring and running other AWS services. The following AWS services can be used or controlled when configuring an Elastic Beanstalk environment directly from the environment deployment:

• AWS X-Ray daemon
• Log and metric collection with CloudWatch
• Log delivery to S3
• Elastic Load Balancers
• RDS databases
• SQS Queues

By default, each environment we create can be configured to have the AWS X-Ray daemon installed to help with distributed tracing when using X-Ray. We also have the ability to deliver logs either to S3 or to CloudWatch, and we can configure the enhanced CloudWatch metric collection. With Elastic Beanstalk tier environments, we are able to configure and customize a load balancer to receive the requests for our application, whereas, with a worker tier, we can configure the SQS for requests. We are also able to add an RDS database to the environment and configure the details on the fly from the deployment. However, adding a RDS database is not the best practice as the environment owns the database and deleting the environment would also delete the database.

If we require additional services and would like to configure them and attach them to the Elastic Beanstalk application, we certainly have the option to do so. We can either use the .ebextensions file to configure the AWS CLI commands that will configure the services or we can simply build the service configuration into the code and execute the commands from the SDK. With Elastic Beanstalk, the only limitation is that the environment is configured via code deployment so even minor changes to the environment will need to be delivered via an application version update.