Upload your analysis file
Now that you have a pre-signed URL to upload your file, it's time to do the actual upload.
You'll use information from the pre-signed generation to do the upload.
Route
The final routes are subject to change before Go-Live Summer 2024
The following applies to EARLY ACCESS prior to Go Live.
Some of our routes will be changing prior to our final go-live date this summer (2024). They won't change during Early Access, but be sure to check the documentation.
In order to make a smooth tranistion, we'll provide detailed information on which routes changed and which remained the same. As a good programming practice, you store the routes in a central library for easier migration.
Older routes may be kept active for short period of time to help with any transitions.
Payload
Response
In the previous step, you initiated a pre-signed url request. The response from that will request will contain the "presigned":"url", which will become the url-endpoint for the POST upload action to upload a file.
Below is the basic structure of the response created from the pre-signed url request.
The Response of an Upload -> 204 ~ No Content (not 200)
The response from uploading a file with a pre-signed URL is simply 204 with no body or other information. It's essentially a response that the information was received and it will be available shortly. S3 works on an eventual consistency model as it replicates this across several availability zones.
Keep that in mind if you are only used to checking for 200 responses.
Typically your file is ready almost immediately. And, since our executions are queued, you can request the start an execution right away.
Example with 🐍 Python
This code block contains the full source, which also includes the initial request to get the pre-signed url (from the previous section).
Generating the Payload
The Code Block above calls this class to create the Payload for the upload.