Let Me Amazon Q Developer That For You

Let Me Amazon Q Developer That For You

Amazon Q Developer often has the answer the customer ask. Or at least, it contributes to it. Should I be worried or ashamed to use it?

Published Oct 18, 2024
Some years ago, I was running a platform with some colleagues and it included answering to support requests (level 1 to 3) on top of the rest. Some questions were quite obvious and one could be tempted to answer Let Me Google That For You. It's clearly not a very nice answer. But it's an answer that I have started to give in the last few months with Amazon Q Developer. There is a catch though.
Amazon Q Developer has become really good at answering non immediately obvious support/architecture questions on AWS. That is to be expected but how many of us ask Amazon Q Developer such questions on a regular basis?
Here is the question which was asked:
In brief, we try to upload a document with PPTX format to S3 bucket and when we try to generate a PresignedURL with AWS UI Console, we can download the document with .pptx extension in its name so that the file can be properly opened/viewed.
But the same scenario is not working as expected with MSG file type. Meaning, after uploading the .msg file to S3, the metadata showing in AWS Console as application/vnd.ms-outlook (below screenshot)*** which is as expected. But when we try to download this object with PresignedURL, the file name doesn’t have an extension .msg which is causing issue for us. Can you please suggest on this!*
I didn't automatically come to the conclusion what the problem was and I simply passed the exact same text to Amazon Q Developer. Here is the beginning of the answer.
I understand your concern regarding the file extension issue when downloading .msg files using presigned URLs from S3. This is a common problem that occurs due to how S3 handles content types and file extensions. Let me explain the issue and provide some suggestions to resolve it.
The reason you're experiencing this behavior is that S3 doesn't automatically add file extensions when generating presigned URLs. Instead, it uses the Content-Type header to determine how the browser should handle the file. For .pptx files, the Content-Type is typically set correctly, allowing browsers to recognize and handle them properly. However, for .msg files, the Content-Type alone may not be sufficient for browsers to associate the correct file extension.
And the answer was immediately here in plain english. The problem lied in the browser not properly handling the Content-Type. I answered via email that Amazon Q Developer gave this answer proposing some timeslots to discuss the situation further. And during a subsequent meeting, we could confirm the conclusion already given and the changes needed in the system to make it work overall.
Three important elements.
  1. When asked the same question, Google wouldn't have returned anything close to the answer from Amazon Q Developer. You can try to give Google the same text.
  2. Despite the good answer from Amazon Q Developer, human interactions were needed to look at the bigger picture, confirm that the problem was correctly stated and find a solution to it.
  3. Don't be ashamed to use such tool to help you answer questions that you are supposed to be able to answer yourself. It only helps you to collect information and organize it. You are still responsible to make this information understood and to adapt the solution to the context... for the moment.
Have you already asked similar questions to Amazon Q Developer (in the IDE)?
 

Any opinions in this post are those of the individual author and may not reflect the opinions of AWS.

Comments