Some of the key architecture decisions regarding hybrid integration are with reference to FileShare between the cloud and on-prem systems/users.
Introduction
As we move/migrate applications from on-prem to the cloud, some of the key architecture decisions regarding hybrid integration are with reference to FileShare between the cloud and on-prem systems/users.
When a part of the ecosystem goes to the cloud, it’s important to have the file sharing seamless, efficient, and performant yet cost-effective — driven by a cloud-native solution approach.
The decision to use a target solution for FileShare varies by use case. This document provides insight into various use cases of file-based integration, services offered by AWS, potential technical debt, and solution approaches. The technical debt referred to here is related to the presence of a solution component in the on-prem data center. The removal of these technical debts is critical to the closure of the data center as well as very high license fees and infra costs associated with resources.
Use cases are primarily categorized into the following:
User to/from system using FileShare
System to/from system using FileShare User and Operational Impact
It needs to be noted that there may be operational changes in scenarios of how users used to upload/download files without compromising authentication/authorization or access related to security. A user operations handbook is created for these solution patterns, and users have trained in the Sandbox environment. These users are business users, and the solution patterns and operational changes are agreed upon with them before design and implementation. Overview — File-Based Integration and AWS Solution OptionsS3 FileGateway: How It Works
AWS S3 FileGateway needs an on-prem appliance (VM). It acts as S3 FileGateway(FG) server
The on-prem systems/users create an SMB Fileshare with this server’s specific folders
The FileGateway server, on another side, integrates with S3.
