For some reason I needed the MX record, that is not created automatically in the domain creation process.
I had a look at the doc you linked. It's actually a misunderstanding of how SES and email/DNS work. The very purpose of verifying a domain is that you don't have to verify individual email addresses. So once you verified foo.com, there is no need to verify email@example.com to send emails from it. This also saves you from all the hacky setup suggested by the author with the inbound + rule setup.
Hope it clarifies.
AWS SES not sending notification via SNSAccepted Answerasked 10 months ago
SNS Topic/Subscription created through Terraform not showing upAccepted Answerasked 8 months ago
Domain and Email Address Identity have different Feedback notification settings for different SNS topics but both of them go to the same topic as what is set for the domain identityAccepted Answerasked 6 months ago
How to trigger SNS topic if IAM user is createdasked 4 months ago
Proper handling of SES bounces sent to sender's reply address (when already using SNS service to handle bounces)Accepted Answerasked a year ago
Unable to recieve email address verification email through SNSasked 2 years ago
aws ses receipt rules for routing email to an existing email addressasked 9 months ago
Can send but not receive email from AWS workmail.asked 2 years ago
ACM validation pending while created with cloudformation and route53asked 4 months ago
How to delete a email subscription in SNS, I had typo while typing email address?asked 10 months ago