2回答
- 新しい順
- 投票が多い順
- コメントが多い順
1
IAM role permissions for S3 looks good. Generally, when using smbguest
as file share authentication method, by default the file permissions are smbguest
user and group and reading the files should have no issues.
May I know the below:
- Can you confirm, the windows client has not connectivity issues to the Storage Gateway on port 445 ?
You can test the connectivity using
telnet
orTestNetConnection
. - Is the file share created with existing files on the S3 bucket. If so how are the files copied to the S3 bucket? What are the file permissions when you see on the windows explorer ?
- Does your work flow or use case requires direct access to the S3 bucket for data copy/upload ?
- Based on what you mentioned about time stamps being updated to current date when viewed/accessed from the windows explorer. Do you have automated cache refresh enabled on the file share ? Generally, this behavior is seen when objects are uploaded directly to S3 and gateway tries to refresh the contents from S3 for the first time.
Based on the description and the error messages you were receiving when reading the file, I would recommend to please to open a case with support to have it investigated further.
回答済み 1ヶ月前
0
Cause of Issue: Amazon Connect outputting files to the S3 bucket utilizing a naming convention including a ":" (Colon) which is a reserved character within Windows.
回答済み 1ヶ月前
関連するコンテンツ
- AWS公式更新しました 2年前
- AWS公式更新しました 2年前
- AWS公式更新しました 2年前
Hello, thank you for your input, Harshi. The issue has been identified. The issue is as follows: Amazon Connect output files are including a ":" in the initial naming convention of the files resulting in error with Windows File System.