Dieser Inhalt ist in der ausgewählten Sprache nicht verfügbar
Wir arbeiten ständig daran, Inhalte in der ausgewählten Sprache bereitzustellen. Vielen Dank für deine Geduld.
How do I use .ebextensions to customize my Elastic Beanstalk environment?
Lesedauer: 3 Minute
0
I want to customize my AWS Elastic Beanstalk environment to create files, install packages, and run commands on Amazon Elastic Compute Cloud (Amazon EC2) instances.
To customize your environment, review the following these best practices:
Use the option_settings key to modify the environment configuration. You can choose from general options for all environments and platform specific options. Note: When you create or update an environment on the Elastic Beanstalk API, the client applies recommended values. Recommended values are directly set at the API level and have the highest precedence. You can't use the option_settings to change the configuration setting.
Precedence rules can stop the application of your option_settings modifications to the environment configuration. To remove the configurations directly applied during environment creation, use the update-environment command with the --options-to-remove flag. You can also use the Elastic Beanstalk API to run the command and make the update
If there are no option settings for your desired resource configuration, then use the Resources key to customize resources in your Elastic Beanstalk environment. Note: Resources defined in configuration files are added to the AWS CloudFormation template that's used to launch your environment. The CloudFormation template supports all CloudFormation resource types. For more information on logical resource names, see Modifying the resources that Elastic Beanstalk creates for your environment.
Use keys to customize software on Linux or Windows servers.
To apply your custom settings to your application, complete the following steps:
Create an application source bundle that includes your configuration files. Note: Folders that start with a period, such as .ebextensions, can be hidden by file browsers. To keep these folders visible, include the .ebextensions folder in the root of your application bundle when you create your application source bundle.