Which action should be taken?
Create an Amazon EFS file system with the performance mode set to Max I/O. Configure the EC2 operating system to mount the EFS file system.
Create an Amazon EFS file system with the throughput mode set to Provisioned. Configure the EC2 operating system to mount the EFS file system.
Update the EC2 launch template to allocate a new 1-TB EBS General Purpose SSO (gp2) volume.
Update the EC2 launch template to exclude the PIOPS volume. Configure the application to use local instance storage.
Explanations:
Amazon EFS is designed for scalability and shared access but may not meet the low latency and high IOPS requirements needed for this application, especially at the specified level of 3,000 IOPS.
While provisioning an Amazon EFS file system with Provisioned Throughput might increase performance, it does not guarantee the same low latency and random access characteristics as an EBS volume configured for PIOPS. It is generally less suited for high IOPS workloads compared to EBS.
Updating to a 1-TB EBS General Purpose SSD (gp2) volume would provide adequate performance (up to 16,000 IOPS depending on the size) while lowering costs compared to PIOPS volumes. General Purpose SSDs are suitable for applications requiring a balance of price and performance.
Using local instance storage may improve performance, but it compromises durability and availability, as data stored on local storage is not persistent. This would not meet the durability requirement of the application and is generally not advisable for critical data.
I conclude that the answer is:
Update the EC2 launch template to allocate a new 1-TB EBS General Purpose SSO (gp2) volume.