Description |
This article describes how to troubleshoot FortiAnalyzer getting errors when uploading log files to an AWS S3 bucket. |
Scope | FortiAnalyzer. |
Solution |
Sample error when performing upload test to the S3 bucket:
diagnose test application uploadd 62 <connector> <remote path>
FAZ # diagnose test application uploadd 62 s3-bucket s3-bucket
2024-11-23 14:44:35 s1) copy file. uuid[670e7820-a966-11ef-b99b-004e656f3701]
2024-11-23 14:44:36 [T27953:cmd_proxy.c:394] 1732344276 proc[670e7820-a966-11ef-b99b-004e656f3701] result not ready 2024-11-23 14:44:36 s-) result not ready. uuid[670e7820-a966-11ef-b99b-004e656f3701] 2024-11-23 14:44:37 [T27953:cmd_proxy.c:399] 1732344277 got proc[670e7820-a966-11ef-b99b-004e656f3701] return code: 256 2024-11-23 14:44:37 s2) rc=256 message[unknown error]
For FortiAnalyzer cloud storage connector settings, refer to the following article: Technical Tip: FortiAnalyzer Cloud-out connector
Steps:
|
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.