{"id":40999,"date":"2016-09-30T16:59:19","date_gmt":"2016-09-30T11:29:19","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=40999"},"modified":"2024-01-02T17:44:32","modified_gmt":"2024-01-02T12:14:32","slug":"aws-ses-integration-for-java-applications","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/aws-ses-integration-for-java-applications\/","title":{"rendered":"AWS SES Integration for Java Applications"},"content":{"rendered":"

Use Case<\/strong><\/p>\n

I came across a use-case, where I had to integrate Amazon Simple Email Service (SES)<\/strong> to send transactional emails<\/strong> from a JAVA application<\/a> using my own registered domain. This blog will guide the reader through the basic steps required for setting up or integrating Amazon SES with my JAVA application.<\/p>\n

About Amazon SES<\/strong><\/p>\n

It is an email service built and maintained by Amazon<\/strong>. It has cost efficient<\/strong>, reliable and scalable infrastructure<\/strong> ready to serve its customers. It can be used to send transactional email, marketing messages, or any other type of high-quality content to the customers. It can also be used to receive messages and deliver them to an Amazon S3 bucket, call your custom code via an AWS Lambda<\/a> function, or publish notifications to Amazon SNS.<\/p>\n

\"Image<\/p>\n

Requirements<\/strong><\/p>\n

1.<\/strong>\u00a0AWS Account<\/strong> with full access to Simple Email Service<\/strong> (SES)<\/strong>.
\n2.<\/strong> Registered domain<\/strong> to be used for sending email.
\n3.<\/strong> Working Java application<\/strong> for sending emails.<\/p>\n

Setting Up Amazon Simple Email Service (SES)<\/strong><\/p>\n

To start the setup we first need to have a domain from which we can send emails. Following sample domain was created:
\n\"SES-2-rt53\"<\/p>\n

Now, we have a sample domain, sample.videoready.tv.\u00a0<\/strong>Now we need to verify it so that we can setup Amazon Simple Email Service (SES) for this domain.<\/p>\n

Following are the steps to setup SES<\/strong><\/p>\n

1.<\/strong> Go to SES console<\/strong><\/p>\n

\"SES-1\"<\/p>\n

2.<\/strong>\u00a0On the left we have an option for Domain<\/strong>, click on the\u00a0domain option and then select Verify a New Domain:<\/strong>\"SES-3\"\u00a0<\/strong><\/p>\n

3.<\/strong> Enter the name of created domain and select the box to Generate DKIM Settings.\u00a0<\/strong>The domain is not verified util the records generated in this process are entered in DNS, in my case it is AWS Route 53<\/strong>. Following records will be generated:\"SES<\/p>\n

It gives an option to setup all records in AWS Route53<\/strong>. But I do not need to set the MX records<\/strong>, but in my use-case, I only needed to send emails and not receive any on my domain. So we setup only TXT<\/strong> and DKIM<\/strong> records in AWS Route53<\/strong>.<\/p>\n

\"SES<\/p>\n

\"SES<\/p>\n

After these records have been setup. The domain takes some time to be verified:\"SES-domain-vrf\"<\/p>\n

4. After the domain verification, we can send a test email from the SES console, to verify that it is functioning properly:\"SES_test-email\"<\/p>\n

Now that we have verified that the Amazon SES service is functioning properly. We move on to integrating this with the Java application<\/strong>. To integrate it with a java application we use SMTP setting\u00a0<\/strong>and then with AWS JAVA SDK<\/strong>. The SMTP settings generate SMTP credentials<\/strong>, which are setup in the application code. These credentials allow the application to use Amazon SES and use the verified domain to send mails.<\/p>\n

Setting Amazon SES for SMTP<\/strong><\/p>\n

On the left, we have an option SMTP Setting<\/strong>, click on it. Then select Generate My SMTP Credentials:<\/strong>\"SES<\/p>\n

Following credentials are generated, which need to be configured in the Java Application. So that application is authorized to use SES for sending emails:\"SES<\/p>\n

In the Java Application, we define SMTP_USERNAME <\/strong>and SMTP_PASSWORD<\/strong>, which authorizes the access to Amazon SES. Apart from SMTP credentials we set the sender and the receiver of the mail. Here, we also define the content and subject of the mail:\"ses-smtp1\"<\/p>\n

Setting Amazon SES with AWS JAVA SDK<\/strong><\/p>\n

If using AWS JAVA SDK<\/strong> to send emails, we can use AWS user secret key <\/strong>and access<\/strong> key<\/strong> to authorize Java application to send emails using Amazon SES. <\/strong>After installing the SDK we setup the keys as follows, to allow the access of application on Amazon SES:\"SES-SDK\"<\/p>\n

\"SES<\/p>\n

Now, the Java application’s integration with Amazon SES is complete, and emails can be sent using both SMTP<\/strong> as well as AWS JAVA SDK<\/strong> method. Using Amazon SES is good in such use-case because\u00a0if the application becomes heavy and it needs to send a\u00a0large number of emails.\u00a0The large volume can easily be handled by Amazon SES due to its scalable architecture.<\/p>\n

Hope this blog was of help to you.<\/p>\n","protected":false},"excerpt":{"rendered":"

Use Case I came across a use-case, where I had to integrate Amazon Simple Email Service (SES) to send transactional emails from a JAVA application using my own registered domain. This blog will guide the reader through the basic steps required for setting up or integrating Amazon SES with my JAVA application. About Amazon SES […]<\/p>\n","protected":false},"author":916,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":34},"categories":[1174,2348,446,1],"tags":[4076,248,2366,3233,1892,596,4844],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/40999"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/916"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=40999"}],"version-history":[{"count":1,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/40999\/revisions"}],"predecessor-version":[{"id":59826,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/40999\/revisions\/59826"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=40999"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=40999"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=40999"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}