EFS should be independent of lifecycle of elasticbean environment

The [tutorial for Deploying a High-Availability WordPress Website](https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/php-hawordpress-tutorial.html) talks about creating an RDS instance external to the elasticbean. The tutorial uses an EFS that is created using [efs-mount in .ebextensions](https://github.com/awslabs/eb-php-wordpress/blob/8e5a386b56923443fd35ad9824db87f99faace64/.ebextensions/efs-create.config#L1) and is symlinked to ``wp-content/uploads``. The ``uploads`` directory in wordpress is used to store the media files.

Since this EFS volume is created through elasticbean, what this means is that if the EB is terminated, the files stored on ``uploads`` are deleted as well. The intent is that the ``uploads`` directory has non-ephemeral files that need to shared across all the instances. Deleting the files when the instance terminates is counter to this intent.

To be consistent, I think both the EFS and RDS should be created outside the elasticbean environment.

Bắt đầu với AWS High-Availability WordPress tutorial và .ebextensions/efs-create.config, sau đó theo dõi cách volume EFS được tạo và liên kết với wp-content/uploads. So sánh vòng đời đó với instance RDS được tạo bên ngoài. Hoàn thành khi EFS của uploads nằm bên ngoài môi trường Elastic Beanstalk và vẫn tồn tại khi môi trường bị chấm dứt.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.