FAQ - Updraft Custom Storage
App distribution with custom storage
🗂️ Updraft Custom Storage — FAQ
🔹 What is Custom Storage?
Custom Storage allows you to connect your own external storage solution — either Google Cloud Storage, AWS S3 or Exoscale). This gives you full control over where your app builds, icons, and keystores are stored.
🔹 What kind of data is stored in Custom Storage?
Once Custom Storage is enabled, the following files will be stored in your own storage bucket:
App builds (.aab, .apk, .ipa)
App icons
Custom AAB keystores
Updraft only stores meta information (such as app name, version, and upload details) in its internal database — this ensures your build history remains visible in the dashboard.
🔹 What happens to previously uploaded builds when activating Custom Storage?
When you activate Custom Storage:
All previously uploaded app versions and their installation URLs will become unavailable.
You can continue to upload new builds; these will be stored in your new custom bucket.
Previous uploaded custom AAB keystore
If you previously set up a custom AAB keystore and activate Custom Storage afterwards, you will need to re-upload your custom AAB keystore, as it will now be stored in your custom bucket.
🔹 What happens when I deactivate Custom Storage?
New uploads will automatically be stored again in the Updraft default storage system.
Existing builds stored in your custom bucket will no longer be accessible until Custom Storage is reactivated.
When you reactivate it, all links to previously uploaded files on your custom storage will become valid again.
🔹 Who is responsible for maintaining Custom Storage?
⚙️ Important Note — Maintenance & Responsibility
When activating Custom Storage (Google Cloud Storage or S3), the setup, maintenance, and access management of that storage are entirely handled by your organization. Updraft provides the integration interface but does not monitor, maintain, or back up your external bucket.
Please ensure:
Your Google Cloud Storage or S3 bucket remains active and accessible.
The Service Account Key or Access Keys you provided stay valid and have the correct permissions.
You regularly manage storage costs, access control, and retention policies in line with your organization’s data policies.
If the bucket or credentials become invalid, previously uploaded builds, icons, or keystores will no longer be available in Updraft until connectivity is restored.
By enabling Custom Storage, you take full responsibility for the availability, maintenance, and security of all stored data.
🔹 Can I use multiple storage providers at the same time?
No. Only one Custom Storage integration can be active per organization — either Google Cloud Storage or an S3-compatible provider.
🔹 Can I switch providers or return to default storage?
Yes. You can deactivate Custom Storage or change the provider at any time. However, previously uploaded builds are not migrated automatically between storage systems.
🔹 How do I enable Custom Storage in Updraft?
Go to Profile → Overview → Custom Storage
Click Enable
Choose your storage type:
Google Cloud Storage → Enter Project ID, Bucket Name, Service Account JSON Key
S3 Storage → Enter Provider Name, Region or Endpoint URL, Bucket Name, Access Keys
Enter your Updraft account password to confirm
Click Enable
🔹 How do I deactivate Custom Storage?
Navigate to Profile → Overview → Custom Storage
Click Deactivate Custom Storage
Confirm by entering your Updraft account password
After deactivation, new builds will be stored using the Updraft default system.
🔹 Where can I get help with setup or troubleshooting?
If you need assistance with enabling or configuring Custom Storage, please contact: 📧 [email protected]
Last updated