Option for configuring existing cloudfront

Open
#65 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
32/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
aws
Domain
cloud, infrastructure

Research direction

The issue names no files, tests, or entry points. Begin by locating the sample's deployment configuration for the Lambda, S3 bucket, and CloudFront distribution; done means an option can target an existing CloudFront distribution while preserving its existing origin settings.

Written by the indexing model from the issue text.

Description

Hello. Thanks for this sample. I believe this will create a new s3 bucket for hosting static files and also create a cloudfront distribution for serving those files/contents. Please let me know if I'm mistaken.

Could you please provide an option so that I can deploy the lambda that will connect to an existing cloudfront?

I already have cloudfront distribution serving from existing s3 bucket. I'd prefer to keep that infrastructure since they have other configs made. Giving the option for using existing cloudfront will also be useful if contents are served from an origin other than s3 bucket.

Dominant language
JavaScript
Stars
73
Forks
21
Avg merge
19h 45m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws-samples/lambdaedge-openidconnect-samples

All issues in aws-samples/lambdaedge-openidconnect-samples

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.