跳至內容

CloudFront - Internal ELB Origin

0

Hi all, By Documentation to be able to use ELB as an Origin for a CloudFront Distribution it should be internet-facing. the question is why CloudFront is showing also Internal Load Balancers between the list of possibile Origin Domains that can be selected during the creation of a new Origin ? there is a way to use CloudFront with Private resources ?

已提問 3 年前檢視次數 9284 次
3 個答案
2
已接受的答案

No, you can't use an internal-only load balancer as an origin for CloudFront.

Why does it show in the list? Because the console is retrieving a list of all load balancers but there's no particular flag that says "this is an internal load balancer" versus "this is an internet-facing load balancer". That's determined by the subnet, route tables and public IP address assignment.

AWS
專家
已回答 3 年前
專家
已審閱 2 年前
AWS
專家
已審閱 3 年前
  • Hi,

    Is that still the case? When you create a load balancer now, you get am option to flag it internet-facing or internal.

    Thanks

  • Yes, my internal and public-facing are marked as such but both still list as possible origins. Seems like AWS should be able to tell if they have an public IP associated with it. Not perfect but better.

0

Yes, you can use an internal-only load balancer as an origin for CloudFront by leveraging CloudFront’s VPC Origin feature.

已回答 1 年前
0

This is now available using CloudFront VPC origins. You can use Application Load Balancers (ALBs), Network Load Balancers (NLBs), and EC2 instances in private subnets as VPC origins.

AWS
已回答 9 個月前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。