- 最新
- 投票最多
- 评论最多
The nationality of the user is best stored in a custom string attribute of the user pool. Any lambda processing some trigger can then lookup the the value for the user in question.
Easiest would be to let an external email system do the localization. Usually a system like that will have mail-merge features and localized Content Management System. Lambda triggers can be used to do the right API calls on you system.
The custom message triggers is a way to go if you want a lighter weight solution. In these methods you could lookup the nationality and return a email body in the right language. Be aware though that emails have a nasty way of specifiying content and styling. The customer messages are maxed at 20,000 UTF-8 characters. This seems a lot but it is reached sooner than you think when a lot of styling is used for various email client / phone sizes.
相关内容
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前