Deploy AWS Outposts with Amazon S3 storage. Configure a Windows Amazon EC2 instance on Outposts as a file server.
Deploy an Amazon FSx File Gateway. Configure an Amazon FSx for Windows File Server Multi-AZ file system that uses SSD storage.
Deploy an Amazon S3 File Gateway. Configure the S3 File Gateway to use Amazon S3 Standard-Infrequent Access (S3 Standard-IA) for the metadata files and to use S3 Glacier Deep Archive for the image files.
Deploy an Amazon S3 File Gateway. Configure the S3 File Gateway to use Amazon S3 Standard-Infrequent Access (S3 Standard-IA) for the metadata files and image files.
Explanations:
AWS Outposts provides on-premises AWS infrastructure but requires additional complexity. It also does not offer SMB support for file shares as needed by the scenario.
Amazon FSx File Gateway is not designed for this use case; it is primarily used for hybrid storage and doesn’t directly support the requirement of SMB access from both data centers and AWS.
S3 File Gateway cannot offer SMB access, and Glacier Deep Archive would be too slow to meet the 5-minute retrieval requirement for image files.
S3 File Gateway provides SMB access, supports the use of S3 Standard-IA for metadata files, and offers the flexibility to meet the 5-minute retrieval time, though S3 Standard-IA for both file types is suboptimal.
If I’m correct, the answer is:
Deploy an Amazon S3 File Gateway. Configure the S3 File Gateway to use Amazon S3 Standard-Infrequent Access (S3 Standard-IA) for the metadata files and image files.