I have deployed Medplum on AWS account successfully and it is working smoothly. But I am trying to configure SMTP. For that i have followed following steps: 1) updated support email id in both: config,json file and in AWS parameter store 2)Added following block in config,json file and in AWS parameter store: "smtp": { "host": "smtp.sendgrid.net", "port": 587, "username": "apikey", "password": "YOUR_API_KEY" } 3) I executed server update command Still it is throwing error, here are some screenshots for ref. But I have one more doubt, in above mentioned SMTP block, what should be the username? apikey or actual username? For now i am using actual username. I kindly request your assistance in resolving this issue. Your guidance and support would be highly appreciated.

HI @sanket_89360 , is there any additional information in your server logs about this failure. That might give more insight into why this failed

I will check and get back to you

Hey @rahul1 What do you think about above issue? Any other ways to finding out the root cause

@sanket_89360 , i just wanted to confirm that you took the following steps: 1. Sign up for a Sendgrid account 2. Create and store a SendGrid API key with full access "Mail Send" permissions. 3. Verify your SendGrid Sender Identity 4. Created a new key in AWS parameter store called

/medplum/[environment]/smtp

5. The value of this AWS secret was

{
  "host": "smtp.sendgrid.net",
  "port": 587,
  "username": "apikey",
  "password": "THE_API_KEY_YOU_CREATED_IN_STEP_2"
}

@sanket_89360 please check above

@rahul1 i have followed the above mentioned steps. the only confusion was related with what should be the username? "actual username" or "apikey". i tried both approaches. but it didnt work. i will check the sendgrid connectivity.

@rahul1 is the value seems in the right format?

@sanket_89360 my apologies. I was just informed that we have an open issue to support SMTP configuration on AWS (vs. localhost). https://github.com/medplum/medplum/issues/2894

ahhh, so any workaround to make it work on aws?

okay, thanks for the update

Hi @sanket_89360 , this is an issue we are trackig, but it is not currently being actively developed in the current sprint. However, we'd be happy to take a community contribution if you are willing 🙂 This issue is marked as one our "good first issues"

@rahul1 ok, thank you