AWS Elastic Beanstalk supports a number of configuration options , these options allow you to modify the settings of resources applied to the environment. Some of these options have default values, these values can be overridden to customize the environment. Other options can be configured to activate additional functions.
Elastic Beanstalk supports two methods for configuration option to save. YAML or JSON format configuration file can be placed in the source code of the application program (in a named directory), and as part of the application deployment source packet. You can create and manage configuration files locally..ebextensions
You saved configuration is created and stored in Elastic Beanstalk environment by running the option or JSON file template. Save the existing configuration can also be extended to create a new configuration.
note
After the configuration of the priorities defined in the configuration settings and configuration files saved or created in the environment is lower than the set creation process (including the Elastic Beanstalk console and EB CLI recommended value of the application). For more information, please refer to the order of priority .
Options can also be specified in a JSON document, and create or provide direct environment of updates to Elastic Beanstalk using the EB CLI or AWS CLI. This option provides a direct method to Elastic Beanstalk will cover all other methods.
Profile ( ).ebextensions
Use .ebextensions configurable options for the desired application uptime, and to be at a higher priority to provide default values are the other options on the level of coverage. .ebextensions The lowest order of priority specified in the options, by any other level of coverage settings.
To use the configuration file, create a project named in the source code top-level .ebextensions folder. Add a extension .config of the file and press the following ways to specify options: