New answers tagged amazon-s3
In some cases, it could be routing problems that are outside Amazon's control, hence why it won't show up on their status pages as being a problem. Look into using multiple regions for S3 or using Cloudfront instead. Since this case may be specific to your configuration, contacting Amazon about the problem would be the first step in resolving this, although ...
The AWS CLI now supports the --query parameter which takes a JMESPath expressions. This means you can sum the size values given by list-objects using sum(Contents.Size) and count like length(Contents). This can be be run using the official AWS CLI as below and was introduced in Feb 2014 aws s3api list-objects --bucket BUCKETNAME --output json ...
S3 is a scalable service. There is nothing to be done on your side. For instances, you would want to use elastic beanstalk. It allows autoscale on certain metrics like cpu utilization, network io etc. This is essentially to add more application servers when your load exceeds one of these thresholds.
You don't need to auto scale Amazon S3 buckets, this is on it's side. What you have to do is to scale up the EC2 instance. I suggest you to read AUTOSCALING YOUR WEBSITE WITH AMAZON WEB SERVICES – PART 1 and AUTO SCALING YOUR WEBSITE WITH AMAZON WEB SERVICES (AWS) – PART 2 where it is really well explained step by step.
The problem is that S3 doesn't allow you to append to an existing S3 object, so all of a sudden, a thousand lines from one machine's log are now a thousand S3 objects--gulp! S3 doesn't deal well with lots of small files, and your costs will quickly skyrocket. You could replace the object (get the existing object, add the new line, re-submit), but this is ...
These are hints from http://blog.celingest.com/en/2013/12/12/cloudfront-configuring-custom-error-pages/ You need to add another CloudFront origin pointing to the bucket where your error page is The cache behaviour of the newly-created origin should have a Path Pattern pointing to the folder (in the error page bucket) where the error pages reside You can ...
It's because you are aliasing to an endpoint, not your specific resource. s3-website-us-east-1.amazonaws.com is the correct value, assuming your bucket lives in us stanard region. http://docs.aws.amazon.com/AmazonS3/latest/dev/website-hosting-custom-domain-walkthrough.html#root-domain-walkthrough-switch-to-route53-as-dnsprovider
If you need a full system backup, you could switch to snapshots... if you need individual files, have you looked at AWS CLI tools? If it's an Amazon Linux instance, they're already installed. If not, see install instructions here. You could set a scheduled job using a command something along these lines: aws s3 sync /your/path/to/backup ...
Top 50 recent answers are included