Getting an error while uploading to s3 `options request denied upload` - amazon-s3

I'm uploading a file to s3 deep archive through the web dashboard and I get the following error options request denied upload. How do I fix or diagnose? I am not running an ad blocker, using safari and see no javascript errors in the console.

Try Removing Adblocker if any used in your browser and try to upload it. This surprisingly worked for me!

Related

Can't upload documents to CloudSearch

I'm trying to upload documents to my cloudsearch domain through AWS CLI using the following command:
aws cloudsearchdomain upload-documents --endpoint-url
http://doc-domainname-id.region.cloudsearch.amazonaws.com/2013-01-01/documents/batch
--content-type application/json --documents documents-batch.json
My access policies are open to everyone search and update but i'm still getting an exception when every time i try to upload a batch of documents:
An error occurred (CloudSearchException) when calling the
UploadDocuments operation: Request forbidden by administrative rules.
I've already uploaded files before using the same commands and everything was fine. Now i'm getting this issue.
Any help would be welcome. Thank you.

HTTP request sent, awaiting response... 403 Forbidden

Using wget to get a file from S3 via a presignedUrl, I can get the file in my local PC using
wget 'https:xxxxx' -O theFile
but when I tried to get the file in a remote (out of my control), It prompted me of this error:
Connecting to xxxx.s3-xxx.amazonaws.com (xxxx.s3-xxx.amazonaws.com)|52.219.68.171|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2018-09-12 09:50:57 ERROR 403: Forbidden.
Update 2018-09-13
Not only the presignedUrl, actually I cannot download it via aws s3 cp with credentials as
AWS_ACCESS_KEY_ID=AAA AWS_SECRET_ACCESS_KEY=BBB aws s3 cp hello.sh.yml s3://opt-prometheus-rules-test/ # to upload
AWS_ACCESS_KEY_ID=AAA AWS_SECRET_ACCESS_KEY=BBB aws s3 cp s3://opt-prometheus-rules-test/JmeterTest.jmx . # to download
In the end, it turned out that the problem lies in the access policy which is set wrongly to prohibited all the getting operations.
I contacted the administrator to solve the problem by modifying the access policy.
If your doubt on this error related to AWS S3 website hosting over linux server then continue reading.
Go to the AWS services S3 and click your created bucket and then click PERMISSIONS tab and the click EDIT option on the right side and then give READ access for Everyone (public access)'s Objects and Object ACL.
Below to this give acknowledge to your access I understand the effects of these changes on this object.
Give save changes. now go back to command prompt and your error will disappear.

CKAN resource file upload by api?

How do I upload file in to resource (either create or update)in CKAN using apis.
I followed the documentation it seems working but getting an error at datapusher page.
Click here for Image of Error
this error indicates a time-out when the datapusher service tries to download the resource from CKAN.
#florianm is dead right here.
Another thing to check is the resource url. The exception suggests you've forgotten to put http:// on the front of the url, or something similar.
Also note that you can upload files directly to CKAN if they are not already on-line somewhere else.
#Vithal this error indicates a time-out when the datapusher service tries to download the resource from CKAN.
Some pointers:
What do your CKAN and datapusher error logs say?
How big is your resource file?
Does this error occur when you upload a tiny CSV file?
Does this error occur when you upload your original resource file to
demo.ckan.org?

Amazon S3 suddenly stopped working with EC2 but working from localhost

Create folders and upload files to my S3 bucket stopped working.
The remote server returned an error: (403) Forbidden.
Everything seems to work previously as i did not change anything recently
After days of testing - i see that i am able to create folders in my bucket from localhost but same code doesnt work on the EC2 instance.
I must resolve the issue ASAP.
Thanks
diginotebooks
Does your EC2 instance have a role? If yes, what is this role? Is it possible that someone detached or modified a policy that was attached to it?
If your instance doesn't have a role, how do you upload files to S3? Using the AWS CLI tools? Same questions for the IAM profile used.
If you did not change anything - are you using the same IAM credentials from the server and localhost? May be related to this.
Just random thoughts...

Apache/nginx 403 when uploading new files

I've been stumped with this for a couple days now. I set up apache on my VPS and am uploading files frequently via FTP to my website. However, when I try to access those links in the browser, Apache gives me a 403 error. When I run the command "chmod 755" on the file and refresh, however, the file is accessed fine. I had the same error when I tried using nginx as my software. Thanks!
I had the same problem. Running command "chmod 755" solved problem but if user upload new file you need to run command again and again...
So I set the default permission for newly uploaded files in /etc/vsftpd.conf
file_open_mode=0755
local_umask=022