serverless-nextjs/serverless-next.js

Forward s3 bucket CORS configuration to s3 bucket component

Open

#595 opened on Sep 9, 2020

View on GitHub
 (1 comment) (1 reaction) (0 assignees)TypeScript (3,998 stars) (447 forks)batch import
enhancementgood first issue

Description

Is your feature request related to a problem? Please describe. Currently there is no way to configure CORS of the created bucket via this component

Describe the solution you'd like Expose a new configuration input, called bucketCors

Describe alternatives you've considered Manually update cors configuration after bucket is created

Contributor guide

Tech stack
typescriptnodejsaws
Domain
cloudbackendinfrastructure
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.
1-2 days
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.
clear
Prerequisites
Basic AWS S3 knowledgeUnderstanding of serverless components
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate the S3 bucket component code in the repository (likely in packages/serverless components/aws s3 or similar). Look for where the bucket is created using AWS SDK or CloudFormation. Add a new optional input parameter for CORS configuration (e.g., bucketCors) and pass it to the bucket creation call. Ensure backward compatibility by defaulting to undefined. Review existing tests and examples for guidance.