What happens to outstanding requests when a Cloudfront origin is changed.

When you edit the origin of a CloudFront distribution to change the source to a different load balancer, any outstanding requests that have not completed yet will likely be dropped or terminated.

Here's why:

1. The outstanding requests are currently being served by the original load balancer specified as the origin in the CloudFront distribution. If you change the origin to a different load balancer, CloudFront will need to establish new connections to the new load balancer.

2. CloudFront is a stateless service, meaning it does not maintain persistent connections with clients. When you edit the origin, CloudFront will start routing new requests to the new load balancer, but it may not be able to complete outstanding requests served by the original load balancer.

3. Depending on the timing and specifics of the change, any outstanding requests still in progress may experience connection termination or timeouts. CloudFront may attempt to establish connections to the new load balancer for new requests, potentially leaving the outstanding requests in an incomplete state.

To minimize disruption to your users, it's essential to plan origin changes during periods of low traffic or implement mechanisms to gracefully handle in-flight requests during the transition. This could involve configuring your applications to retry requests or implementing error handling strategies to notify users of interrupted operations. Additionally, monitoring tools can help track the impact of origin changes and identify any issues that arise during the transition

Hope it clarifies and if does I would appreciate answer to be accepted so that community can benefit for clarity, thanks ;)