You can use the CVM allows the device to apply for their own certificate and installation.
README Languages: Chinese blog(中文)
In order to ensure the secured communication between IoT devices and AWS IoT Core, Devices may use X.509 certificates to connect to AWS IoT using TLS mutual authentication protocols. AWS Cloud security mechanisms protect data as it moves between AWS IoT and other devices or AWS services.
This mutual TLS authentication mode requires that a device certificate meets either of the following two conditions:
- The certificate used on the IoT device is issued by AWS IoT Core
- The CA certificate which is used to sign IoT device certificate is pre-imported into a customer’s AWS account and associated with their AWS IoT Core environment AWS understands that customers will have devices that currently do not have the ability to meet condition 1 or 2 immediately. Therefore, we have provided a reference application called, Certificate Vending Machine, which demonstrates how customers can provision devices with certificates created in AWS IoT.
Certificate Vending Machine (CVM) is an ideal fit for customers who do not have certificates pre-installed on the devices and are unable to obtain CA certificates to pre-create device certificates during their manufacturing process. On this occasion, you can use CVM system which allows the device to apply for their own certificate and then install the certificate into storage on the device. This document provides the design ideas and associated source code, which can help customers quickly develop a CVM system. Since the original IoT device does not contain a certificate for TLS mutual authentication, we need to pay attention to three points.
- When IoT devices and the CVM system are communicating, a trusted DNS environment is needed in order to prevent the man-in-middle attack along with using other secured communication method, such as HTTPS.
- When an IoT device requests a certificate, it should have a unique identifier. The identifier, such as serial number, client ID or product ID, will be used for policy binding and to ensure that the device is a valid device.
- All certificates submitted by the CVM system are AWS IoT Core signed certificates. If you need to use a custom CA certificate, refer to the Just-in-time Registration (JITR) certificate authentication method.
The entire implementation can be divided into three modules: IoT devices, CVM system and AWS IoT Core.
- IoT device side
- Request a device certificate via HTTPS connection.
- Submit the device serial number and the registration token when requested. Registration token is a one-time token to avoid device serial number spoofing.
- CVM system
- Provides remote access to IoT devices for certificate application.
- Generates secured certificate for each IoT device that can be used to communicate to AWS IoT Core.
- Uses database, like DynamoDB, to store information such as the device ID, key registration information, and the applied device certificate.
- Associates IoT Thing Name, Certificate Policy, and Certificate ID by querying the association table in DynamoDB. In parallel, CVM modifies the certificate status attribute in DynamoDB to ensure that a device can only register for a single active certificate.
- IoT Core
- Response to API calls to generate the certificate and key pairs.
The basic workflow of the CVM system is as follows:
The architecture of CVM system is as follows:
Using the API Gateway and Lambda solution for scalability, the detailed workflow is shown as follows:
- When IoT device requests access to IoT platform, it triggers a certificate application to CVM system. Then IoT device sends the appropriate API calls to the API Gateway for IoT device certificate application.
- AWS API Gateway invokes Lambda to initiate certificate request to IoT Core.
- After receiving the request from API Gateway, Lambda checks DynamoDB to validate if the request is legitimate and applies for a certificate to the backend IoT Core.
- The CVM system uses the AWS SDK to make a series of API calls to AWS IoT Core. These API calls perform actions such as creating a new thing in the AWS IoT Thing Registry and creating an associated device certificate.
- AWS IoT Core generates a device certificate, key pairs and returns the certificate information and the certificate ID to CVM system.
- Lambda uses a series of API calls to associate Thing Name, Certificate, and Policy on IoT Thing registry by querying pre-created DynamoDB association table according to product serial number.
- Update all the associated information of the current device to DynamoDB association table
- Lastly, the CVM system returns the certificate to the IoT devices
In order to ensure the security of the CVM system, the AWS Lambda function needs to be scoped to the minimum permissions needed in order to create certificates. The following example shows how to assign the correct IAM role privilege to the CVM system.
First of all, you need to understand the CVM system needs to have the IAM authority to complete the certificate application and the issuance process.
- Access AWS DynamoDB for querying, modifying, and updating device associations in DynamoDB table
- Access the IoT platform to apply for IoT device certificates
The policy template for IAM role as follows, you should modify it more specifically for the minimum privilege.
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "IoTCWlogsPolicy",
"Effect": "Allow",
"Action": [
"logs:*",
"iot:CreateThing",
"iot:AttachPolicy",
"iot:AttachThingPrincipal",
"iot:CreatePolicy",
"iot:CreateKeysAndCertificate"
],
"Resource": "*"
},
{
"Sid": "dynamodPolicy",
"Effect": "Allow",
"Action": [
"dynamodb:Query",
"dynamodb:UpdateItem"
],
"Resource": "arn:aws:dynamodb:REGION:123456789012:table/TableName"
}
]
}
Secondly, you need to allow lambda assume this role by adding trust relationship.
In addition to the IAM authority division, you need to create an association table on DynamoDB for the binding relationship between the device, the certificate and policy. Specifically, you need to create the following database fields in DynamoDB:
- Product id: IoT device ID
- Access Token: IoT Token
- timestamp: certificate request timestamp
- applyState: request status (if the certificate is set to -1, it means that the device has already registered the certificate)
- certID: certificate ID associated with the device
The solution is available as a AWS CloudFormation SAM template, and included in this repository (template.yml). Click the following button to deploy it to your AWS account in the us-east-1 region:
You will need to provide some parameters to point AWS Lambda.
When the cloudformation CREATE_COMPLETE, you can see the output of Cloudformation.
[
]
You must create item in your device dynamodb table, or you will see access deny.
[
]
Please use the link from the first step. https://XXXXX.execute-api.us-east-1.amazonaws.com/PROD/getcert?serialNumber=ascas&deviceToken=zxcz
The following CVM system reference source code uses the IoT interface provided by the AWS Node.js SDK to complete the certificate request and add the associated Thing Name and Policy.
// Create cert
iot.createKeysAndCertificate(params, function(err, certdata) {
console.log("certdata:");
console.log(certdata);
if (err) console.log(err, err.stack); // an error occurred
else{
// Create IoT Policy for above cert
var params = {
policyDocument: config.PILICY_DOCUMENT, /* required */
policyName: serialNumber /* required */
};
iot.createPolicy(params, function(err, data) {
if (err) console.log(err, err.stack); // an error occurred
else{
console.log(data);
// Attach policy for cert
var params = {
policyName: serialNumber, /* required */
target: certdata.certificateArn /* required */
};
iot.attachPolicy(params, function(err, data) {http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/Iot.html
This library is licensed under the Apache 2.0 License.