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.

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 added the Don't merge Do not merge this PR label Jan 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Don't merge Do not merge this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants