Questions tagged with Device Management
Sort by most recent
Browse through the questions and answers listed below or filter and sort to narrow down your results.
Device MetaData in AWS IOT core
Can we store Device/Thing MetaData in AWS IOT core ? We have iot things that we provision using fleet provisioning. These devices have metadata associated with it and other characteristics example battery health data which can change. What is a good practice to maintain this data ? Should we use device shadows to maintain the battery health etc ? This data only flows from the device to aws and not vice versa , is the device shadow still a good place to hold the information ? How do we store the metadata associated with a thing ? We will need to retrieve this data using api's when needed.
Aws IOT core for Android devices
We are looking to use AWS IOT core for device management of our android devices . Our devices already have our custom app installed on them and our plan was to leverage the app to provision the device. So we decided to bundle a common certificate and start up script (code) in the app . The script will be invoked on device start up and this will provision our devices by connecting to iot core. Can you advice us if this will work because 1) We will use a common certificate for all devices . If we are using fleet provisioning then my understanding is that aws iot core will install the unique certificates on the device during first connection . In our case , the certificates are installed on the app . So will it be possible for us to use fleet provisioning ? 2) Do we have to use unique certificates for each device while provisioning ? 3) Can we use BKS (bouncy castle keystore) instead of X509 certs?
AWS IoT Greengrass (V2) Core Device - Management
Hello, I have a couple of questions related to selecting the right tool for the job. There are three different technologies, which apparently all of them can handle device management: 1. AWS Systems Manager Agent component - the standard edition is limited to 1,000 devices (per account and per region). My understanding is that it would allow me to use the regular system manager capabilities, e.g., patching, automation, session manager (remote shell access), etc. 2. AWS IoT Device Management - there are some unique capabilities but similar to AWS Systems Manager it enables Device Jobs (that can be used to support software updates), Secure Tunneling (remote access), etc. 3. AWS Greengrass V2 Deployments (Create deployments) - appear to allow updating Greengrass software via jobs. I prefer to use just the tools I really need. Can you please advise what is the different between the three approach specifically for managing (patch/updates) Greengrass (V2) Core devices? is the 3rd option (AWS Greengrass V2 Deployments) sufficient for patch/updates in this particular use case? Thank you
Webdriver testcases are failing while setting connection
Trying to deploy a basic webdriver.io + nodejs test on devicefarm but always for ios device test cases are getting stuck at Testcase is failing: job arn: arn:aws:devicefarm:us-west-2:612756076442:job:02bd6c95-640d-43b3-82eb-6f618777ac73/1a6364f3-7528-44b1-afa1-d6c2dc51d881/00000 ``` 2022-05-04T22:40:58.353Z ERROR @wdio/runner: Error: Failed to create session. [0-0] Unable to connect to "http://localhost:4723/", make sure browser driver is running on that address. [0-0] If you use services like chromedriver see initialiseServices logs above or in wdio.log file as the service might had problems to start the driver. [0-0] at startWebDriverSession (/private/tmp/scratchY4h2F6.scratch/test-packagex5aknf/node_modules/integration/node_modules/webdriver/build/utils.js:72:15) [0-0] at process.processTicksAndRejections (node:internal/process/task_queues:95:5) [0-0] at async Function.newSession (/private/tmp/scratchY4h2F6.scratch/test-packagex5aknf/node_modules/integration/node_modules/webdriver/build/index.js:46:45) [0-0] at async remote (/private/tmp/scratchY4h2F6.scratch/test-packagex5aknf/node_modules/integration/node_modules/webdriverio/build/index.js:77:22) [0-0] at async Runner._startSession (/private/tmp/scratchY4h2F6.scratch/test-packagex5aknf/node_modules/integration/node_modules/@wdio/runner/build/index.js:223:56) ``` and for android testcases is asking for node version greater than 12 (after adding nvm install 18.1.0 in yaml)
Device Name on Instances console does not match "Filesystem" device name from "df -k" command
On the Instances console page, the EBS volume for the root device is reported to be: /dev/xvda But, the "df -k" command from the instance itself is reporting: /dev/nvme0n1p1 (an NVMe) device. ``` $ df -k Filesystem 1K-blocks Used Available Use% Mounted on devtmpfs 193955196 0 193955196 0% /dev tmpfs 193965976 0 193965976 0% /dev/shm tmpfs 193965976 780 193965196 1% /run tmpfs 193965976 0 193965976 0% /sys/fs/cgroup /dev/nvme0n1p1 1048563692 26926468 1021637224 3% / tmpfs 38793196 0 38793196 0% /run/user/1000 ``` Is there something wrong? Shouldn't they match? I need to know what kind of device it is so I know which instructions to follow for extended the file system as I just finished resizing the volume. There are two different instructions on this page depending on if the device is XVD or NVMe: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/recognize-expanded-volume-linux.html Thanks, Al
Device registration via JITP w/ pre-provisioning hook
When creating provisioning templates in AWS IoT Core you can attach a pre-provisioning hook. https://docs.aws.amazon.com/iot/latest/developerguide/pre-provisioning-hook.html I'm looking at onboarding devices using the JITP flow referenced here. https://docs.aws.amazon.com/iot/latest/developerguide/jit-provisioning.html There exist thing attributes that need to be populated at provisioning time. These attributes are not available to be encoded in the device certificate at manufacturing time. The attributes are used as part of the device policy and topic pattern in a multi-tenant solution to ensure no cross-contamination of data between customers. I would like to use a pre-provisioning hook to further augment the data available to the provisioning template. Is this possible? I understand that JITR is an option that would allow further augmentation but I would like to avoid having to manage the infrastructure necessary to support that approach.
Amazon Access Control system hardware (RFID/Biometrics)
VentureBeat (https://venturebeat.com/) featured article on AWS access control system hardware 2 years ago, but no information is available from the link. https://devices.amazonaws.com/ please share pointers to AWS access control system hardware and supporting software sdk/resources if any. Thank you so much.
unable to start httpd service - getting Address Already in use: make_sock: could not bind to address
I copied new ssl cert files to my server but upon doing a httpd restart I get the following error: (98) Address Already in use: make_sock: could not bind to address [::]:80 (98) Address Already in use: make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down unable to open logs Pretty sure this is related to something other than the new certificate files, but this is the first time I attempted to restart the server in quite some time.