Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Why are AuthRole and UnauthRole required for hosting?
See original GitHub issue** Which Category is your question related to? **
init and hosting
** What AWS Services are you utilizing? **
s3 and cloudfront
** Provide additional details e.g. code snippets **
I’d like to use AWS Amplify only for hosting (at least for now) and would like to avoid unnecessary extra resources getting created. I noticed that the generated cloudformation templates and the config files generated by init refer to AuthRole and UnauthRole, which refer to Cognito, which I’m not using. I attempted to remove them manually from the cloudformation file, but when running amplify publish, they get re-created. Is there a good way to remove them entirely, or a particular reason why they’re needed? Thanks!
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hi guys im using only API module of Amplify, but the process create this roles, UnauthRole and authRole, i explored this roles and they dont have any policy attached… this is normal? If i add other service as Auth with cognito this files change?
Thanks!!
@UnleashedMind Thanks for the quick reply! In that case, can this ticket turn into a feature request to only create those roles when adding a category that requires them?