Home › Forums › AWS › AWS Certified Solutions Architect Professional › S3 is not file server › Reply To: S3 is not file server
-
Is Oracle redefining the concept of a “File Server” too, when they added REST endpoints to their “File Server” service?
https://docs.oracle.com/en/cloud/paas/integration-cloud/rest-api-fs/rest-endpoints.html
Moreover, have you read the new solutions right now in the market that uses Amazon S3 as a file system/server, such as S3FS-FUSE, ObjectiveFS, RioFS et cetera? Obviously, these solutions allow you to mount Amazon S3 as a File System, or sort of as a “file server” if you will:
https://cloud.netapp.com/blog/amazon-s3-as-a-file-system
Technically, a server that hosts your files and is accessible via RESTful APIs, is considering as “Object storage”, and not a “file server”. That’s my point here and I’m saying there’s an ambiguity in the commonly accepted definition of “file server” – it’s not limited to be a network-attached file server anymore that you connect to via LAN.
Case in point, we (Tutorials Dojo) are not redefining the definition of “file server” to make the provided answer here correct. I have provided ample evidence above of concrete, and already existing examples for your reference.
And once again, it’s clearly shown in the scenario that the main objective is to migrate the data over the weekend, where the methods are using:
– S3 sync
– S3 Multipart Upload
– Direct Connect
– Snowball
The scenario is not entirely about using Amazon S3 as a “file server”, but rather, using it to quickly migrate the data.
We’re always open to feedback to further improve our reviewers. As professionals, I think it’s healthy to have this kind of conversation as this is also a medium for both parties to learn. To avoid this kind of confusion once again, @Kenneth-Samonte-Tutorials-Dojo and will add the information I shared in this thread to the explanation of the question.
Thank you for your time and have a great week ahead!
Cheers,
Jon Bonso