BYOC
Blazing fast GitHub Action Runners, hosted on WarpBuild's cloud
For using snapshots in your BYOC custom runners, ensure that the following quotas are available in your cloud account.
AWS
Quota | Recommended Limit | Notes |
---|---|---|
Concurrent snapshot copies per destination Region | 50 | Increase this if multiple snapshots are getting created in the same region in parallel. |
CompleteSnapshot requests per account | 100 | Increase this if multiple snapshots are getting created in an account across regions in parallel. |
Concurrent snapshots per General Purpose SSD (gp3) volume | 100 | We use gp3 as the EBS SSDs, so it is recommended to increase it to a larger value. |
Pending snapshots per account | 100 | This is required for cases where AWS receives snapshot request and marks it as pending. |
GetSnapshotBlock requests per account | 5,000 per second | Used for EBS creation and snapshot creation. |
PutSnapshotBlock requests per account | 5,000 per second | Used for snapshot creation to write the data blocks from EBS to snapshot. |
Snapshots per Region | 100,000 | |
StartSnapshot | 25 per second | The number of simultaneous requests to start creating snapshots. |
Storage for General Purpose SSD (gp3) volumes, in TiB | 100 | If there are additional EC2 instances outside of WarpBuild that are using gp3 storage we recommend to increase the storage limit to a larger number based on your requirements. |
AMIs | 50,000 | The maximum number of public and private AMIs allowed per Region. These include available, pending, and disabled AMIs, and AMIs in the Recycle Bin. |
TTL
Snapshots are retained for a maximum of 15 days. After this period, the snapshot is automatically deleted.
Last updated on