1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Hi. JITP and fleet provisioning are two different things, but I think you mean fleet provisioning.
There really isn't anything to do in the case of provisoning by claim. If you picked trusted user, an IAM role would be created.
This workshop module presents a full provisioning by claim setup procedure, using CLI commands: https://catalog.us-east-1.prod.workshops.aws/workshops/7c2b04e7-8051-4c71-bc8b-6d2d7ce32727/en-US/provisioning-options/fleet-provisioning
Contenus pertinents
- demandé il y a 2 mois
- demandé il y a un an
- demandé il y a 9 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 8 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
you're right, I meant to say fleet provisioning. Looking at this section: https://catalog.us-east-1.prod.workshops.aws/workshops/7c2b04e7-8051-4c71-bc8b-6d2d7ce32727/en-US/provisioning-options/fleet-provisioning#create-claim-certificate-and-key I understand about creating the claim certificate and key, then attaching the claim certificate to a policy, but there is nothing that attaches the policy to the provisioning template. In the console, once you choose "Claim provisioning initiator" you can choose a policy to attach to the provisioning template. Is that step not necessary? Just the existence of the policy will cause it to get used by the template?