You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The platform looks up available device types in the production S3 bucket of balenaCloud. We're currently pointing instances directly to the bucket, but we should instead use files.balena-cloud.com which proxies that bucket. The two obvious benefits are that users would then be able to deploy openbalena in strict networks (where all outbound connections must be explicitly allowed by a firewall and whitelisting s3.amazonaws.com is too broad) and also allows balenaCloud to change the actual storage location.
The text was updated successfully, but these errors were encountered:
The platform looks up available device types in the production S3 bucket of balenaCloud. We're currently pointing instances directly to the bucket, but we should instead use files.balena-cloud.com which proxies that bucket. The two obvious benefits are that users would then be able to deploy openbalena in strict networks (where all outbound connections must be explicitly allowed by a firewall and whitelisting s3.amazonaws.com is too broad) and also allows balenaCloud to change the actual storage location.
The text was updated successfully, but these errors were encountered: