[AMI Updates] JIN-kEI (Auto-Scaling) now supports PHP7 and CloudWatch Logs!

We have updated our JIN-KEI (Auto-Scaling) architecture.
Since today’s update, some configurations on PHP and Nginx became customisable; you can monitor exported logs through CloudWatch Logs and EC2 System Manager, and also handle with them through command line interface.


PHP7 Standard

      ___         _            __
     / _ | __ _  (_)_ _  ___  / /____
    / __ |/  ' \/ /  ' \/ _ \/ __/ _ \
   /_/ |_/_/_/_/_/_/_/_/\___/\__/\___/


 Nginx 1.11.9, PHP 7.0.15, Percona MySQL 5.6.34, WP-CLI 1.0.0

 amimoto     /
 digitalcube https://en.digitalcube.jp/

On the latest version of JIN-KEI (Auto-Scaling), PHP7 became standard for PHP.

Using AWS Certificate Manager with JIN-KEI, you can quickly build PHP7 + HTTP/2 enabled servers.

CloudWatch Logs Ready

You need to create a framework to collect tonnes of log files. JIN-KEI (Auto-Scaling) automatically gather and transfer the following logs to CloudWatch Logs by default. This new feature makes you much easier to check logs of your websites, quickly start analysing them with Amazon Elasticsearch Service.

Logs will be gathered
  • /var/log/messages
  • /var/log/php-fpm/www-error.log
  • /var/log/nginx/{instance_id}.backend.access.log
  • /var/log/nginx/{instance_id}.access.log
  • /var/log/nginx/{instance_id}.error.log

Customisable configuration of PHP and Nginx

You can customise some configuration of PHP and Nginx when you started CloudFormation. No need to login to the server and configure it via SSH, after you started it up.

Configure it with starting up page of CloudFormation
Configure it with starting up page of CloudFormation.
Complete list of the customisable value on CloudFormation
CloudFormation Parameters Name Description Default
PHPMemoryLimit Modify memory limit of PHP (memory_limit) 128M
NginxClientMaxBodySite Modify client_max_body_size on Nginx 4MB
IsMobileDetect Enabling UA detectives via WordPress disabled
WPIsMultiSite Modifying Nginx value to enable creating WordPerss Multi-site. disabled

EC2 System Manager support

The system will install EC2 System Manager to the JIN-KEI (Auto-Scaling) enabled instance by default. You may handle running instance through the manager so easily.

Other updates

  • Enable SSH access through ELB
  • Integrate EC2 instances under the AutoScaling Group
  • No more adding credentials to S3/CloudFront when you connect them.
  • Update OS to the latest on our AMI: AMIMOTO (Auto-Scaling ready)

How to start JIN-KEI (Auto-Scaling)

You can start it through WordPress Powered by AMIMOTO (Auto-Scaling ready) on AWS Marketplace.
Choose [Delivery Methods] -> [WordPress powered by JIN-KEI (Auto-Scaling)], then set it up using startup wizard.

How to upgrade to the latest

After downloading the template, patch updates to your running CloudFront.
The URL of updated CloudFormation Template:

[Warning] Some resources will be removed by updating CloudFormation.

During the upgrade process, CloudFormatin will eliminate some resource. If it removed EC2, RDS, EFS or S3, you would lose your stored data permanently.

For more updating CloudFormation, check AWS’ official document:
Update Behaviors of Stack Resources