1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
3
Ok so it's unclear how you are programmatically create new account.
However, I'm assuming you are using the Service Catalog API, as specified here.
Please make sure the ManagedOrganizationalUnit field has the specific format of OU_NAME (OU_ID)
As seen below:
{
pathId: "lpv2-7n2o3nudljh4e",
productId: "prod-y422ydgjge2rs",
provisionedProductName: "Example product 1",
provisioningArtifactId: "pa-2mmz36cfpj2p4",
provisioningParameters: [
{
key: "AccountEmail",
value: "abc@amazon.com"
},
{
key: "AccountName",
value: "ABC"
},
{
key: "ManagedOrganizationalUnit",
value: "Custom (ou-xfe5-a8hb8ml8)"
},
{
key: "SSOUserEmail",
value: "abc@amazon.com"
},
{
key: "SSOUserFirstName",
value: "John"
},
{
key: "SSOUserLastName",
value: "Smith"
}
],
provisionToken: "c3c795a1-9824-4fb2-a4c2-4b1841be4068"
}
con risposta 2 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
Just to add on the answer here: the format for the provisioning parameter 'ManagedOrganizationalUnit' must match this for all level 2 and deeper nested OUs, the level 1 OUs (directly underneath the root level) do not require the 'OU (ou-id)' format.