-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(aws-appsync): userPoolConfig authorizer ignores the userpool region #13691
Comments
Found a workaround (not sure if it is intended to be used this way... ). The code will set the region based on the
|
Nice finds on this and the workaround. Definitely will have to look into how this can be solved on the CDK side. We likely can parse out the region from the user pool arn within the |
The issue is related to the way the |
…13715) Importing a `UserPool` using `fromUserPoolArn()` method would not retain the account/region from the ARN and would instead use the environment from the scope it is imported to. Closes #13691 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
…ws#13715) Importing a `UserPool` using `fromUserPoolArn()` method would not retain the account/region from the ARN and would instead use the environment from the scope it is imported to. Closes aws#13691 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…ws#13715) Importing a `UserPool` using `fromUserPoolArn()` method would not retain the account/region from the ARN and would instead use the environment from the scope it is imported to. Closes aws#13691 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
I know this issue is closed, but wanted to leave this here for anyone else still having this issue as this issue is still present after the UserPool fix above. I have opened #20195, which will address this root issue which is in AppSync, not UserPools. It is also present in a few other modules outside of AppSync. In the short term, a property override can be used to fix this.
|
When adding an authorizer to the appSync, using the userPoolConfig, we can import the authorizer from the Arn, however the the CF will add the deployment region rather than the authorizer region for that particular instance.
Reproduction Steps
What did you expect to happen?
What actually happened?
Environment
Other
I have tried overwriting the env to see if that would be picked up as a workaround to no avail:
I expect the region to be picked up based on the retuned authorizer. As it most likely will include its own region (or picked up from the id as it is also included...)
This is 🐛 Bug Report
Thanks!
The text was updated successfully, but these errors were encountered: