Describe the bug
Currently the AWS Amplify is not available in all the regions & IAM Identity center is available. For the organisation where we have the region constraint, we have to keep the IAM identity center in the local region but since Amplify is not available there we have to go for the approach of having the TEAM stack deployed in the different region then IdC.
Expected behavior
We can have 2 regions in the parameter template file,
REGION : Region where our TEAM stack is going to deployed due to unavailability of AWS service.
IDC_REGION : Region where our IdC is configured
Additional context
I have tried to configure the same with a couple of changes in the TeamRouter and other files where we are going by default region for OU & IdC related calls. I am able to do the operations, creating the policies, approvers, create request and even able to approve it as well.
But after approving it just doesn't get updated & goes in Error state.
Describe the bug Currently the AWS Amplify is not available in all the regions & IAM Identity center is available. For the organisation where we have the region constraint, we have to keep the IAM identity center in the local region but since Amplify is not available there we have to go for the approach of having the TEAM stack deployed in the different region then IdC.
Expected behavior We can have 2 regions in the parameter template file,
REGION: Region where our TEAM stack is going to deployed due to unavailability of AWS service.IDC_REGION: Region where our IdC is configuredAdditional context I have tried to configure the same with a couple of changes in the TeamRouter and other files where we are going by default region for OU & IdC related calls. I am able to do the operations, creating the policies, approvers, create request and even able to approve it as well. But after approving it just doesn't get updated & goes in Error state.