A financial services firm runs a containerized microservices application deployed on Amazon ECS across three Availability Zones. The container tasks require concurrent read and write access to a shared directory containing transaction log templates. The storage system must provide POSIX-compliant access, scale throughput up to during peak trading hours, and support concurrent connections from hundreds of containers. Which configuration options should a solutions architect select to meet these requirements? (Select TWO.)
- Create an Amazon Elastic File System (Amazon EFS) and configure it to use Elastic Throughput mode.Cevap
- Configure the Amazon ECS task definitions to mount the Amazon EFS volume using the EFS volume configuration.Cevap
- CProvision an Amazon EBS gp3 volume and enable Multi-Attach to share the filesystem across all container tasks.
- DConfigure an Amazon EBS io2 volume with Multi-Attach enabled, formatted with a standard ext4 filesystem, and mount it to the tasks.
- EDeploy a single Amazon EBS io2 Block Express volume and configure the container tasks to access it concurrently using a standard Network File System (NFS) client.
Cevap
The solutions architect should create an Amazon Elastic File System (Amazon EFS) configured with Elastic Throughput mode, and mount the Amazon EFS volume inside the Amazon ECS task definitions.
The requirements dictate concurrent, POSIX-compliant read and write access across three Availability Zones with spiky throughput needs. Amazon EFS provides serverless, highly available, shared file systems that can be concurrently mounted by hundreds of container tasks. Configuring it with Elastic Throughput mode allows the throughput to scale dynamically up to without pre-provisioning capacity. Standard ECS task configurations natively support mounting EFS volumes.
Adım Adım Çözüm
Anahtar Kavram
Selecting and integrating high-performing, scalable, and shared POSIX storage for containerized applications running across multiple Availability Zones.