Blaise
March 4, 2024, 9:14pm
1
I created an EC2 instance using the Balena OS AMI (balenaOS-2.113.3-generic-aarch64). The config.json
file I used is pretty similar to the config shown in this blogpost. BalenaOS AWS Amazon Machine Images now available - balena Blog
The instance starts perfectly fine, but I can’t see it show up on the balena dashboard. What am I missing?
Blaise
March 4, 2024, 9:19pm
2
To be specific, the config includes the following keys (some values redacted).
{
"apiEndpoint": "https://api.balena-cloud.com",
"appUpdatePollInterval": 900000,
"applicationId": "",
"deltaEndpoint": "https://delta.balena-cloud.com",
"listenPort": "48484",
"logsEndpoint": "https://logs.balena-cloud.com",
"mixpanelToken": "",
"registryEndpoint": "registry2.balena-cloud.com",
"vpnEndpoint": "cloudlink.balena-cloud.com",
"vpnPort": "443",
"persistentLogging": true,
"deviceApiKeys": {
"api.balena-cloud.com": ""
}
}
mpous
March 5, 2024, 10:36am
3
Do you see any logs in AWS @Blaise ? Did you try this from the blogpost?
please use a config.json
configured for development mode and use the EC2 serial console to access to the serial console prompt of your instance. Direct AWS SSH access is not possible, but instances can be accessed via balenaCloud’s cloudlink access, either via the dashbaord web console or in development mode using the balena CLI ssh command.
Blaise
March 5, 2024, 8:56pm
4
I haven’t tried that, but I’ll let you know after giving it a try.
Blaise
March 5, 2024, 9:12pm
5
From the EC2 serial console, i’m not able to see the login prompt that I see with other EC2 instances that are not using the BalenaOS AMI.
Blaise
March 5, 2024, 9:34pm
6
Eventually, I got this to work!