I’ll be honest. I love using AWS.
eb deploy is my go to command. The ElasticBeanstalk cloud ecosystem is amazing and I would find it hard to do my day job without it.
There is something to be said about the merry-go-round you are sent on when you need to change, upgrade, migrate (insert operative word here) a service your application relies on.
I recently moved a website from an Amazon Linux AMI to an Amazon Linux 2 platform. Along the way, I found out that Apache HTTPD was no longer the default proxy server  used on ElasticBeanstalk instances.
Additionally, and randomly, the following php.ini settings can be configured via the
aws:elasticbeanstalk:container:php:phpini option settings config namespace :
- Proxy server – The proxy server to use on your environment instances. By default, nginx is used.
- Document root – The folder that contains your site’s default page. If your welcome page is not at the root of your source bundle, specify the folder that contains it relative to the root path. For example, /public if the welcome page is in a folder named public.
- Memory limit – The maximum amount of memory that a script is allowed to allocate. For example, 512M.
- Zlib output compression – Set to On to compress responses.
- Allow URL fopen – Set to Off to prevent scripts from downloading files from remote locations.
- Display errors – Set to On to show internal error messages for debugging.
- Max execution time – The maximum time in seconds that a script is allowed to run before the environment terminates it.
E.g. you would set max_execution_time to 1000 by adding the following to your env.config file inside your .ebextensions folder:
option_settings: aws:elasticbeanstalk:container:php:phpini: max_execution_time: 1000
However, if you mistakenly assume you can also override
post_max_size, you will be presented with a deploy error during
2022-11-01 01:05:31 ERROR Invalid option specification (Namespace: 'aws:elasticbeanstalk:container:php:phpini', OptionName: 'post_max_size'): Unknown configuration setting.
Instead, to override other php.ini settings not included in the aforementioned list, you have to use the files block of a configuration file (e.g. .ebextensions/php-ini.config) to add a .ini file to /etc/php.d/:
files: "/etc/php.d/project.ini" : mode: "000644" owner: root group: root content: | upload_max_filesize = 64M post_max_size = 64M max_input_time = 1000 html_errors = "On" display_startup_errors = "On"
Similarly, you would use the same approach to enable a PHP extension like Mongo :
files: "/etc/php.d/99mongo.ini": mode: "000644" owner: root group: root content: | extension=mongo.so
Am I the only one frustrated with having to bore through multiple AWS docs articles to get to the bottom of the above while articles like Deploying a high-availability WordPress website with an external Amazon RDS database to Elastic Beanstalk don’t touch on the
eb deploy aspect at all?