Open Almenon opened 1 year ago
One weird thing I noticed is the lambda is trying to describe us east limits. Not sure why it tried to do that, the lambda was in us-west-2. But the resource was *
so it should be able to describe a different region without error.
Also here is the contents of my config/region-switch.yaml
:
---
BootstrapQualifier: "ssoutility"
SSOServiceAccountId: "459446695407"
SSOServiceAccountRegion: "us-west-2"
SSOServiceTargetAccountRegion: "us-east-1"
When following https://github.com/aws-samples/aws-iam-identity-center-extensions/blob/main/docs/documentation/Region-Switch.md I ran into the following error when deploying the discovery stack:
I checked the lambda's execution role and it did have dynamodb describelimits permissions, so maybe it's a timing issue where the policy wasn't attached when the lambda ran.
Logs: https://pastebin.com/gnSW6wXb