在Amazon Linux 2实例的.ebextensions中创建apache.config配置Apache长连接参数未生效问题求助

Looks like you're hitting a common gotcha with Amazon Linux 2 Elastic Beanstalk's Apache configuration setup—AL2 changed how web server configs are handled compared to older Amazon Linux 1 environments. Let's walk through the most likely issues and fixes:

1. You're Using the Wrong Configuration Pattern for AL2 #

Amazon Linux 2-based EB environments prioritize the .platform directory for web server customizations over .ebextensions for many scenarios. Your current approach using .ebextensions/apache.config to create a file in /etc/httpd/conf.d might not trigger as expected because EB's AL2 setup has optimized paths for this.

Instead, restructure your project to use this layout at the root:

.platform/
└── httpd/
    └── conf.d/
        └── timeout.conf

Inside timeout.conf, drop the YAML wrapper and just add your Apache directives directly:

Timeout 300
KeepAliveTimeout 300

When you deploy this, EB will automatically copy this file to /etc/httpd/conf.d/ during the environment setup—no need to define file creation via YAML.

2. Double-Check Your .ebextensions Setup (If You Prefer That Route) #

If you want to stick with .ebextensions, verify these critical details:

• File placement & naming: Ensure apache.config is in the root .ebextensions folder (not a subfolder) and spelled correctly (no typos like .ebextension or apache.conf).
• YAML syntax: YAML is strict about spaces (tabs are invalid!). Your config must have proper indentation like this:

  files: 
    "/etc/httpd/conf.d/timeout.conf" : 
      mode: "000644"
      owner: root
      group: root
      content: |
        Timeout 300
        KeepAliveTimeout 300
  

• Redeploy after changes: Simply adding the file to your project won't apply it—you need to redeploy the environment. Use the eb deploy CLI command or click "Redeploy" in the Elastic Beanstalk console.

3. Check Deployment Logs for Clues #

Log into your EC2 instance and inspect these logs to pinpoint why the file wasn't created:

• /var/log/eb-engine.log: This log tracks every step of EB's deployment process. Look for entries related to your apache.config—you might see errors about invalid YAML, permission issues, or invalid paths.
• /var/log/httpd/error_log: If the file was created but Apache ignored it, this log will show syntax errors in your timeout.conf (unlikely here, but worth checking).

4. Verify Which Config Files Apache Is Loading #

Run this command on your instance to list every config file Apache is loading:

httpd -t -D DUMP_INCLUDES

If /etc/httpd/conf.d/timeout.conf isn't in the output, either EB failed to create it, or Apache isn't scanning that directory (the latter is rare for AL2's default Apache setup).

5. Rule Out Permission Issues #

If EB tried to create the file but hit a permission block, the eb-engine.log will show "permission denied" errors. EB runs deployment tasks as root, so this is unlikely unless you've modified the /etc/httpd/conf.d/ directory permissions in a previous config.

内容的提问来源于stack exchange，提问作者tomohiro