microsoft / microsoft/PowerPlatformConnectors
[BUG] <title>Access Denied Error in Uploading multiple files is S3 Buckets
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.3k
- Forks
- 1.5k
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 11
Description
Type of Connector
Independent Publisher Connector
Name of Connector
Amazon S3 Bucket
Describe the bug
If the running the upload operation in loop I am getting Access denied error in Put operation .If i run the file separately (single file) I do not get any issues. Error is coming randomly
Is this a security bug?
No, this is not a security bug
What is the severity of this bug?
Severity 1 - Connector is broken or there's a very serious issue
To Reproduce
Upload 10-15 files from SharePoint to AWS S3 bucket using the connector
Expected behavior
Access Denied error should not come
Environment summary
Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build)
CLI version (paconn --version)
OS version
Shell Type (e.g. bash, cmd.exe, Bash on Windows)
Additional context
If the running the upload operation in loop I am getting Access denied error in Put operation .If i run the file separately (single file) I do not get any issues. Error is coming randomly
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file, test, or entry point is named. Start by reproducing the Amazon S3 Put operation with 10–15 SharePoint files in a loop, then compare it with a single-file upload and capture the intermittent authorization failure; done means repeated loop uploads complete without Access Denied errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100