Bartender Integration Builder - Amazon S3 Bucket access Error (403)
Hello
Within Bartender Integration builder I'm getting the following ERROR message when trying to access an Amazon S3 Bucket:
" Access Denied The remote server returned an error: (403) Forbidden. The remote server returned an error: (403) Forbidden."
Our IT department setup the Amazon S3 Bucket with subfolder and provide permissions.
I can access the S3 buckets via "S3 Browser" app without issue and have uploaded a single CSV file to the xxxCSV subfolder but still cannot get the Bartender Integration to run properly in test mode.
=============================================================================
Info:
Program: Seagull License Server 2016 R9; License: Automation (10 Printers); Version: 11.0.9.3160 (64-bit) OS; Windows 10 Enterprise x64 build 18363
Bartender Integration builder:(Added the Amazon S3 Storage)
- File Detection: Location: xxxBartenderxxx
- Folder to Scan: amazon://xxxBartenderxxx/us-east-1/ourbucketname/xxxCSV
The Bartender CSV File Integration works correctly as I first set it up on our local network. Afterward then switched the File Detection to Amazon S3 Storage.
=============================================================================
-
It could be a permissions issue as the integration will run using a local system account by default and that may not have access/rights to network resources. On the Print Document > Action tab try configuring to use a different user account that has these elevated permissions.
0 -
I have this same issue, have you ever solved this? Seems like the error is coming from the Amazon end?
0 -
So the resolution to our S3 issue was to setup a Windows 10 EC2 workstation. Where files were transferred from the S3 bucket direct to the folder storage on the EC2 workstation.
- Local ADMIN and RDP access was given to that Window 10 EC2 workstation.
- I then modified the integrations for, *.CSV file, pickup to point to the EC2 workstation folder
> Example:---> \\AWS_Win10EC2WorkStation_008\CSV-FilePickUp001
The Bartender Integrations worked just fine after that.
0
Please sign in to leave a comment.
Comments
3 comments