3 ms·
My use case is different. I want to put data into S3, but want it only accessible on my instances in the VPC, none of which I want to have access to the outsid
by Patrick_Devine 13y ago
My use case is different. I want to put data into S3, but want it only accessible on my instances in the VPC, none of which I want to have access to the outside world.
I realize many people probably don't have this particular need, however, I don't think it's completely unreasonable. Instead, I'm just mounting an EBS volume on an instance and running nginx to serve files.
- toomuchtodo 13y ago> My use case is different. I want to put data into S3, but want it only accessible on my instances in the VPC, none of which I want to have access to the outside world. Which you can still do, by using bucket policies/permissions in S3 (specifically EC2 IAM roles in this scenario). I think we're arguing different use cases though. If your content is only used or getting served from one machine, EBS volumes. If you need to have it served to the world, available to multiple instances, etc, S3.