Would it be possible for you to share the actual command or code that you executed?
If sometimes it succeeds, but sometimes it fails, it could be a problem around the network.
The internet is a big place; there are likely many networks between your computer and AWS. It's possible that there is a problem with an AWS service (S3 in this case) but it's also possible that there is packet loss on a network between you and AWS that is causing the problem. You may not see packet loss to other destinations because the path to there is different; you may also be crossing a network that is rate limiting traffic to or from AWS. It's very difficult to tell because all of those networks are controlled by different entities.
If this is an ongoing issue and it is detrimental to your usage of AWS, please create a support case so that the team can investigate.
thx. Is there a way I can pin point down which steps in that whole process just roughly?
You might try running a tool like MTR - it provides (somewhat) real-time statistics on the path between you and a destination - think of it as "traceroute on steroids". It's still not perfect because packet loss is not always related to path detection/testing. But it's something.
- asked 3 years ago
- Accepted Answerasked 6 years ago
- asked a year ago
- AWS OFFICIALUpdated 3 days ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a year ago
- How can I troubleshoot the "Could not connect to the endpoint URL" error when I run the sync command on my Amazon S3 bucket?AWS OFFICIALUpdated 2 years ago
- EXPERTpublished 5 months ago
sure, the actual code is just
aws s3 cp <local-file-dir> <s3-dir>
Thanks for sharing. There did not seem to be anything wrong with the commands themselves. If you add "--debug" to the command options, you can check the debug log and possibly find something that will help you resolve the error.