I'm sorry to hear you're experiencing problems creating the MX record for your organization. I took a look at your account and your WorkMail organization seems to have all domains configured correctly. Do you still have problems creating the MX record?
The MX record shows an "inconsistent" validation.
inbound-smtp.us-east-1.amazonaws.com definitely has an A record. Your error message almost looks like you have combined the priority field in with the destination. The Destination is inbound-smtp.us-east-1.amazonaws.com. The priority entry should be 10.
It looks like there is a typo in the domain. The records currently resolved to 10 inbound-smtp.us-east-1.amazonaws.com.com. Note the double .com.com.
Correcting that should solve the problem.
Publishing an MX record for Amazon SES email receivingasked 2 years ago
Receiving mail with Amazon SES doesn't work because the MX record resolves to the CNAME I set up for CloudfrontAccepted Answerasked 21 hours ago
My MX record is not showing when I do a dig commandasked 2 years ago
Need assistance with MX record to use on my websiteasked 7 months ago
Pointing an A Record and CNAME Record to WIX Not Working, A Record not propagatingasked a year ago
Domain Verification REVOCATION WARNING despite presence of TXT record,asked 3 years ago
Do You Have to Add New MX or TXT Records to a Domain using SES?asked 3 years ago
Do I need an A record?asked 4 years ago
What is the IP address of my AWS website so I can add the A record on Cloudflare?Accepted Answerasked a month ago
Do I need MX record for only sending emails?asked 3 months ago