Which solution meets these requirements?
Use AWS Snowball to migrate data out of the on-premises solution to Amazon S3. Configure on-premises systems to mount the Snowball S3 endpoint to provide local access to the data.
Use AWS Snowball Edge to migrate data out of the on-premises solution to Amazon S3. Use the Snowball Edge file interface to provide on-premises systems with local access to the data.
Use AWS Storage Gateway and configure a cached volume gateway. Run the Storage Gateway software appliance on premises and configure a percentage of data to cache locally. Mount the gateway storage volumes to provide local access to the data.
Use AWS Storage Gateway and configure a stored volume gateway. Run the Storage Gateway software appliance on premises and map the gateway storage volumes to on-premises storage. Mount the gateway storage volumes to provide local access to the data.
Explanations:
AWS Snowball is designed for one-time data transfer to AWS. It does not provide ongoing local access or continuous backup solutions and cannot serve as a mounted storage endpoint for regular access.
AWS Snowball Edge supports local storage with a file interface temporarily, but it is not a long-term or continuous backup solution. It also lacks the automatic sync capability needed for ongoing backups to Amazon S3.
Cached volume gateways in AWS Storage Gateway primarily store data in AWS and cache only frequently accessed data locally, meaning most data access relies on the cloud. This does not fully satisfy the requirement for maintaining comprehensive local data access.
Stored volume gateways in AWS Storage Gateway keep a full copy of the data locally while asynchronously backing up to AWS. This configuration ensures automatic, secure data transfer to AWS while maintaining full local access.
I conclude that the answer is:
Use AWS Storage Gateway and configure a stored volume gateway. Run the Storage Gateway software appliance on premises and map the gateway storage volumes to on-premises storage. Mount the gateway storage volumes to provide local access to the data.
I reckon the answer is:
Use AWS Storage Gateway and configure a stored volume gateway. Run the Storage Gateway software appliance on premises and map the gateway storage volumes to on-premises storage. Mount the gateway storage volumes to provide local access to the data.