ListObjectsV2 operation: Access Denied
See original GitHub issueHi,
I got strange behaviours when upgrading from 2.1.0 to 2.5.0.
On some DVC repo, I get an unexpected error - _find() got an unexpected keyword argument 'prefix' or a forbidden error 403 on other.
My setup is pretty simple, I have an s3 remote with AWS in each DVC repo and I simply add and push some data. Nothing fancy, no pipeline.
Setup:
Ubuntu 20.10 Python 3.8 DVC 2.1.0 or 2.5.0
Issue Analytics
- State:
- Created 2 years ago
- Comments:29 (10 by maintainers)
Top Results From Across the Web
Resolve Access Denied error for ListObjectsV2 using S3 sync
If the ListObjectsV2 permissions are properly granted, then check your sync command syntax. When using the sync command, you must include the -- ......
Read more >AccessDenied for ListObjects for S3 bucket when permissions ...
An error occurred (AccessDenied ) when calling the ListObjectsV2 operation: Access Denied. Using this form worked: aws s3 ls {bucket name}.
Read more >An error occurred (AccessDenied) when calling ... - AWS re:Post
An error occurred (AccessDenied ) when calling the ListObjectsV2 operation: Access Denied. 0. Just done creating a cluster and connecting to it.
Read more >S3 Access Denied when calling ListObjectsV2 | bobbyhadz
S3 Access Denied when calling ListObjectsV2 # · Open your AWS S3 console and click on your bucket's name · Click on the...
Read more >Why do I get an Access Denied error for ListObjectsV2 when I ...
Why do I get an Access Denied error for ListObjectsV2 when I run the sync command on my S3 bucket?
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Thanks! Ok, so something more complex is going on then. Will need to take a closer look.
CC @isidentical maybe you’ve run into this before.
okay, after some downgrade testing working on
2.1.0. and next version(2.2.0) it stop working