|« PreviousNext »|
|Did this page help you? Yes | No | Tell us about it...|
When deploying your applications, you may want to customize and configure the software that your application depends on. These files could be either dependencies required by the application—for example, additional packages from the yum repository—or they could be configuration files such as a replacement for httpd.conf to override specific settings that are defaulted by AWS Elastic Beanstalk. You may also want to customize your environment resources that are part of your AWS Elastic Beanstalk environment (e.g., SQS queues, ElastiCache clusters). For example, you may want to add an Amazon SQS queue and an alarm on queue depth, or you might want to add an Amazon ElastiCache cluster.
You can use configuration files if you are deploying your AWS Elastic Beanstalk application using one of the following container types:
PHP 5.3 and PHP 5.4
Ruby 1.8.7 and 1.9.3
Apache Tomcat 6 and 7
Windows Server 2008 R2 running IIS 7.5 and Windows Server 2012 running IIS 8
To learn how to customize your environment using configuration files, see Customizing and Configuring AWS Elastic Beanstalk Environments.
Currently, AWS Elastic Beanstalk does not support configuration files for Windows Server 2008 R2 running IIS 7.5, legacy Windows Server 2012 running IIS 8, legacy PHP 5.3, and legacy Tomcat 6 and 7 containers. If you want to customize your environment, you can create a custom Amazon Machine Image (AMI) that AWS Elastic Beanstalk uses for your applications. You do this by customizing the existing AWS Elastic Beanstalk AMI. For information, see Using Custom AMIs.
If you unsure if you are running a legacy container, then check the Elastic Beanstalk console to see if it is a legacy container type. For instructions, see To check if you are using a legacy container type.