New answers tagged amazon-ami
Yes, you can modify the volume type / size / IOPS when you launch any instance using the created AMI.
To resolve this issue: Remove the lines like: mysqlnd_ms.enable=1 mysqlnd_ms.force_config_usage=1 mysqlnd_ms.config_file=/etc/mysqlnd_ms_cfg.ini extension=mysqlnd_ms.so from the php.ini file Create a new file called /etc/php.d/mysqlnd_ms.ini and put those lines in there and restart php-fpm service php-fpm restart
The volume type you specify for the AMI becomes the default volume type for launches. The EC2 console does make it easy to select what volume type you want when you launch, but support for that varies across client tools. The Amazon Linux AMI makes their EBS-backed AMIs available for both Magnetic and General Purpose SSD by default: $ aws ec2 ...
I can't really explain the behaviour you're experiencing, but AWS themselves are recommending that you should not use fstab entries but instead make use of RC init scripts. See quote below from Cindy@AWS. This forum post is pretty old though and is not really an answer to the same issue you have, but maybe doing it this way will solve your issue as well. ...
My issue was I was using user "ubuntu" instead of "ec2-user" on the Amazon Linux AMIs, May help a future googler.
Top 50 recent answers are included