Do we need to instantiate the AmazonSimpleEmailServiceClient everytime we're gonna send an email for the entire lifespan of our application?

[penguinawesome]

We are planning to use the AWS SES C# SDK for sending emails coming from a background service / windows service that runs 24/7.

In the official documentation: https://aws.amazon.com/blogs/messaging-and-targeting/getting-started-with-amazon-ses-and-net/

The example was

using (var client = new AmazonSimpleEmailServiceClient(awsAccessKey, awsSecretKey))
   {
   		 client.SendEmail(request);
   }	

it looks like it is instantiating everytime it will send an email, do we really need to do this for our scenario? Or it would be better to instantiate it in a singleton? Just like in c# httpclient and httpclient factory.

[ashishdhingra]

Hi @firephantomassasin,

Good morning.

Thanks for posting guidance question. The lifetime of AmazonSimpleEmailServiceClient instance depends on your use case. It doesn't makes much difference whether you want to use the shared Singleton instance or a short-lived instance that is disposed off in the code execution block. Having a Singleton instance if the application is sending too many emails frequently avoids the expense and overhead of having too many HTTP connection pools.

I also notice that the access and secret key in the example are directly used in the AmazonSimpleEmailServiceClient constructor. This might be a fine for local development purposes, however for production environments, please refer Best practices for managing AWS access keys.

Thanks,
Ashish

[penguinawesome]

Hi @ashishdhingra,

But if we plan to make the AmazonSimpleEmailServiceClient singleton for the entire lifespan of our background service, would it be fine? Accessing it from different multiple threads as well to send many emails frequently.

[normj]

@firephantomassasin The service clients like AmazonSimpleEmailServiceClient are thread safe so you can use a single instance for the whole process. In general using a shared instance is the preferred pattern for performance. Most of creating the service client is light weight but if the service client has to determine the region and credentials based on the environment that can be slightly expensive.

[ashishdhingra]

Closing this issue since the required input(s) have been provided.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.