0

I have Apache installed on my server (AWS EC2 instance that is used by Elastic Beanstalk). There is the main configuration file httpd.conf that contains two configuration properties:

Timeout 60
KeepAliveTimeout 60

I need to change these parameters, but there is a problem that this main configuration file is overwritten after each application deploy. So any my changes are lost after some time (and default values are restored then).

I found that I can add another configuration file and put it in conf.d directory so that Apache will load this file as well. So I want to create such file (let's say conf.d/custom.conf) and put these two parameters here, but with changed values:

Timeout 180
KeepAliveTimeout 180

The main httpd.conf file contains the following lines as well:

Include conf.d/*.conf
Include conf.d/elasticbeanstalk/*.conf

And these lines are placed after Timeout and KeepAliveTimeout options.

So, the question is: will options from a custom conf file override the options from the main file? As a result I want to have Timeout=180 and KeepAliveTimeout=180.

1
  • If I remember it properly Beanstalk kills instance each time during rebuild so your additional files will be lost. There definitely is a way to supply customization but I don't know, sorry. I prefer CloudFormation.
    – Putnik
    Jul 21, 2017 at 19:47

1 Answer 1

0

If you want to personalize your Elastic Beanstalk environment and to make those changes permanent, I suggest taking a look at ebextensions. Also, take a look at the values AWS recommends for Apache back-ends running behind an ELB.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .