Skip to content

Latest commit

 

History

History
66 lines (44 loc) · 4.08 KB

File metadata and controls

66 lines (44 loc) · 4.08 KB

Task-K001 – Request a New Device Identifier and Attestation Keys

Make sure that you are logged in to the Frustration-Free Setup Console using a valid developer account. The keys that will be generated will be a set of 5 static keys that are associated with that developer account. So, in order to make use of the keys, you will need to test them in an environment where an Echo device has been setup using that developer account.

  1. Open the onboard tab in the Frustration-Free Setup console, and click on Request a new device type Identifier.

  2. Populate the full details about the product that you’re planning to use for Wi-Fi Simple Setup.

    The device data collected are mainly used for onboarding to Amazon Device Management Service. The following table shows what every fields will be used for by Amazon:

Device Meta Data Description
Contact Name Name of the Developer that will be using the device
Contact Email Email address to receive the key and device identifiers generated.
Product Manufacturer Name of the manufacturer. Used for reference.
Manufacturer Website Website of the manufacturer. Used for reference only.
Product Name Name of the product. This will be used for identifying the device. It will drive a device type and Product Id in Amazon Device Management Service.
Product Description Description of product. Used for reference only.
Product SKU SKU of the product. Will be used for reference in Amazon and can be changed later.
Device Protocol Support This should be Wi-Fi.
Expected Launch Date A planned date for launch. Used for reference only.
  1. You should receive the following email from Frusteration-Free setup team within 5-10 business days with the new device Identifier and DSS public key to use:

  2. Once you have the new device Identifiers, you should open the Frustration-Free Setup Console and open the Manage tab and select Manage Keys:

  5. Select the device type that you received in the email to start creating its Attestation Keys:

![](media/image23.png)
  1. Follow the instructions in the screen below to create the proper software DAK to make sure you can create various static keys to use in your test device:

  2. You should be able generate as many key pairs as you want for development purposes(Limit is 50 per dev dak) and below is a sample of the output files:

  3. Now you are ready to use the device keys in your SDK, make sure you replace the following files with the files specific for your devices: certificate.pem, private_key.pem, and dss_publiic_key.pem (This should be replaced with the key you received from FFS support)

Next>>