Skip to main content

File Upload

What you’ll learn
  • how file uploads are handled by the deployed cloud infrastructure and application code


Webiny Cloud Infrastructure - API - File Upload

For brevity, the diagram doesn't include network-level cloud infrastructure resources, like region, VPC, availability zones, and so on. Check out the Default VPC and Custom VPC topics if you're interested in that aspect of the deployed cloud infrastructure.


The diagram shows what happens every time a client tries to upload a binary file.

To provide file upload functionality, the File Manager application relies on a method called pre-signed POST payload. Once certain conditions are met, the method enables uploading files directly to an S3 bucket, which is significantly more efficient than having the file travel through multiple cloud infrastructure resources.

Learn more

If you want to learn more, feel free to check out a blog post we wrote on this exact subject and which explains the process in detail.

The process consists of three steps:

  1. The client issues a GraphQL HTTP request which instructs the GraphQL Server C to generate the necessary pre-signed POST data.
  2. Once the client receives the pre-signed POST data, in a new POST HTTP request, the data, and the actual file are uploaded to the S3 bucket G.
  3. Finally, another GraphQL request is issued, which instructs the GraphQL Server C to store the file meta data. The data is stored both in Amazon DynamoDB E and Amazon ElasticSearch Service F.


Who can upload files?

Only users with proper permissions can perform file uploads. Both authentication and authorization are performed in steps one and three, on the GraphQL Server c.

Is there a way to define a maximum file upload size?

Yes, by going into the File Manager's general settings section, and manually entering the appropriate values.

File Manager Settings

Last updated on by Adrian Smijulj