-
Notifications
You must be signed in to change notification settings - Fork 4k
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-cognito-identitypool-alpha: fromIdentityPoolArn Method throws when using a string from a StringParameter lookup #29780
aws-cognito-identitypool-alpha: fromIdentityPoolArn Method throws when using a string from a StringParameter lookup #29780
Comments
Thanks @Xenoha for reaching out . I can see in the code why this is producing an error -
|
I encountered a similar error, how do I fix them.
|
Comments on closed issues and PRs are hard for our team to see. |
1 similar comment
Comments on closed issues and PRs are hard for our team to see. |
Describe the bug
When using the construct to lookup an IdentityPool from a SSM StringParameter. The construct throws validation errors because it is expecting an actual string of two parts separated by a ':'.
Expected Behavior
Should be able to lookup an Identity pool with a SSM StringParameter stringValue.
Current Behavior
Code at lines 118 of the Identitypool.js file throws
// if (!(idParts.length === 2)) // throw new Error('Invalid Identity Pool Id: Identity Pool Ids must follow the format <region>:<id>'); // if (idParts[0] !== pool.region) // throw new Error('Invalid Identity Pool Id: Region in Identity Pool Id must match stack region');
Reproduction Steps
const identityPool = IdentityPool.fromIdentityPoolArn(this, 'some-identityPool', indentityPoolStringParameter.stringValue)
Possible Solution
Review other constructs best practices for allowing SSM StringParameter lookup stringValue strings.
Additional Information/Context
No response
CDK CLI Version
2.135.0
Framework Version
No response
Node.js Version
20.12.0
OS
Linux
Language
TypeScript
Language Version
Typescript 5.4.4
Other information
No response
The text was updated successfully, but these errors were encountered: