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
Can I add more than one emailKeyPrefix value? I'm trying to decide whether to create multiple folders within a bucket. One for each email address on the same domain. I'm considering this just in case I need to manually search for something. I'm not really sure what the best practice is for SES. I assume that if I decide to go that route, I'll need to create a separate Email Receiving rule for each address. What I don't know however is whether I can use the same Lambda function for multiple emailKeyPrefixes. Is there any way to check all subfolders within a bucket using a wildcard or even better for versatility, list multiple emailKeyPrefixes? If not, I assume I would also have to create a separate Lambda function for each rule, correct? Is it even worth it? Thoughts or any experience with this would be much appreciated.
Signed,
Obsessive compulsive planner.
The text was updated successfully, but these errors were encountered:
Can I add more than one emailKeyPrefix value? I'm trying to decide whether to create multiple folders within a bucket. One for each email address on the same domain. I'm considering this just in case I need to manually search for something. I'm not really sure what the best practice is for SES. I assume that if I decide to go that route, I'll need to create a separate Email Receiving rule for each address. What I don't know however is whether I can use the same Lambda function for multiple emailKeyPrefixes. Is there any way to check all subfolders within a bucket using a wildcard or even better for versatility, list multiple emailKeyPrefixes? If not, I assume I would also have to create a separate Lambda function for each rule, correct? Is it even worth it? Thoughts or any experience with this would be much appreciated.
Signed,
Obsessive compulsive planner.
The text was updated successfully, but these errors were encountered: