Asking Amazon Q for fixing the Bug Regarding Uploading an Attachment using Amazon SES

This is a submission for the Amazon Q Developer "Quack The Code" Challenge: Crushing the Command Line Preface If you have read my previous post, I got the bug when uploading the attachment. Since I would like to crack the bug. Let's ask Amazon Q! What I Built Just a simple prompt for fixing the code. Prompt: My AWS Lambda function has a bug when uploading the attachment using ses service, Please examine Demo Summary of the changes The commit made by Amazon Q "Fixed" Email Okay, but it's not really fixed my code. However, it makes me think there is some documentation or news regarding the limit. I found it here. So, I decided to ask Amazon Q to increase the attachment limit. Of course, the issue still exists; it seems the PDF has been corrupted when sending the email. I've checked the size when downloading, it has the correct size. But the attached file size was doubled. So, I decided to ask Amazon Q to compress it. Very unfortunate, I can't open the zip file! So, I think the bug occurs when sending the base64 data, which introduces a corrupted file. I hope it will be fixed when I identify the SDK with Amazon Q later. But not now, sorry. Code Repository bervProject / MergePDFOnline Merge PDF Online MergePDFOnline Merge PDF Online LICENSE Copyright (C) 2022 Bervianto Leo Pratama This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details. You should have received a copy of the GNU Affero General Public License along with this program. If not, see . View on GitHub How I Used Amazon Q Developer Writing a prompt with specific context. Sadly, it's not fixed now. I hope it will, later.

May 6, 2025 - 16:06

Asking Amazon Q for fixing the Bug Regarding Uploading an Attachment using Amazon SES

This is a submission for the Amazon Q Developer "Quack The Code" Challenge: Crushing the Command Line

Preface

If you have read my previous post, I got the bug when uploading the attachment. Since I would like to crack the bug. Let's ask Amazon Q!

What I Built

Just a simple prompt for fixing the code.

Prompt:

My AWS Lambda function has a bug when uploading the attachment using ses service, Please examine

Demo

Summary of the changes

The commit made by Amazon Q
"Fixed" Email

Okay, but it's not really fixed my code. However, it makes me think there is some documentation or news regarding the limit. I found it here. So, I decided to ask Amazon Q to increase the attachment limit.

Of course, the issue still exists; it seems the PDF has been corrupted when sending the email. I've checked the size when downloading, it has the correct size. But the attached file size was doubled. So, I decided to ask Amazon Q to compress it.

Very unfortunate, I can't open the zip file! So, I think the bug occurs when sending the base64 data, which introduces a corrupted file.

I hope it will be fixed when I identify the SDK with Amazon Q later. But not now, sorry.

Code Repository

bervProject / MergePDFOnline

Merge PDF Online

MergePDFOnline

Merge PDF Online

LICENSE

    Copyright (C) 2022 Bervianto Leo Pratama

    This program is free software: you can redistribute it and/or modify
    it under the terms of the GNU Affero General Public License as published
    by the Free Software Foundation, either version 3 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU Affero General Public License for more details.

    You should have received a copy of the GNU Affero General Public License
    along with this program.  If not, see .

View on GitHub

How I Used Amazon Q Developer

Writing a prompt with specific context.

Sadly, it's not fixed now. I hope it will, later.