Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Platform should use a well-known domain for device-type discovery #70

Open
dfunckt opened this issue Nov 28, 2019 · 1 comment
Open

Comments

@dfunckt
Copy link
Member

dfunckt commented Nov 28, 2019

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.

@balena-ci
Copy link
Contributor

[roman-mazur] This issue has attached support thread https://jel.ly.fish/#/support-thread~c0c4609d-1416-4308-be00-a9d81b313ad6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants