Which solution meets these requirements MOST cost-effectively?
Create a new S3 bucket. Deploy an AWS Storage Gateway file gateway within the VPC that is connected to the Direct Connect connection. Create a new SMB file share. Write nightly database exports to the new SMB file share.
Create an Amazon FSx for Windows File Server Single-AZ file system within the VPC that is connected to the Direct Connect connection. Create a new SMB file share. Write nightly database exports to an SMB file share on the Amazon FSx file system. Enable nightly backups.
Create an Amazon FSx for Windows File Server Multi-AZ file system within the VPC that is connected to the Direct Connect connection. Create a new SMB file share. Write nightly database exports to an SMB file share on the Amazon FSx file system. Enable nightly backups.
Create a new S3 bucket. Deploy an AWS Storage Gateway volume gateway within the VPC that is connected to the Direct Connect connection. Create a new SMB file share. Write nightly database exports to the new SMB file share on the volume gateway, and automate copies of this data to an S3 bucket.
Explanations:
A file gateway provides a local cache of frequently accessed data and asynchronously uploads data to S3. This is a cost-effective way to move backups to S3, especially with a Direct Connect connection. The nightly exports can be written to the file share, and the gateway will handle the transfer to S3.
Amazon FSx for Windows File Server is a fully managed Windows file server in AWS, suitable for applications that require native Windows file system compatibility. It’s not designed for simply storing backups and is more expensive than using S3 directly or with a file gateway. Single-AZ deployments do not offer high availability.
A Multi-AZ Amazon FSx for Windows File Server provides high availability, but it’s even more expensive than a Single-AZ deployment and is still not the most cost-effective solution for storing backups. The high availability is unnecessary for backups.
A volume gateway presents cloud-based iSCSI volumes to on-premises applications. This is not suitable for writing file-based backups. The file gateway option (A) is the correct storage gateway type for this use case. Automating copies to S3 is also redundant, as the file gateway already handles the transfer to S3.
As far as I can tell, the answer is:
Create a new S3 bucket. Deploy an AWS Storage Gateway file gateway within the VPC that is connected to the Direct Connect connection. Create a new SMB file share. Write nightly database exports to the new SMB file share.