How can the company migrate the web infrastructure to AWS without delaying the content refresh process?

By:
In: SAP-C01
Tagged:
With: 1 Comment
A company has an existing on-premises three-tier web application.The Linux web servers serve content from a centralized file share on a NAS server because the content is refreshed several times a day from various sources.The existing infrastructure is not optimized and the company would like to move to AWS in order to gain the ability to scale resources up and down in response to load.On-premises and AWS resources are connected using AWS Direct Connect.

How can the company migrate the web infrastructure to AWS without delaying the content refresh process?

Create a cluster of web server Amazon EC2 instances behind a Classic Load Balancer on AWS. Share an Amazon EBS volume among all instances for the content. Schedule a periodic synchronization of this volume and the NAS server.

Create an on-premises file gateway using AWS Storage Gateway to replace the NAS server and replicate content to AWS. On the AWS side, mount the same Storage Gateway bucket to each web server Amazon EC2 instance to serve the content.

Expose an Amazon EFS share to on-premises users to serve as the NAS serve. Mount the same EFS share to the web server Amazon EC2 instances to serve the content.

Create web server Amazon EC2 instances on AWS in an Auto Scaling group. Configure a nightly process where the web server instances are updated from the NAS server.

Explanations:

Sharing an Amazon EBS volume among multiple EC2 instances is not feasible, as EBS volumes can only be attached to a single EC2 instance at a time. This would complicate the content refresh process and could lead to delays in accessing updated content.

While using an on-premises file gateway with AWS Storage Gateway allows for integration with AWS services, it may introduce latency due to the necessity of replicating data to AWS. This could delay the content refresh process as the web servers rely on data being immediately available.

Amazon EFS provides a fully managed file system that can be accessed concurrently by multiple EC2 instances. It allows for seamless scaling and immediate access to updated content, ensuring that the content refresh process is not delayed.

A nightly update process would result in delays since the content would not be refreshed throughout the day. This option fails to meet the requirement of maintaining an up-to-date content refresh process for the web application.

2025-10-12

1 Comment

  1. Olivia
    Author

    I compute that the answer is:
    Expose an Amazon EFS share to on-premises users to serve as the NAS serve. Mount the same EFS share to the web server Amazon EC2 instances to serve the content.

Leave a Reply

Your email address will not be published. Required fields are marked *

9 + 3 =