While Buildstash offers simple, low-cost storage for your builds out the box, you may prefer to host your own build data. We make it easy to connect an AWS S3 bucket (or S3 API compatible storage from another provider).<blockquote>ℹ️ This feature is available to users on our Pro plan and up.</blockquote>Follow the steps below to setup a custom storage bucket on an application.<h2>Prepare S3 bucket</h2><ol class="steps-list"><li>Create new bucket If you haven't already created an S3 bucket to use with Buildstash, it is strongly advised to start with a new or empty bucket. Our application expects a certain directory structure and won't be able to work with existing files.<img src="https://uploads.productlane.com/b65088f363047eb4741f60c2d7e7d6e0.png">Once you've connected a bucket to Buildstash, you can feel free to re-use across applications (or even workspaces) as you prefer. You can disable ACLs, and block all public access during creation. </li><li>Set CORS policy Once the bucket is created, you must set your CORS policy to allow Buildstash domains the access we need. To edit the bucket's CORS policy, select your bucket in the AWS console, then go to Permissions &gt; Cross-origin resource sharing (CORS) &gt; Edit.<img src="https://uploads.productlane.com/bd99e64268a2eaf475f1f51846f072a3.png"><pre class="relative language-json"><code class="language-json relative">[<text>
 </text>{<text>
 </text>"AllowedHeaders":<text> </text>[<text>
 </text>"*"<text>
 </text>],<text>
 </text>"AllowedMethods":<text> </text>[<text>
 </text>"PUT",<text>
 </text>"POST",<text>
 </text>"DELETE",<text>
 </text>"GET"<text>
 </text>],<text>
 </text>"AllowedOrigins":<text> </text>[<text>
 </text>"https://buildstash.com",<text>
 </text>"https://*.buildstash.com",<text>
 </text>"https://builds.download",<text>
 </text>"https://*.builds.download",<text>
 </text>"https://buildsta.sh",<text>
 </text>"https://*.buildsta.sh"<text>
 </text>],<text>
 </text>"ExposeHeaders":<text> </text>[<text>
 </text>"ETag",<text>
 </text>"Location"<text>
 </text>]<text>
 </text>}]</code></pre>Enter the above JSON configuration, then save. </li><li>Get S3 credentials, attached to user with valid access policy You'll need to create an IAM user in AWS with the necessary access to your new bucket. You can follow the instructions in the <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html" target="_blank" rel="noopener noreferrer nofollow" class="cursor-pointer box-border font-semibold border-b hover:border-b-[2px] transition-all duration-75 " style="text-decoration: none; color: inherit; border-color: var(--portal-accent-color);">AWS documentation to set this up</a>, and create an access key for the user. We recommend creating a user specifically for this purpose, locked down with just the necessary access to this bucket. Below is an example of a valid access policy, assuming your bucket was titled "buildstash-builds-bucket". <pre class="relative language-json"><code class="language-json relative">{<text>
	</text>"Version":<text> </text>"2012-10-17",<text>
	</text>"Statement":<text> </text>[{<text>
			</text>"Effect":<text> </text>"Allow",<text>
			</text>"Action":<text> </text>[<text>
				</text>"s3:ListBucket",<text>
				</text>"s3:ListBucketMultipartUploads",<text>
				</text>"s3:GetBucketCORS",<text>
				</text>"s3:GetBucketLocation",<text>
				</text>"s3:GetObject",<text>
				</text>"s3:GetObjectAcl",<text>
				</text>"s3:PutObject",<text>
				</text>"s3:DeleteObject",<text>
				</text>"s3:ListMultipartUploadParts",<text>
				</text>"s3:AbortMultipartUpload",<text>
				</text>"s3:RestoreObject",<text>
				</text>"s3:ReplicateObject"<text>
			</text>],<text>
			</text>"Resource":<text> </text>[<text>
				</text>"arn:aws:s3:::buildstash-builds-bucket",<text>
				</text>"arn:aws:s3:::buildstash-builds-bucket/*"<text>
			</text>]}<text>
	</text>]}</code></pre>Securely note the access key and secret access key provided. </li></ol><h2>Connect bucket to your Buildstash app</h2><ol class="steps-list"><li>Navigate to your application storage settings In a fresh Buildstash application, go into your app's Settings &gt; Storage &gt; Configure storage.<img src="https://uploads.productlane.com/43d00623178c907b44dea9b084908159.png">Note, you can only setup custom storage on an application when no builds are stored in it. This also applies to removing an existing custom store and switching back to Buildstash provided storage. </li><li>Enter S3 configuration Enter the details for your S3 bucket, including the correct bucket region.<img src="https://uploads.productlane.com/2c2d0a6f97114b09d29e8c47f1d69fe6.png"> When you hit "Save" a test connection request will be made to the bucket, and if it is successful, the custom store will successfully save. </li><li>Your S3 bucket is now active for custom build storage! 🎉 Builds uploaded to this application will now be hosted within your custom bucket. <blockquote>⚠️ Buildstash now expects to manage the files in this bucket, and that files will be where we expect them to be. Please manage build files (uploading, deleting, etc) via the Buildstash interface and our provided tooling, and don't edit files directly in the bucket, to avoid causing issues like broken build links.</blockquote></li></ol>

Integrations

AWS S3

Guide

Get started

Overview

GitHub Actions

Azure DevOps Pipelines

fastlane

JumpCloud

Docs

Buildstash

AWS S3

Table of Contents