# Uploading large files

<span class="rvts6">In occasions, file sizes can be prohibitively large for uploading using the REST interface, as some services have file limits of 2GB or 4GB for a single file size.</span>

<span class="rvts6">In these cases, there are alternatives to consider:</span>

1. <span class="rvts6">If the files have not been compressed, consider placing them into a ZIP archive before uploading. The processor system will unpack the files.</span>
2. <span class="rvts6">If the entity type allows, consider splitting the spatial data into several files that under the required limit.</span>
3. <span class="rvts6">Bypass the REST upload altogether, and upload directly to the storage system, for instance AWS S3 or Azure Blob Storage.</span>

<span class="rvts6">The following sections cover how to upload data directly, depending on the storage system in use.</span>

<span class="rvts6">  
</span>

##### <span class="rvts16">Uploading data directly to Azure Blob Storage</span>

<span class="rvts6">In order to upload data directly into Azure Blob storage, it is necessary to know how storage keys are composed in the system.</span>

<span class="rvts6">The keys in Azure are composed using the following syntax:</span>

<span class="rvts6">&lt;OrganizationID&gt;@&lt;ProjectID&gt;@&lt;EntityID&gt;@&lt;FileName&gt;</span>

<span class="rvts6">Where:</span>

<span class="rvts6">OrganizationID - Set to 2343243456678890</span>

<span class="rvts6">ProjectId - The ID of the project that contains the data entity</span>

<span class="rvts6">EntityId - The ID of the entity that will contain the file</span>

<span class="rvts6">FileName - Name for the file</span>

<span class="rvts6">Here is one particular examples of such a key:</span>

<span class="rvts6">2343243456678890@03684CA0F35947EC8243E52972CA3E70@3AC3A444AF414041A0668032536697AD@myblockmodel.zip</span>

<span class="rvts6">This key/blob pair should be created in the Blob Container that is used by the deployment.</span>

<span class="rvts6">  
</span>

##### <span class="rvts16">Uploading data directly to AWS S3</span>

<span class="rvts6">In order to upload data directly into AWS S3, it is necessary to know how storage keys are composed in the system.</span>

<span class="rvts6">The keys in Azure are composed using the following syntax:</span>

<span class="rvts6">&lt;OrganizationID&gt;@&lt;ProjectID&gt;@&lt;EntityID&gt;@&lt;FileName&gt;</span>

<span class="rvts6">Where:</span>

<span class="rvts6">OrganizationID - Set to 2343243456678890</span>

<span class="rvts6">ProjectId - The ID of the project that contains the data entity</span>

<span class="rvts6">EntityId - The ID of the entity that will contain the file</span>

<span class="rvts6">FileName - Name for the file</span>

<span class="rvts6">Here is one particular examples of such a key:</span>

<span class="rvts6">2343243456678890@03684CA0F35947EC8243E52972CA3E70@3AC3A444AF414041A0668032536697AD@myblockmodel.zip</span>

<span class="rvts6">This key/blob pair should be created in the S3 Bucket that is used by the deployment.</span>