aws-appsync-community
aws-appsync-community copied to clipboard
Feature request: $util functions to generate signed S3 URL's
I currently have an API that manages a lot of files stored in S3, with the file metadata stored in a DBD table. It would be nice if there was a VTL mapping template $util function that could generate a pre-signed URL for an S3 object right in the template. Currently, one has to create a lambda function that will generate these URL's, and thus incur the lambda startup time and billing. It would seem like a simple thing to add as the generation of the URL doesn't require any network requests, it just needs to generate the signature.
Thank you for your interest in AppSync. I will bring your request to the team.
This would be a HUGE win for AppSync as it would perfectly fill the file uploads void in GraphQL using a proper and proven cloud native architecture. 100ms Lambda bill time makes using a Lambda to sign a URL (or even a large array of signed URL's) a costly operation. While you could offset that cost by writing a simple containerized S3 URL signing service, that requires fronting access to the containers via API Gateway and only public API endpoints are supported by AppSync (unless that has changed?) which means there's no way to enforce authentication/authorization at the gateway level (still unsure whether passing through a JWT from AppSync to an API Gateway-fronted backend is a supported operation allowing OAuth 2 authentication/authorization at the service level.)
This single signed S3 URL $util function would completely eliminate the need for any and all of this.
@vlekakis Is there any update on this?
Is there any update on this?
@vlekakis Have there been any updates/development on this feature in the past 2 years? As already written in this issue, it would increase the use-cases of AppSync a lot.
Any updates on this? This would be definitely really handy.
This missing feature is the only reason my read-only AppSync queries need to invoke lambda, seems like an huge missing link between two of AWS's most prominent services.
@vlekakis Any updates/development on this? it has been several years and this would really make a large impact to many developers.
👍
+1
I'd also like to see this implemented. Has there been any activity on this?
Would be a great improvement ! Has anyone found a way to do this without a lambda ?
still open and unaddressed after 3 years?! cmon. There is a clear need for this functionality, please address ASAP.
+1
+1
It would be great!