Each ELB will have it's own public DNS. You will need a CNAME for your domains to map them to the ELB so that your users can get to your ELB like this: www.mysite.com.
CloudFront will push an S3 bucket to Amazon's edge network - putting that content closer to it's requesting user. Your domain names shouldn't point directly to this content, however your site (on your EC2 instance) will consist of HTML files that reference your CloudFront distribution.
Now you'll have one or more servers processing requests and CloudFront serving the content. Very plausible.
If the content is static it makes more sense to think in terms of CloudFront pointing at S3.
For Amazon S3 buckets configured to host static websites, you also have the option of creating an ‘Alias’ record that maps to your S3 website bucket. Alias records have two advantages: first, unlike CNAMEs, you can create an Alias record for your zone apex (e.g. example.com, instead of www.example.com), and second, queries to Alias records are free of charge.
发布评论
评论（3）
每个 ELB 都有自己的公共 DNS。您需要一个 CNAME 以便您的域能够映射将它们添加到 ELB，以便您的用户可以像这样访问您的 ELB：www.mysite.com。
CloudFront 将把 S3 存储桶推送到 Amazon 的边缘网络 - 让该内容更接近其发出请求的用户。您的域名不应直接指向此内容，但是您的网站（在 EC2 实例上）将包含引用您的 CloudFront 分发。
现在，您将拥有一台或多台处理请求的服务器，并由 CloudFront 提供内容。非常有道理。
祝你好运。
乍得
Each ELB will have it's own public DNS. You will need a CNAME for your domains to map them to the ELB so that your users can get to your ELB like this: www.mysite.com.
CloudFront will push an S3 bucket to Amazon's edge network - putting that content closer to it's requesting user. Your domain names shouldn't point directly to this content, however your site (on your EC2 instance) will consist of HTML files that reference your CloudFront distribution.
Now you'll have one or more servers processing requests and CloudFront serving the content. Very plausible.
Best of luck.
Chad
您可以将 ELB 或 EC2 实例指向云端，这将使您的动态内容更接近用户。
http: //aws.amazon.com/about-aws/whats-new/2012/05/13/amazon-cloudfront-now-supports-dynamic-content/
You can point your ELB or EC2 instance to cloudfront and this will push your dynamic content closer to your users.
http://aws.amazon.com/about-aws/whats-new/2012/05/13/amazon-cloudfront-now-supports-dynamic-content/
如果内容是静态的，那么考虑指向 S3 的 CloudFront 更有意义。
对于配置为托管静态网站的 Amazon S3 存储桶，您还可以选择创建映射到 S3 网站存储桶的“别名”记录。别名记录有两个优点：首先，与 CNAME 不同，您可以为您的区域顶点创建别名记录（例如 example.com，而不是 www.example.com），其次，对别名记录的查询是免费的。
If the content is static it makes more sense to think in terms of CloudFront pointing at S3.
For Amazon S3 buckets configured to host static websites, you also have the option of creating an ‘Alias’ record that maps to your S3 website bucket. Alias records have two advantages: first, unlike CNAMEs, you can create an Alias record for your zone apex (e.g. example.com, instead of www.example.com), and second, queries to Alias records are free of charge.