You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support PKCS#11 for mutual TLS on Unix platforms (#356)
- Update to latest `aws-crt-cpp`, which exposes PKCS#11 functionality (see awslabs/aws-crt-cpp#315)
- Add `pkcs11-pub-sub` sample, demonstrating an MQTT connection where the private key is stored in PKCS#11 token.
- Add docs for sample
- Sample runs in CI
@@ -339,7 +394,7 @@ get the sample up and running. These steps assume you have the AWS CLI installed
339
394
sufficient permission to perform all of the listed operations. You will also need python3 to be able to run parse_cert_set_result.py. These steps are based on provisioning setup steps
340
395
that can be found at [Embedded C SDK Setup](https://docs.aws.amazon.com/freertos/latest/lib-ref/c-sdk/provisioning/provisioning_tests.html#provisioning_system_tests_setup).
341
396
342
-
First, create the IAM role that will be needed by the fleet provisioning template. Replace `RoleName` with a name of the role you want to create.
397
+
First, create the IAM role that will be needed by the fleet provisioning template. Replace `RoleName` with a name of the role you want to create.
343
398
``` sh
344
399
aws iam create-role \
345
400
--role-name [RoleName] \
@@ -351,17 +406,17 @@ aws iam attach-role-policy \
The rest of the instructions assume you have used the following for the template body:
367
422
``` sh
@@ -371,13 +426,13 @@ If you use a different body, you may need to pass in different template paramete
371
426
372
427
#### Running the sample and provisioning using a certificate-key set from a provisioning claim
373
428
374
-
To run the provisioning sample, you'll need a certificate and key set with sufficient permissions. Provisioning certificates are normally
429
+
To run the provisioning sample, you'll need a certificate and key set with sufficient permissions. Provisioning certificates are normally
375
430
created ahead of time and placed on your device, but for this sample, we will just create them on the fly. You can also
376
431
use any certificate set you've already created if it has sufficient IoT permissions and in doing so, you can skip the step
377
432
that calls `create-provisioning-claim`.
378
-
433
+
379
434
We've included a script in the utils folder that creates certificate and key files from the response of calling
380
-
`create-provisioning-claim`. These dynamically sourced certificates are only valid for five minutes. When running the command,
435
+
`create-provisioning-claim`. These dynamically sourced certificates are only valid for five minutes. When running the command,
381
436
you'll need to substitute the name of the template you previously created, and on Windows, replace the paths with something appropriate.
382
437
383
438
(Optional) Create a temporary provisioning claim certificate set. This command is executed in the debug folder(`aws-iot-device-sdk-cpp-v2-build\samples\identity\fleet_provisioning\Debug`):
0 commit comments