You can send images from the web app to a bucket in Amazon S3. The browser sends each image directly to your bucket. For the general steps of an upload, read Uploads: send images to processing and storage services.
What you need
- An Amazon Web Services (AWS) account. To make one, click the icon at the right end of the Amazon S3 row in the New Upload dialog. The AWS site opens in a new tab.
- An S3 bucket.
- A CORS rule on the bucket that allows uploads from the web app. Read "Set the CORS rule of the bucket" below.
- An access key for an AWS user that can put objects in the bucket. Read "Make an access key" below.
- A computer browser at app.dronelink.com.
- A plan that includes this integration. To see which plans include it, find "Amazon S3" in the plan comparison table.
Set the CORS rule of the bucket
The browser sends the images to your bucket from app.dronelink.com. S3 refuses an upload from a web page, unless the CORS rule of the bucket allows that page.
- In the AWS console, open the bucket.
- Click Permissions.
- In Cross-origin resource sharing (CORS), click Edit.
- Enter this rule. If the bucket has other rules, add this rule to them.
[
{
"AllowedHeaders": ["*"],
"AllowedMethods": ["PUT"],
"AllowedOrigins": ["https://app.dronelink.com"],
"ExposeHeaders": []
}
]
- Click Save changes.
Make an access key
The web app uses the access key in your browser to sign each file upload. It does not send the key to Dronelink. Use a key that can only put objects in the bucket.
- In AWS IAM, make a user for the uploads.
- Give the user permission for
s3:PutObjecton the bucket, for examplearn:aws:s3:::your-bucket/*. - Make an access key for the user. Keep the access key ID and the secret access key.
Important: Do not use the access key of your AWS root user.
Settings
- Access Key ID: the ID of the access key.
- Secret Access Key: the secret of the access key. The browser does not keep it. Enter it for each upload.
- Region: the AWS Region of the bucket, for example us-east-1. Always enter the Region.
- Bucket: the name of the bucket.
- Path: optional. The folder in the bucket for the images, for example folder/subfolder. If you start the upload from a mission page, the default is the mission name and the capture time, for example my-mission/2026-11-16_14-30-00.
The browser keeps the Access Key ID, Region, Bucket and Path for the next upload.
Where the images go
Each image goes to the Path in the bucket. The web app uses only the file name. It does not keep folders from your computer. The name gets a number before the extension. The first file gets 0, the second file gets 1, and so on. Example: the first file DJI_0001.JPG becomes folder/subfolder/DJI_0001_0.JPG.
The number keeps images with the same name from two folders apart. If an object with the same name is already in the bucket, S3 replaces it. To keep each upload apart, use a different Path for each upload.
After the upload
The upload card shows the region, the bucket and the path. Open the bucket in the AWS console to see the images.
Troubleshooting
- "Error: Upload failed": the browser could not send the file. Make sure that the CORS rule of the bucket is correct. Then make sure that the Region is the Region of the bucket.
-
"Error: Upload failed with status 403": S3 refused the access key. Make sure that the key and the secret are correct, and that the user has
s3:PutObjecton the bucket. - Another status number: S3 refused the file. Make sure that the Bucket and the Region are correct.
- One file failed: the web app sends each file one time. If one file fails, the upload stops. The files that arrived stay in the bucket. Start a new upload.