An option to accept email attachments as a CDN in the AWS's Simple Email Service

[CW-AnandRamesh]

Describe the feature

As of now, files have to be received within services as a stream or a byte array before passing the same to AWS SES for sending emails. A better approach would be to receive this file as a CDN Url directly in SES.

Use Case

Problem with current approach is to maintain scalability of our services with increasing requests and their corresponding memory profile management. By utilizing a CDN to share the attachment, memory resources of the service responsible for sharing this to AWS SES will be improved significantly.

Proposed Solution

No response

Other Information

No response

Acknowledgements

• [x] I may be able to implement this feature request
• [ ] This feature might incur a breaking change

AWS .NET SDK and/or Package version used

AWSSDK.SimpleEmail 3.7.300.54

Targeted .NET Platform

.NET 6

Operating System and version

Windows 11

[bhoradc]

Hello @CW-AnandRamesh,

Thank you for submitting the feature request. I understand the scalability and memory management improvements that direct CDN file support in AWS SES could bring to applications.

I will further review this with the .NET SDK team. Having said that, implementing it would primarily require changes on the AWS SES service side. Will keep you posted on further updates.

Regards, Chaitanya

[CW-AnandRamesh]

Thanks Chaitanya! Sure keep us posted

[ashishdhingra]

@CW-AnandRamesh Good afternoon. Although I'm not entirely sure, the functionality to receive this file as a CDN Url directly in SES might not be supported due to security reasons where a CDN Url could be exploited to point to malicious code. In such a case, it would be responsibility of calling code to download the file pointed out by CDN Url and use SendRawEmail API operation to send RawMessage containing attachment(s) in addition to other sections. Also you should try using the new AWSSDK.SimpleEmailV2. I will discuss with the team to get additional input and validate the use case.

Thanks, Ashish

[ashishdhingra]

P122374479

[ashishdhingra]

@CW-AnandRamesh Based on response from service team, SES does not currently support specifying attachments via URL. They will consider this request for a future product release. As of now we cannot provide ETA for the same. The feature, once supported, should be propagated to all the AWS SDK(s) via model and feature update.

Closing this issue for now since this request is in service team backlog.

Thanks, Ashish

[github-actions[bot]]

This issue is now closed.

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.