- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Hi Sharath, thanks for your question. Before we write a new object, we attempt to determine if an object with the same name already exists and, if it does, whether it represents a directory. In a normal filesystem, trying to write file 'XYZ' when directory 'XYZ/' already exists would fail. In S3, it would allow you to create both objects, 'XYZ' and 'XYZ/'. Unfortunately, AWS Transfer Family doesn't have good way to represent this state. We try to avoid this state altogether since either the file or directory would end up masked at SFTP level. We recognize this limitation and are exploring possible solutions, such as "read only" and "write only" flags at the SFTP server level. Please let us know if a feature like this would be useful.
In the meantime, you may be able to achieve this end user experience by using AWS Transfer Family managed workflows. Specifically, workflows allow you to copy incoming files to new directories and delete the original file, resulting in an 'upload only' type experience. You can learn more about managed workflows here.
Contenuto pertinente
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa