ysugimoto/aws-lambda-image

User-Defined Metadata

Open

#19 opened on Apr 3, 2016

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (826 stars) (225 forks)batch import
enhancementhelp wanted

Description

It is possible to conserve User-Defined Metadata file information in new generated images

metadata like "x-amz-meta-"

Contributor guide

Tech stack
javascriptaws
Domain
backendcloud
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
JavaScript basicsAWS LambdaS3 metadata
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Review the Lambda function handler (likely index.js) to understand how images are processed and uploaded to S3. The current implementation likely reads the source image, resizes it, and writes to a destination bucket without preserving the original user defined metadata. To fix, modify the S3 putObject call to include the metadata from the source object, which can be retrieved from the Lambda event or by calling getObjectAttributes. Ensure that only allowed metadata headers are copied. See AWS S3 SDK documentation for copying object metadata.