You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the helper script causes an application deployment error since email is not set, causing the gurum-owner tag to be empty. Update the script to ask for email information. Consider adding the cognito role policy to the api CloudFormation template and create the cognito group attached to the role policy through the helper script.
The text was updated successfully, but these errors were encountered:
One fix for this might be to include the now generic tag based policy (kalleeh/gurum-api#9 (comment)) to the API template. Let's call it for example, gurum-group-policy.
This can then be referenced by whatever automation (helper script today) that would,
Prompt user if they want to create a group (Cognito Group).
If Yes, create an IAM Role that maps to that group and attach the gurum-group-policy to that IAM role.
Prompt if the user want to create a user (Cognito User).
Ask what group the user should be a member of and place the user in that Cognito Group.
This would also of course prompt for the e-mail address to be added to the user.
Using the helper script causes an application deployment error since email is not set, causing the gurum-owner tag to be empty. Update the script to ask for email information. Consider adding the cognito role policy to the api CloudFormation template and create the cognito group attached to the role policy through the helper script.
The text was updated successfully, but these errors were encountered: