#CloudFront
Man, Pre:Invent is getting up to steam. This is a major paradigm shift for CloudFront Functions 😳

buff.ly/K3lbw6a
Amazon CloudFront Functions now supports network calls
Amazon CloudFront Functions now supports network calls via cf.fetch() and cf.beacon() methods, enabling edge-based authentication, personalization, and…
buff.ly
November 18, 2026 at 10:04 PM
AWS: CloudFront Functions network calls
November 20, 2026 at 3:30 PM
November 19, 2026 at 12:39 AM
Amazon CloudFront simplifies domain moves and onboarding for SaaS Manager

https://aws.amazon.com/about-aws/whats-new/2026/11/cloudfront-domain-moves-distribution-tenants
November 19, 2026 at 11:33 PM
Amazon CloudFront adds IP based routing and connection logs to SaaS Manager

https://aws.amazon.com/about-aws/whats-new/2026/11/cloudfront-ip-based-routing-connection-logging
November 19, 2026 at 11:33 PM
Amazon CloudFront Functions now supports network calls

Amazon CloudFront Functions can now make network calls and act on the response during a request. CloudFront Functions runs lightweight JavaScript at CloudFront edge locations to customize requests and responses. Previ...

#AWS #AmazonCloudfront
Amazon CloudFront Functions now supports network calls
Amazon CloudFront Functions can now make network calls and act on the response during a request. CloudFront Functions runs lightweight JavaScript at CloudFront edge locations to customize requests and responses. Previously, if your logic depended on data from another service, you had to use Lambda@Edge or move that logic to your origin. Now your functions can use real-time data to personalize, authenticate, or route requests at the edge, close to your viewers. With the new cf.fetch() method, your functions can call your API endpoints and use the response to decide how to handle each request. For example, you can check an AI agent's permissions and usage budget so that only authorized requests reach your API or MCP server, or send request signals to a security or fraud detection service to block or challenge bad traffic. With cf.beacon(), you can send analytics events in the background without slowing down viewers, even for content served from cache. Both methods take advantage of the origin settings already on your distribution, including origin access control (OAC), VPC origins, and connection reuse. Network calls are available at all CloudFront edge locations. They cost $0.10 per million calls, on top of CloudFront Functions invocation charges, and are included at no additional cost in the Pro plan and above in CloudFront flat-rate plans. To learn more, see https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/helper-functions-network-calls.html in the Amazon CloudFront Developer Guide and https://aws.amazon.com/cloudfront/pricing/.
aws.amazon.com
November 18, 2026 at 9:05 PM
Amazon CloudFront standard logging now supports CMCD and additional log fields

https://aws.amazon.com/about-aws/whats-new/2026/11/cloudfront-standard-logging-cmcd-fields
November 19, 2026 at 12:39 AM
Amazon CloudFront Announces WebSocket and gRPC Support for Origin Mutual TLS

https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-cloudfront-origin-mtls-websockets-grpc/
November 19, 2026 at 12:39 AM
Amazon CloudFront standard logging now supports CMCD and additional log fields

Amazon CloudFront standard logging now supports additional access log fields that were previously available only in CloudFront real-time logs. You can now include these fields in your standard ...

#AWS #AmazonCloudfront
Amazon CloudFront standard logging now supports CMCD and additional log fields
Amazon CloudFront standard logging now supports additional access log fields that were previously available only in CloudFront real-time logs. You can now include these fields in your standard logs and deliver them to Amazon S3, Amazon CloudWatch Logs, or Amazon Data Firehose, without setting up an additional data stream for real-time logs. The new fields include the IP address of the CloudFront server that handled the request, identifiers that separate traffic on a primary distribution from traffic on a staging distribution, and a media quality confidence score. They also include Common Media Client Data (CMCD) fields, which video players send with each request to report details like bitrate, buffer length, and playback session ID. Streaming teams can use these fields to match playback problems that viewers see with CloudFront delivery data, which makes troubleshooting faster. These fields are available in all CloudFront edge locations, and standard logging pricing applies. To learn more, see https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/standard-logging.html.
aws.amazon.com
November 18, 2026 at 11:05 PM
Amazon CloudFront standard logging now supports CMCD and additional log fields previously available only in real-time logs.
Amazon CloudFront standard logging now supports CMCD and additional log fields
Amazon CloudFront standard logging now supports CMCD and additional log fields previously available only in real-time logs.
aws-news.com
November 18, 2026 at 10:20 PM
Amazon CloudFront now enables seamless domain migration for SaaS platforms with single-request domain moves, no downtime, and HTTP serving during certificate configuration.
Amazon CloudFront simplifies domain moves and onboarding for SaaS Manager
Amazon CloudFront now enables seamless domain migration for SaaS platforms with single-request domain moves, no downtime, and HTTP serving during certificate configuration.
aws-news.com
November 19, 2026 at 10:51 PM
Amazon CloudFront simplifies domain moves and onboarding for SaaS Manager

