

You can basically take a file from one s3 bucket and copy it to another in another account by directly interacting with s3 API.

Recently i had a requirement where files needed to be copied from one s3 bucket to another s3 bucket in another aws account.
Aws s3 copy from one bucket to another download#
If a user in an aws account has proper permissions to upload and download stuff from multiple buckets in that account, you can pretty much copy files between buckets as well(well buckets in the same account). It also offloads the responsibility of serving files from the application to the AWS S3 API. S3 takes care of scaling the backend storage as per your requirement, and your application needs to be programmed to interact with it. Which means, if somebody in the world has a bucket named mybucket, you cannot have a bucket with that name. Always remember the fact that the name space for bucket name is common in the whole of s3 across all accounts. You can use aws cli, or other command line tools to interact/store/retrieve files from a bucket of your interest. You can have as many buckets as you want.

You need an Access Key and Secret Key pair to do operations on an s3 bucket.īucket is nothing but a construct to uniquely identify a place in s3 for you to store and retrieve files. It's also highly secure, and access is only granted on a policy based method for aws user accounts(also called IAM accounts). Usually applications can directly interact with S3 API to store and retrieve files. You can use s3 for storing media files, backups, text files, and pretty much everything other than something like a database storage. It has a good reputation of infinite scalability and uptime. Simple Storage Service(s3) offering from AWS is pretty solid when it comes to file storage and retrieval.
