You can set a bucket policy as detailed in this blog post: http://ariejan.net/2010/12/24/public-readable-amazon-s3-bucket-policy/ As per @robbyt’s suggestion, create a bucket policy with the following JSON: { “Version”: “2008-10-17”, “Statement”: [ { “Sid”: “AllowPublicRead”, “Effect”: “Allow”, “Principal”: { “AWS”: “*” }, “Action”: [ “s3:GetObject” ], “Resource”: [ “arn:aws:s3:::bucket/*” ] } ] } Important: replace bucket in … Read more
In boto 3, the ‘Key.set_contents_from_’ methods were replaced by Object.put() Client.put_object() For example: import boto3 some_binary_data = b’Here we have some data’ more_binary_data = b’Here we have some more data’ # Method 1: Object.put() s3 = boto3.resource(‘s3’) object = s3.Object(‘my_bucket_name’, ‘my/key/including/filename.txt’) object.put(Body=some_binary_data) # Method 2: Client.put_object() client = boto3.client(‘s3′) client.put_object(Body=more_binary_data, Bucket=”my_bucket_name”, Key=’my/key/including/anotherfilename.txt’) Alternatively, the binary … Read more
The letter change on the URI scheme makes a big difference because it causes different software to be used to interface to S3. Somewhat like the difference between http and https – it’s only a one-letter change, but it triggers a big difference in behavior. The difference between s3 and s3n/s3a is that s3 is … Read more
I’m not sure if you have already solved it. I had the same issue. It’s because AWS S3 is looking for that folder (projects) to serve from, which you don’t have. Simply point Error document to index.html. This worked for me. You can handle error pages in react-router.
I think what you want is Browser-Based Uploads Using POST. Basically, you do need server-side code, but all it does is generate signed policies. Once the client-side code has the signed policy, it can upload using POST directly to S3 without the data going through your server. Here’s the official doc links: Diagram: http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingHTTPPOST.html Example … Read more
After two days of debugging, I finally discovered the problem… The key I was assigning to the object started with a period i.e. ..\images\ABC.jpg, and this caused the error to occur. I wish the API provides more meaningful and relevant error message, alas, I hope this will help someone else out there!
There is no concept of folders or directories in S3. You can create file names like “abc/xys/uvw/123.jpg”, which many S3 access tools like S3Fox show like a directory structure, but it’s actually just a single file in a bucket.
You’ll just need two models. One for the Post and the other would be for the Images. Your image model would have a foreignkey to the Post model: from django.db import models from django.contrib.auth.models import User from django.template.defaultfilters import slugify class Post(models.Model): user = models.ForeignKey(User) title = models.CharField(max_length=128) body = models.CharField(max_length=400) def get_image_filename(instance, filename): title … Read more
Wrap the S3 upload() function with the node.js stream.PassThrough() stream. Here’s an example: inputStream .pipe(uploadFromStream(s3)); function uploadFromStream(s3) { var pass = new stream.PassThrough(); var params = {Bucket: BUCKET, Key: KEY, Body: pass}; s3.upload(params, function(err, data) { console.log(err, data); }); return pass; }
You have successfully transfered the domain to Gandi, but your domain is still configured with GD nameservers. Check this: Log in to your AWS web console Select Route53 service Select Hosted Zones in the left pane Select verticeinteractive.co.uk (but do not click on the domain name, just select the radio button) Notice the 4 name … Read more