per-entity - Re: Re: [Per-Entity] TLS private keys and CDNs
Subject: Per-Entity Metadata Working Group
List archive
- From: <>
- To:
- Subject: Re: Re: [Per-Entity] TLS private keys and CDNs
- Date: Thu, 29 Sep 2016 20:04:15 +0000 (UTC)
- Ironport-phdr: 9a23:73RLLBWskB5+9NFXTizVvJlQu1HV8LGtZVwlr6E/grcLSJyIuqrYZRyPt8tkgFKBZ4jH8fUM07OQ6P+wHzFbqs/c+Fk5M7VyFDY9wf0MmAIhBMPXQWbaF9XNKxIAIcJZSVV+9Gu6O0UGUOz3ZlnVv2HgpWVKQka3AzFoPfz4EZL+iMG+1ub6u8GCIlZ+rWHiOvYqdV328l2Q5YEqht56J7x0xx3Vo2dZU+VQzmRtIFWV2RHm6ZSe5plmpnBbu+8r9shPeaT8Y6kiS7FEVnIrP31jt56jjgXKUQbavyhUaW4RiBcdWlGU4Q==
Nick asked me to forward this to list about some examples of serving content
over IPv4/IPv6 from AWS.
No TLS:
http://s3.dualstack.us-east-1.amazonaws.com/cjh-cam/aiken.html
http://cjh-cam.s3.dualstack.us-east-1.amazonaws.com/aiken.html
TLS, but with overall shared amazonaws.com cert:
https://s3.dualstack.us-east-1.amazonaws.com/cjh-cam/aiken.html
https://cjh-cam.s3.dualstack.us-east-1.amazonaws.com/aiken.html
The IPv6 support is a rather new feature, and as you can see, it is tied to a
region... so it's not truly a CDN (although it would be served from multiple
Availability Zones ).
IPv6 support isn't available for static hosting out of S3 bucket, nor for
CloudFront (which I think would ultimately be the better solution as you can
manage the cert and it is a true CDN with over 60 edge locations).
- [Per-Entity] TLS private keys and CDNs, David Walker, 09/21/2016
- Re: [Per-Entity] TLS private keys and CDNs, Nick Roy, 09/21/2016
- Re: [Per-Entity] TLS private keys and CDNs, David Walker, 09/21/2016
- Re: Re: [Per-Entity] TLS private keys and CDNs, chubing, 09/29/2016
- Re: [Per-Entity] TLS private keys and CDNs, David Walker, 09/21/2016
- Re: [Per-Entity] TLS private keys and CDNs, Nick Roy, 09/21/2016
Archive powered by MHonArc 2.6.19.