RunDeck Series 4 - Configure RunDeck SMTP With AWS SES
For any automations notification system is very important. Rundeck provides multiple integrations for job notifications. But SMTP is main for many users. In this blog, we are going to configure RunDeck SMTP with AWS SES.
Tip:Configure Nginx ProxyPass For RunDeck
AWS SES: #
AWS SES is a managed SMTP service.
Go to your AWS Console –> SES. SES available on three regions.
- US East (N. Virginia)
- US West (Oregon)
- EU (Ireland)
You can select which is nearest to you or low cost.
Add Sender Email in SES: #
In the SES console, Go to Email address and verify your sender email address. SES uses this email for sending emails.
Create SMTP Credentials: #
Go to SMTP Settings –> Create My SMTP Credentials. Provide an user name for SES, then click create. I’ll generate an AccessKey and SecretKey.
- Access Key – Username
- Secret Key – Password
SMTP Server Details: #
In SMTP Settings you can get your SMTP server details.
NOTE: Im using Virginia, so please make sure your SMTP endpoint with your region {: .notice}
Add SMTP Details to RunDeck: #
Add the below lines to rundeck-config.properties file.
vi /etc/rundeck/rundeck-config.properties
#SMTP Details
grails.mail.host=email-smtp.us-east-1.amazonaws.com
grails.mail.port=587
grails.mail.username=XXXXXXXXXXXXXXX #your access key
grails.mail.password=XXXXXXXXXXXXXXX #your secret key
[email protected] #your ses verified sender email
service rundeckd restart