Hot answers tagged amazon-s3
It is possible, though not trivial, to setup NFS Clusters in Amazon EC2 using DRBD for synchronous replication and Pacemaker + Corosync for automating failover of the NFS service and exports between nodes (without interrupting client access). If you're planning on replicating synchronously ("real-time"), you'll need both your EC2 instances to be in the ...
You're probably hitting a bottleneck on the NAT instance. Driving 200 servers worth of large HTTP requests through the one server is probably taxing it too much (be it CPU or network bandwidth). Split your servers across multiple subnets with multiple NAT instances, or put them in a public subnet with direct networking to S3 rather than via a NAT.
Idea 1: If you type aws s3api help you'll see a lot of get-bucket-* commands that provide you with the bucket settings. You can plug these into the create-bucket and put-bucket-* commands for the target bucket. pros: fast, can be automated cons: some work to map all of the get output with put input, process needs to be updated as S3 bucket attributes are ...
That is actually a very recent feature of S3. You can now define endpoints with access policies in VPCs. See this blog post for more information: VPC Endpoint for Amazon S3
Only top voted, non community-wiki answers of a minimum length are eligible