CloudFront now enables seamless domain migration to multi-tenant distributions with zero downtime via OnDomainTakeover. Domains can serve HTTP traffic immediately while TLS certificates are configured.
November 19, 2026 at 11:03 PM
Amazon CloudFront now supports WebSocket and gRPC traffic with origin mutual TLS authentication for secure, bidirectional connections to application origins.
Amazon CloudFront Announces WebSocket and gRPC Support for Origin Mutual TLS
Amazon CloudFront now supports WebSocket and gRPC traffic with origin mutual TLS authentication for secure, bidirectional connections to application origins.
aws-news.com
November 18, 2026 at 7:25 PM
Amazon CloudFront Functions now supports network calls via cf.fetch() and cf.beacon() methods, enabling edge-based authorization, bot detection, and metrics collection without added latency.
Introducing network calls in Amazon CloudFront Functions
Amazon CloudFront Functions now supports network calls via cf.fetch() and cf.beacon() methods, enabling edge-based authorization, bot detection, and metrics collection without added latency.
aws-news.com
November 18, 2026 at 8:17 PM
Amazon CloudFront Functions now supports network calls via cf.fetch() and cf.beacon() methods, enabling edge-based authentication, personalization, and analytics without requiring Lambda@Edge.
Amazon CloudFront Functions now supports network calls
Amazon CloudFront Functions now supports network calls via cf.fetch() and cf.beacon() methods, enabling edge-based authentication, personalization, and analytics without requiring Lambda@Edge.
aws-news.com
November 18, 2026 at 8:17 PM
Amazon CloudFront adds IP based routing and connection logs to SaaS Manager

CloudFront now lets you segregate poor customers from rich ones using IP addresses. Because nothing says "modern SaaS architecture" like literally redlining your users by network location.
November 19, 2026 at 11:03 PM
🆕 Amazon CloudFront Functions now allow network calls via cf.fetch() and cf.beacon() for real-time data at the edge. Costs $0.10/million, included in Pro+ plans. For details, see Amazon CloudFront Developer Guide and pricing.

#AWS #AmazonCloudfront
Amazon CloudFront Functions now supports network calls
Amazon CloudFront Functions can now make network calls and act on the response during a request. CloudFront Functions runs lightweight JavaScript at CloudFront edge locations to customize requests and responses. Previously, if your logic depended on data from another service, you had to use Lambda@Edge or move that logic to your origin. Now your functions can use real-time data to personalize, authenticate, or route requests at the edge, close to your viewers. With the new cf.fetch() method, your functions can call your API endpoints and use the response to decide how to handle each request. For example, you can check an AI agent's permissions and usage budget so that only authorized requests reach your API or MCP server, or send request signals to a security or fraud detection service to block or challenge bad traffic. With cf.beacon(), you can send analytics events in the background without slowing down viewers, even for content served from cache. Both methods take advantage of the origin settings already on your distribution, including origin access control (OAC), VPC origins, and connection reuse. Network calls are available at all CloudFront edge locations. They cost $0.10 per million calls, on top of CloudFront Functions invocation charges, and are included at no additional cost in the Pro plan and above in CloudFront flat-rate plans. To learn more, see Helper methods for network calls in the Amazon CloudFront Developer Guide and Amazon CloudFront pricing.
aws.amazon.com
November 18, 2026 at 9:10 PM