create_provisioning_template
async
¶
create_provisioning_template(
template_name: TemplateName,
template_body: TemplateBody,
provisioning_role_arn: RoleArn,
*,
config_overrides: Optional[AsyncIoTClientConfig] = None,
description: Optional[TemplateDescription] = None,
enabled: Optional[Enabled2] = None,
pre_provisioning_hook: Optional[ProvisioningHook] = None,
tags: Optional[TagList] = None,
type: Optional[TemplateType] = None,
) -> CreateProvisioningTemplateResponse
Creates a provisioning template.
Requires permission to access the CreateProvisioningTemplate action.
Parameters:
-
template_name(TemplateName) –The name of the provisioning template.
-
description(Optional[TemplateDescription], default:None) –The description of the provisioning template.
-
template_body(TemplateBody) –The JSON formatted contents of the provisioning template.
-
enabled(Optional[Enabled2], default:None) –True to enable the provisioning template, otherwise false.
-
provisioning_role_arn(RoleArn) –The role ARN for the role associated with the provisioning template. This IoT role grants permission to provision a device.
-
pre_provisioning_hook(Optional[ProvisioningHook], default:None) –Creates a pre-provisioning hook template. Only supports template of type
FLEET_PROVISIONING. For more information about provisioning template types, see type. -
tags(Optional[TagList], default:None) –Metadata which can be used to manage the provisioning template.
For URI Request parameters use format: ...key1=value1&key2=value2...
For the CLI command-line parameter use format: &&tags "key1=value1&key2=value2..."
For the cli-input-json file use format: "tags": "key1=value1&key2=value2..."
-
type(Optional[TemplateType], default:None) –The type you define in a provisioning template. You can create a template with only one type. You can't change the template type after its creation. The default value is
FLEET_PROVISIONING. For more information about provisioning template, see: Provisioning template.
Raises:
-
InternalFailureException–An unexpected error has occurred.
-
InvalidRequestException–The request is not valid.
-
LimitExceededException–A limit has been exceeded.
-
ResourceAlreadyExistsException–The resource already exists.
-
ThrottlingException–The rate exceeds the limit.
-
UnauthorizedException–You are not authorized to perform this operation.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_iot/_services/async_io_t.py
3620 3621 3622 3623 3624 3625 3626 3627 3628 3629 3630 3631 3632 3633 3634 3635 3636 3637 3638 3639 3640 3641 3642 3643 3644 3645 3646 3647 3648 3649 3650 3651 3652 3653 3654 3655 3656 3657 3658 3659 3660 3661 3662 3663 3664 3665 3666 3667 3668 3669 3670 3671 3672 3673 3674 3675 3676 3677 3678 3679 3680 3681 3682 3683 3684 3685 3686 3687 3688 3689 3690 3691 3692 3693 3694 3695 3696 3697 3698 3699 | |