Custom S3 bucket
Add your own custom S3 bucket to store your app builds.
S3 compatible storage (AWS, Exoscale)
For those considering S3 compatible storage, specifically through AWS or a similar S3-compatible storage provider, the following steps outline the process of integrating this custom storage option into your Updraft setup:
What you need
Before you start make sure you have
Access to S3 Compatible Storage: Get the credentials to connect to your chosen storage service.
Access with the Right Permissions: Associate the necessary permissions with your key to interact with the bucket.
Set the correct policy for AWS S3 Bucket
Change Public access for AWS S3 Bucket
Permissions Policy for AWS S3 Bucket Example
Below is a sample policy snippet for AWS that ensures the correct permissions are in place:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "s3:*",
"Resource": "arn:aws:s3:::bucket-name"
}
]
}
This policy permits a range of actions on the specified storage bucket, including uploads, retrieval, and management of files.
Change Public Access for AWS S3 Bucket
Below is a needed change for Public Access:
Uncheck: Block public access to buckets and objects granted through new access control lists (ACLs)
Uncheck: Block public access to buckets and objects granted through any access control lists (ACLs)
Connect S3 Bucket with Updraft
After you set up the S3 bucket with your service provider you can set it up in Updraft
Log in to Updraft and go to "Profile -> Overview"
In the next step choose the option "S3"
Provider name: This is the name of your integration.
Region: The region of your bucket.
Bucket name: The name of the bucket.
Password: type in your Updraft Account password to confirm it
Click on enable to add your custom storage.
ℹ️ If you choose another S3 compatible storage provider than AWS. You can leave the Region empty and enter your endpoint URL instead.
Deactivate Custom Storage
Custom storage provides flexibility for storing your uploaded data, but there may be occasions when you need to deactivate or reactivate it.
Steps
Accessing Custom Storage Settings: Navigate to your account overview settings and find the "Custom Storage" section.
Click on the "Deactivate Custom Storage" option.
Confirm your action by entering your account password.
Uploading new app versions/builds:
Once custom storage is deactivated, new data will be stored on the Updraft DB system again.
Ensure that you're aware of this change when uploading new builds.
Old app versions/builds
Each previously uploaded build will not be available anymore
If a build is stored on inaccessible custom storage, a proper information message will be displayed when attempting to download it.
Custom storage settings are not removed from the database until the custom storage integration is deleted.
Reactivating Custom Storage: If you choose to reactivate custom storage, the URLs from previously uploaded builds on custom storage become valid again.
Conclusion: Managing custom storage settings ensures control over where your data is stored. Following these steps allows for a seamless transition between storage options, maintaining accessibility and clarity regarding your uploaded builds.
Note: Make sure to keep your account password secure and be mindful of the storage location information when interacting with builds.
Previous uploaded app versions
When you activate Custom Storage all previous uploaded app versions and installation-links will get unanvailable.
Previous uploaded custom AAB keystore
If you setup a custom AAb keystore and activate later custom storage, you need to re-upload the custom AAB keystore.
FAQ
What kind of data are stored within the custom S3 bucket?
If you are using custom storage (S3), new app versions (.aab, .apk, .ipa), app icons, custom AAB keystore will be stored on your custombucket.
We receive meta information when uploading the app build. Such information is stored in the Updraft database to keep the structure.
Last updated
