UserPool props option to disable creation of SMS role

[fractionalJoe]

Currently, UserPool creates an IAM role for SMS communication (using SNS) if a role is not supplied via the smsRole property in the props. I propose adding a way to prevent the creation of that role without supplying a role.

Use Case

The UserPool I maintain does not store a phone number and so does not provide SMS messaging. Our security posture is very conservative, so that autogenerated roles and policies are not allowed. This requires the security team to create and document an empty role, for my UserPool to reference. Needless to say this is a frowned upon practice. Adding this feature would remove this workaround.

Proposed Solution

I propose that the smsRole be of type string | IRole.

• If smsRole === "DEFAULT", then the UserPool is generated as it is today when smsRole is undefined and a role is created.
• If smsRole is of type IRole, then the UserPool is generated as it is today when a role is provided through smsRole, where no role is created and the provided role is referenced in the templates SmsConfiguration.
• If smsRole === NONE, then the UserPool is generated without the following properties in the template: SmsConfiguration, SmsVerificationMessage, VerificationMessageTemplate.SmsMessage

Additionally, an enum could be created for these smsRole values.

Other

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

---

This is a 🚀 Feature Request

[ryaeng]

This is a duplicate of #6943

[nija-at]

Closing since this is a duplicate