For example, if you store in West VA, and COPY to the Northern CA region, that incurs cost. All corrections are welcome.Īmazon's FAQ is here: and I'll reference this below.ĬOPY can be several things, one of which is copying between regions which does cost.
I’m also including WHERE I discovered it (wanted to get it all from Amazon). So what I learned about PUT/COPY/POST/LIST and GET Requests while digging in to assess our costs. I also found references to POST and LIST see below. It is putting a file (without reference to size).ĪLSO, COPY indeed is copying files within S3, but there’s more. I was watching for whether PUT was per file or per some packet size which would make it more difficult to price. PUT is uploading (specifically one file is one PUT). Taking a look into S3 REST API, though, I assume get_bucket_filesize() is implemented as a LIST (a GET operation on a bucket brings, along with some more data, the size of each object in the response) and get_object_filesize() is implemented as a GET (using the HEAD operation on a single file also brings its size included in the metadata). My argument is that it is possible to implement a download using a GET, an upload using a PUT or a POST, and so forth. Of course these assumptions depend on which SDK you are using (it seems you're using the PHP one) and its underlying implementation.
You have not asked, but a GET is the download of a file from S3 and DELETE would obviously be the deletion of a file. POST is an alternate form of PUT that enables browser-based uploads asĮvery time you, for example, get the contents of a given S3 bucket, you're running into a LIST operation.
#SOCCER SPIRITS TIER LIST S3 UPDATE#
From my experience using S3 (and also from the basics of HTTP protocol and REST), POST is the creation of a new object (in S3, it would be the upload of a new file), and PUT is a creation of a new object or update of an existing object (i.e., creation or update of a file).
0 kommentar(er)
