Skip to content

Conversation

@droguljic
Copy link
Contributor

Exposing CloudFront as a independent component adds flexibility and supports use cases such as multiple origins per distribution. Three types of behaviors are supported:

  • S3, tailored for S3 origins with auto-configuration including cache policy oriented towards static assets and response headers policy with security headers.
  • LB, tailored for ALB origins with auto-configuration including cache policy for dynamic content and response headers policy with security headers.
  • Custom, configurable option with by default disabled caching.

@droguljic droguljic self-assigned this Dec 2, 2025
@droguljic droguljic force-pushed the feat/cloudfront branch 2 times, most recently from ed85a45 to bd7c17c Compare December 5, 2025 17:54
Exposing CloudFront as a independent component adds flexibility and
supports use cases such as multiple origins per distribution.
Three types of behaviors are supported:
- S3, tailored for S3 origins with auto-configuration including cache
policy oriented towards static assets and response headers policy with
security headers.
- LB, tailored for ALB origins with auto-configuration including cache
policy for dynamic content and response headers policy with security
headers.
- Custom, configurable option with by default disabled caching.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants