Baixado 57 vezes
Carregado porAmazon Web Services LATAM
Iniciando com Amazon Cloudfront
Este documento discute como a Amazon CloudFront pode ser usada para distribuir conteúdo de forma escalável e eficiente, incluindo vídeos educacionais para milhares de alunos. A CloudFront permite que a Estratégia Concursos entregue mais de 230TB de dados por mês aos seus clientes de forma rápida e a um baixo custo.
Mais conteúdo relacionado
Semelhante a Iniciando com Amazon Cloudfront
![Melhorando o desempenho do seu WordPress [WordCamp São Paulo 2015]](https://cdn.slidesharecdn.com/ss_thumbnails/wordcampsaopaulo2015-151130144513-lva1-app6891-thumbnail.jpg?width=640&height=640&fit=bounds)
Iniciando com Amazon Cloudfront
- 1. © 2017, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Julio Faerman, AWS DevRel June 22, 2017 Iniciando com Amazon CloudFront
- 2. Nesta sessão: • Comoajudou a Estratégia Concursos • Compreender a Rede de Distribuição de Conteúdo • Benefícios de utilizar o CloudFront • Novas funcionalidades e aplicações • Eficiência de Custo • Começando a usar
- 3. “Os serviços daAmazon nos permite entregar conteúdo em escala” O Estratégia Concursos é referência nacional em cursos preparatórios para Concursos Públicos Entregamos PDFs e videoaulas (inclusive em alta resolução) aos alunos “O CloudFront nos permite entregar mais de 230TB por mês aos nossos clientes” - Ricardo Vale, CEO
- 4. O Desafio Entregar vídeoscom qualidade e velocidade aos alunos Garantir a escalabilidade Reduzir custos
- 5.
- 6. O que sãoCDNs e por que utilizá-las? • Distribuir conteúdo globalmente • Ampliar a distribuição de servidores de cache • Direcionar clientes para a melhor localidade • Armazenar conteúdo em caches de borda • Acelerar conteúdo dinâmico e estático • Melhorar escalabilidade, desempenho, custo e segurança de aplicações
- 7. O Amazon CloudFront CDNGlobal com capacidade e escala massiva Otimizado para performance e escala Funcionalidades de segurança embutidas Configuração totalmente self-service Relatórios robustos em tempo real Amazon CloudFront Conteúdo dinâmico, estático ou vídeos
- 8.
- 9. Componentes do CloudFront •Distributions • Origins • Behaviors • Restrictions, Error Pages, Tags • AWS WAF Web ACLs • Edge Locations • Price Classes distribution edge location Amazon CloudFront
- 10. Distributions distribution Domínio único docloudfront.net para referenciar objetos example: abc123.cloudfront.net Contém origem(s) das versões originais de conteúdo example: orign.mysite.com Suporte a HTTP e HTTPS example: https://cdn.mysite.com Contém configurações e tags example: origins, behaviors, error pages, restrictionsHINT: CNAME the CloudFront.net domain with Amazon Route 53 to personalize the distribution
- 11. Origins Qualquer bucket doS3 ou servidor HTTP público Restrição de acesso via OAI, URL assinado ou cabeçalho personalizado pela origem Conexões persistentes Conectividade SSL Full ou Half Bridge Conexões de proxy Conexões otimizadas com a AWS Custom Origin EC2 instance web app server Elastic/Application Load Balancing Amazon S3 Bucket
- 12. Behaviors • Path PatternMatching • Origin Selection • Headers • Query Strings / Cookies • Signed URL • SSL Certificates • Protocol Enforcement • Time To Live (TTL) • GZIP Compression
- 13. Behaviors • Path PatternMatching • Origin Selection • Headers • Query Strings / Cookies • Signed URL • SSL Certificates • Protocol Enforcement • Time To Live (TTL) • GZIP Compression Rotear para origens específicas Ajustar o protocolo HTTP Ajustar o método HTTP Ajustar cabeçalhos e opções Ajustar cache Repassar cookies e query strings Restringir acesso Ajustar compressão Altera o comportamento com base no path
- 14. Behaviors • Path PatternMatching • Origin Selection • Headers • Query Strings / Cookies • Signed URL • SSL Certificates • Protocol Enforcement • Time To Live (TTL) • GZIP Compression Configure uma ou muitas origens Na AWS ou em outros ambientes
- 15. Behaviors • Path PatternMatching • Origin Selection • Headers • Query Strings / Cookies • Signed URL • SSL Certificates • Protocol Enforcement • Time To Live (TTL) • GZIP Compression Encaminhar os cabeçalhos para a origem Fazer cache baseado em cabeçalhos Ajudar os TTLs de cache Deteccção de dispositivo None: optimized Whitelist: specify headers to forward All: dynamic content, no caching GET, HEAD, OPTIONS, PUT, POST, PATCH, DELETE
- 16. HEAD Identical to GETexcept that the server MUST NOT return a message-body in the response. Used for obtaining meta-information about the entity implied by the request without transferring the entity-body itself POST Used to request the origin server to accept the entity enclosed in the request as a new subordinate of the resource identified by the Request-URI in the Request- Line. PUT The fundamental difference between the POST and PUT requests is reflected in the different meaning of the Request-URI. PATCH Used to apply partial modifications to a resource DELETE Requests that the origin server delete the resource identified by the Request- URI OPTIONS Request for information about the communication options available on the request/response chain identified by the Request- URI GET Requests for content from the cache HTTP, HTTPS and RTMP Behaviors, HTTP Methods
- 17. 1) Variar aresposta por User Agent. Example: Desktop, Mobile, Tablet 2) Variar a resposta por idioma. Example: user would prefer Danish but will accept British English and other types of English. (Accept-Language: da, en- gb;q=0.8, en;q=0.7 ) 3) Variar a resposta por protocolo: Example: CloudFront-Forward-Proto detected and customer sent different content based on connection type. Mobile User (CloudFront-Is- Mobile-Viewer) Desktop User (CloudFront-Is- Desktop-Viewer) 1 1 2 3 Behaviors, Headers
- 18. Behaviors • Path PatternMatching • Origin Selection • Headers • Query Strings / Cookies • Signed URL • SSL Certificates • Protocol Enforcement • Time To Live (TTL) • GZIP Compression Repassa Query Strings e Cookies para a origem ?key=querystringparam Set-Cookie Header Alterar a resposta por Query String/Cookie Armazenar diversas cópias do objeto Usar a Query String / Cookie como Cache Key Forward All Forward Whitelist
- 19. Behaviors • Path PatternMatching • Origin Selection • Headers • Query Strings / Cookies • Signed URL • SSL Certificates • Protocol Enforcement • Time To Live (TTL) • GZIP Compression Restringir acesso ao conteúdo Conteúdo por assinatura, direitos digitais,… Políticas premoldadas ou personalizadas Aplicação cria e assina URLs CloudFront armazena caches baseados na URL ou cookie assinado
- 20. Customer Location http://mysite.com/asset.mp4?&Expires=1357034400 5&Signature=nitfHRCrtziwO2HwPfWw~yYDhUF5EwRunQA- j19DzZr vDh6hQ73lDx~-ar3UocvvRQVw6EkC~GdpGQyyOSKQim- TxAnW7d8F5Kkai9HVx0FIu- jcQb0UEmatEXAMPLE3ReXySpLSMj0yCd3ZAB4UcBCAqEijkytL6f 3fVYNGQI6&Key-Pair-Id=APKA9ONS7QCOWEXAMPLE 1)A solicitação primeiro passa por servidor de autenticação para validar o usuário e o pedido para então gerar a URL assinada 2) Uma URL assinada é enviada como un redirecionamento 302 3) A requisição é feita com a URL assinada, autenticada segundo a política de acesso e expiração do conteúdo 4) O CloudFront autentica a politica com a URL assinada, ajusta a chave de cache e envia o conteúdo ao cliente EC2 Auth Server Send content to requestor via cache edge www.mysite.com/asset.mp4 EC2 Auth Server Authenticate URL, Policy Statement, and Expiration CloudFront Logic CloudFront Edge Cache Signed URL
- 21. Behaviors • Path PatternMatching • Origin Selection • Headers • Query Strings / Cookies • Signed URL • SSL Certificates • Protocol Enforcement • Time To Live (TTL) • GZIP Compression Certificado compartilhado Certificado personalizado AWS Certificate Manager
- 22. Behaviors • Path PatternMatching • Origin Selection • Headers • Query Strings / Cookies • Signed URL • SSL Certificates • Protocol Enforcement • Time To Live (TTL) • GZIP Compression HTTP and HTTPS: Clientes podem usar ambos protocolos. Redirect HTTP to HTTPS: HTTP é redirecionado para HTTPS HTTPS Only: Clientes podem acessar apenas usando HTTPS
- 23. Behaviors • Path PatternMatching • Origin Selection • Headers • Query Strings / Cookies • Signed URL • SSL Certificates • Protocol Enforcement • Time To Live (TTL) • GZIP Compression Short TTL = Conteúdo Dinâmico Long TTL = Conteúdo Estático Reduz carga na origem If Modified Since Min, Max, Default TTL’s
- 24. Behaviors • Path PatternMatching • Origin Selection • Headers • Query Strings / Cookies • Signed URL • SSL Certificates • Protocol Enforcement • Time To Live (TTL) • GZIP Compression Accept-Encoding: gzip Compacta antes da entrega Otimiza consumo de banda e tempo de download Comprime arquivos de “Content- type” selecionados
- 25. Tipos Comprimíveis • PathPattern Matching • Origin Selection • Headers • Query Strings / Cookies • Signed URL • SSL Certificates • Protocol Enforcement • Time To Live (TTL) • GZIP Compression application/eot application/xml+rss image/svg+xml application/font application/x-font- opentype text/css application/font-sfnt application/x-font-truetype text/csv application/javascript application/x-font-ttf text/html application/json application/x-httpd-cgi text/javascript application/opentype application/x-javascript text/js application/otf application/x-mpegurl text/plain application/pkcs7-mime application/x-otf text/richtext application/truetype application/x-perl text/tab-separated-values application/ttf application/x-ttf text/xml application/vnd.ms- fontobject font/eot text/x-script application/xhtml+xml font/ttf text/x-component application/xml font/otf text/x-java-source font/opentype application/x-opentype
- 26. Restrictions, Errors eTagsa • Geographical Restriction • White List or Black List • Country Level Granularity • No Additional Charges • Caching Error Pages • 4XX, 5XX Codes • Cache Default Page • Cache Custom Page
- 27. AWS WAF WebACLs Proteção de camada 7 / Aplicação Propagação rápida Regras controláveis Itegração e Automação Custo simplificado
- 28. Edge Locations CloudFront contémuma rede global de pontos de presença Roteamento baseado em latência Localidade comum para CloudFront, WAF e Route53 Rede em expansão Rede otimizada e altamente conectada Projetado para alto desempenho
- 29. CloudFront Regional EdgeCaches Europe Frankfurt, Germany North America Ashburn, VA Portland, Oregon Asia Pacific Mumbai, India Singapore Sydney, Australia Seoul, South Korea Tokyo, Japan South America São Paulo, Brazil
- 30. CloudFront Regional EdgeCaches Origin Regional Edge Cache Reduzindo carga em custom origins Origin Edge Locations Arquitetura Anterior Arquitetura Atual
- 31. CloudFront Regional EdgeCaches • Não necessita de modificações nas distribuições • Regional Edge Caches são habilitados por padrão • Regional Edge Caches tem as mesmas funcionalidades que outras edge locations • Sem custo adicional • Melhoria de cache-hits mensurável pelo console
- 32. Amazon CloudFront GlobalContent Delivery Network North America Cities: 19 PoPs: 28 South America Cities: 2 PoPs: 3 Rio de Janeiro, Brazil (2) São Paulo, Brazil Europe / Middle East / Africa Cities: 15 PoPs: 24 Amsterdam, The Netherlands (2) Berlin, Germany Dublin, Ireland Frankfurt, Germany (5) London, England (4) Madrid, Spain Marseille, France Milan, Italy Munich, Germany Paris, France (2) Prague, Czech Republic Stockholm, Sweden Vienna, Austria Warsaw, Poland Zurich, Switzerland Ashburn, VA (3) Atlanta, GA (3) Chicago, IL Dallas/Fort Worth, TX (3) Hayward, CA Jacksonville, FL Los Angeles, CA (2) Miami, FL Minneapolis, MN Montreal, QC Newark, NJ New York, NY (3) Palo Alto, CA Philadelphia, PA San Jose, CA Seattle, WA South Bend, IN St. Louis, MO Toronto, ON CloudFront Regional Edge Caches Regional Edge Caches: 9 Oregon, N. Virginia, Frankfurt, Sao Paulo, Mumbai, Singapore, Seoul, Tokyo, Sydney 75 CloudFront Edge Locations (PoPs), 9 Regional Edge Caches (PoPs), 48 Cities, 5 Continents Edge location AWS Region / Regional Edge Cache Regional Edge Cache Asia Pacific Cities: 12 PoPs: 20 Chennai, India Hong Kong, China (3) Manila, the Philippines Melbourne, Australia Mumbai, India (2) New Delhi, India Osaka, Japan Seoul, Korea (3) Singapore (2) Sydney, Australia Taipei, Taiwan Tokyo, Japan (4)
- 33. All 68 PoPs, 41Cities, 22 Countries North America + Europe 45 PoPs, 27 Cities, 11 Countries North America + Europe + East and South East Asia* 62 PoPs, 37 Cities, 20 Countries Deliver Content Globally and Control Pricing to Fit Performance and Cost Objectives *does not include India (4) or Australia (2) PoPs CloudFront Components: Price Classes
- 34. Arquitetura de Referência corporatedata center AND, OR edge location Static Content Origin Amazon Route 53 EC2 instance web app server Elastic Load Balancing Amazon S3 bucket Dynamic Content Origin CNAME: cdn.mysite.com FOR: abc123.cloudfront.net regional edge cache AWS WAF
- 35. Beneficios do AmazonCloudFront • Acelerar a entrega de conteúdo web/mobile • Escalar aplicações reduzindo tráfego na origem • Proteger infraestruturas com segurança de borda • Economizar com transferência de dados • Aplicações diversas: • Media/Entertainment • Gaming • Digital Advertising • Software Downloads • Financial Services • Social Media • Education Technology • Hotel / Travel
- 36. Segurança e Regulamentaçãocom CloudFront • Regulamentações de segurança • PCI DSS Level 1 Compliance • ISO 9001, 27001, 27017, 27018 • Funcionalidades de segurança • Signed URL • Signed Cookies • Enforce HTTPS to origin • Support iOS ATS • Support for TLSv1 .1 and TLSv1.2 between edge and origin • Add/Modify Request Headers Forwarded From CloudFront to Origin • Integration with AWS Certificate Manager (SNI Certs from Amazon) • Integration with AWS WAF (web application firewall) • Geographic Restriction • IPv6 Support
- 37. CloudFront: Componente integradoda AWS Mobile Application Delivery Static and Dynamic Object Origin Web and Application Server Origin Enterprise Applications CloudFront, WAF, Route 53 CloudFront, WAF, Route 53, Elastic Transcoder CloudFront, WAF, Route 53, Elemental / Elastic Transcoder CloudFront, WAF, Route 53
- 38. Amazon CloudFront andAWS WAF Pricing Pricing Components Gigabytes Transferred Request Rates (HTTP, HTTPS) -GET, HEAD -PUT, POST, PATCH, OPTIONS, DELETE Custom SSL Certificate AWS WAF Pricing -Web ACL -Rule -Requests AWS WAF Amazon CloudFront
- 39. Use Lambda@Edge • Lambda@Edgeé uma extensão do AWS Lambda para executar código Node.js code em edge locations. • Traga seu código para mais próximo do usuário final, melhorando a experiência de uso de sua aplicação. Continuous scaling No servers to manage Never pay for idle – no cold servers Globally distributed Sign up for preview: https://pages.awscloud.com/lambda-at-edge-preview.html
- 40. Write once, runeverywhere
- 41. CloudFront Triggers for Lambda@EdgeFunctions
- 42. • User Properties– Identify a user’s location • Client Device properties - Delete or modify headers • A/B Testing - “Flip a coin” to select a version of content • Ad content - Rewrite URLs • Pretty URLs – Avoid revealing your origin directory structure Content Customization
- 43. Visitor Validation • Handlingbots • Detect search engine bots and filter traffic • Confirm valid sessions • View user-agent to confirm legitimacy of request
- 44. Eficiência de Custodo CloudFront • Custo sob demanda • Mesmo custo para conteúdo estático ou dinâmico • Mesmo custo para HTTP / HTTPS • Desconto para reserva de capacidade • Certificados SSL/TLS gratúitos com ACM • Sem custos de plataforma • Sem custos de consultas de DNS para registros ALIAS do Route 53 que resolvem para distribuições do CloudFront PriceperGB Data Transfer Data Transfer Economies of Scale Public Rates Private Rates
- 45. Eficiência de Custodo CloudFront EC2 instance web app server Elastic/Application Load Balancing Amazon S3 Bucket Data Transfer/Processing ($/GB) Requests ($/Requests) = Total Charge $ $ $ = $$$
- 46. Eficiência de Custodo CloudFront EC2 instance web app server Elastic/Application Load Balancing Amazon S3 Bucket Data Transfer/Processing ($/GB) Requests ($/Requests) CDN + + 3rd Party CDN Charges = Total Charge $ $ $ $ = $$$$
- 47. $ Eficiência de Custodo CloudFront EC2 instance web app server Elastic/Application Load Balancing Amazon S3 Bucket CloudFront + CloudFront = Total Charge $ $ $ = $
- 48. On Demand Pricing PublishedOnline Regional Tiered Rates Pay As You Go Free Tier Reserved Capacity Reduced Pricing Contracts Tailored to Use Case Variable Term Price Classes Optimize for Cost Regional Data Transfer User Controlled Turn On/Off Any Time Amazon CloudFront Pricing No Data Transfer Fees from AWS Origins to Amazon CloudFront No Charge for Regional Edge Cache No Charge for SSL/TLS Certs from Amazon Certificate Manager No Charge for Shared CloudFront certificates Low Monthly Charge for Custom Hosted Certificates Same Rate, Same Network for HTTP and HTTPS traffic Simple Request Fees Covered by Existing Customer Service Plan
- 49. Disponibilidade: Amazon CloudFrontGlobal View *Data from Cedexis, Last 30 Days, Availability measured over All Regions. November 2016
- 50. DDoS Mitigation Sem impactode disponibilidade mesmo sob DDoS Trafego sob ataque
- 51. Relatórios do CloudFront:Access Logs W3C Extended Log Format Delivered to S3 Reporting Permissions Controlled Delivered Several Times / Hour
- 52. Relatórios do CloudFront Richmetrics for more detailed insight • Cache Statistics • Usage Charts • Popular Objects • Browser, Operating Systems, Devices, Locations, & Top Referrers • CloudWatch Metrics Integration • Additional Metrics with Lambda • 1 -2 Minute Availability
- 53. Amazon CloudFront: Novidades •ACM Import • IPv6 • HTTP/2 • Query String Whitelisting ACM v6 • Cost Allocation Tagging • Origin Security Options • New Edge Locations
- 54. Getting Started withAmazon CloudFront • Developer Guide • Tutorials and Blogs • Webinars and Videos Streaming videos to millions of mobile app users via Amazon CloudFront CDN Deploy preconfigured protections using AWS WAF FREE TIER! 50 GB Data Transfer Out and 2,000,000 HTTP and HTTPS Requests each month for one year
- 55. AWS CloudFront PartnerProgram https://aws.amazon.com/cloudfront/partners Amazon CloudFront
- 56.
- 57. Foco na experiênciade uso • Ajustar o desempenho em proporções globais • Operar em escala através de indústries • Operar durante alto tráfego como eventos de e-commerce • Video ao vivo ou sob-demanda • Distribuição digital de Aplicações Corporativas e jogos • Atualizações de Software • Distribuição de aplicações Mobile
- 58. © 2017, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Julio Faerman, AWS DevRel Track 5 16:55 – 17:40 Deep Dive em aceleração de entrega de conteúdo, APIs e aplicações utilizando Amazon CloudFront e Lambda@Edge
- 59.
- 60. Ainda não temo App oficial do AWS Summit São Paulo? http://amzn.to/2rOcsVy Não deixe de avaliar as sessões no app!
- 61. © 2017, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Julio Faerman, AWS DevRel June 22, 2017 Iniciando com Amazon CloudFront Obrigado
Notas do Editor
- #3 Understanding cloudfront: description, size, history, integration with AWS, why people use it Benefits: Application acceleration, dynamic content delivery, vod and live video delivery, application protection, static content delivery, scaling to meet demand. Market specific features including gaming, ecommerce, software delivery, media/entertainment, digital advertising, and social media, reporting/analytics and visibility into the application and audience, security. New Features: HTTP/2, IPv6, SSL, New Edge Locations, Mid-Tier Caching (performance) Getting Started: include sign up, partner channel, direct engagement Pricing: include public pricing, committed pricing, price benefits, fees, AWS WAF Use cases: let’s review a few key customer use cases being highlighted here at reinvent this year. I’d like to talk about GoPro and Sony Ven.ue
- #4 30 segundos para apresentar a empresa, rapidamente
- #5 Os 4 (máximo) maiores desafios do projeto, que foram resolvidos pela utilização da nuvem da AWS
- #6 Diagrama de solução, e explicar a solução, vantagens, etc
- #9 Show you what we’ve done in each of these areas and.
- #11 Distributions: A distribution specifies the location or locations of the original version of your files. A distribution has a unique CloudFront.net domain name (e.g. abc123.cloudfront.net) that you can use to reference your objects through the global network of edge locations. If you wish, you can also map your own domain name (e.g. www.example.com) to your distribution. You can create distributions to either download your content using the HTTP or HTTPS protocols, or stream your content using the RTMP protocol.
- #12 CloudFront can accept any publically addressable Amazon S3 or HTTP server as an origin. This means that
- #13 With Behaviors, you really get to experience the power of what CloudFront can do for your web / mobile application. Behaviors allow you to have granular control of the CloudFront CDN and provide the ability to enforce certain policies, change results based on request type, control the cacheablity of object, and many more. Let’s walk through some of the behaviors and start with Path Pattern Matching.
- #14 Path Pattern Matching provides you with
- #15 Distributions: A distribution specifies the location or locations of the original version of your files. A distribution has a unique CloudFront.net domain name (e.g. abc123.cloudfront.net) that you can use to reference your objects through the global network of edge locations. If you wish, you can also map your own domain name (e.g. www.example.com) to your distribution. You can create distributions to either download your content using the HTTP or HTTPS protocols, or stream your content using the RTMP protocol.
- #16 Distributions: A distribution specifies the location or locations of the original version of your files. A distribution has a unique CloudFront.net domain name (e.g. abc123.cloudfront.net) that you can use to reference your objects through the global network of edge locations. If you wish, you can also map your own domain name (e.g. www.example.com) to your distribution. You can create distributions to either download your content using the HTTP or HTTPS protocols, or stream your content using the RTMP protocol.
- #17 NOTES: PUT/POST will use a CloudFront edge as a proxy to send back to origin. CloudFront proxies ONLY, it is NOT a store and forward CDN meaning you can’t use PUT or POST to pre-load a cache. Caches are only filled upon a request, or GET.
- #18 There are many other examples to highlight, this slide just shows a few common VARY actions. Also common is the CORS support where an asset in one domain can be served by an origin in another that has been set up to share assets. This has been a very popular feature request.
- #19 Some web applications use query strings to send information to the origin. A query string is the part of a web request that appears after a ? character; the string can contain one or more parameters separated by & characters. In the following example, the query string includes two parameters, color=red and size=large:
- #20 A signed URL includes additional information, for example, an expiration date and time, that gives you more control over access to your content. This additional information appears in a policy statement, which is based on either a canned policy or a custom policy.
- #21 CloudFront can be used to authenticate content. For added security encrypt the connection via SSL. Signed URL’s require a canned or custom policy statement to be made for CloudFront. The customer will specify parameters such as: Query Sting (?color, image_size, etc.) Expiration time/date in UNIX format IP Address They will also need to include in the signed URL the: Hashed and signed version of the policy statement Key Pair ID used to generate the signature
- #22 Distributions: A distribution specifies the location or locations of the original version of your files. A distribution has a unique CloudFront.net domain name (e.g. abc123.cloudfront.net) that you can use to reference your objects through the global network of edge locations. If you wish, you can also map your own domain name (e.g. www.example.com) to your distribution. You can create distributions to either download your content using the HTTP or HTTPS protocols, or stream your content using the RTMP protocol.
- #23 Explain why this is something customers would like to do.
- #24 You can control how long your objects stay in a CloudFront cache before CloudFront forwards another request to your origin. Reducing the duration allows you to serve dynamic content. Increasing the duration means your users get better performance because your objects are more likely to be served directly from the edge cache. A longer duration also reduces the load on your origin.
- #25 Serving Compressed Files When Your Origin Server Is Running IIS By default, IIS does not serve compressed content for requests that come through proxy servers such as CloudFront. If you're using IIS and if you configured IIS to compress content by using the httpCompressionelement, change the value of the noCompressionForProxies attribute to false so IIS will return compressed content to CloudFront. In addition, if you have compressed objects that are requested less frequently than every few seconds, you might have to change the values of frequentHitThreshold and frequentHitTimePeriod. For more information, refer to the IIS documentation on the Microsoft website. Serving Compressed Files When Your Origin Server Is Running NGINX When CloudFront forwards a request to the origin server, it includes a Via header. This causes NGINX to interpret the request as proxied and, by default, NGINX disables compression for proxied requests. If your version of NGINX includes the gzip_proxied setting, change the value to any so that NGINX will return compressed content to CloudFront. For more information, see the NGINX documentation for the module ngx_http_gzip_module.
- #26 Serving Compressed Files When Your Origin Server Is Running IIS By default, IIS does not serve compressed content for requests that come through proxy servers such as CloudFront. If you're using IIS and if you configured IIS to compress content by using the httpCompressionelement, change the value of the noCompressionForProxies attribute to false so IIS will return compressed content to CloudFront. In addition, if you have compressed objects that are requested less frequently than every few seconds, you might have to change the values of frequentHitThreshold and frequentHitTimePeriod. For more information, refer to the IIS documentation on the Microsoft website. Serving Compressed Files When Your Origin Server Is Running NGINX When CloudFront forwards a request to the origin server, it includes a Via header. This causes NGINX to interpret the request as proxied and, by default, NGINX disables compression for proxied requests. If your version of NGINX includes the gzip_proxied setting, change the value to any so that NGINX will return compressed content to CloudFront. For more information, see the NGINX documentation for the module ngx_http_gzip_module.
- #27 You can configure CloudFront to respond to requests using a custom error page when your origin returns an HTTP 4xx or 5xx status code. For example, when your custom origin is unavailable and returning 5xx responses, CloudFront can return a static error page that is hosted on Amazon S3. You can also specify a minimum TTL to control how long CloudFront caches errors. For more information, see Customizing Error Responses in the Amazon CloudFront Developer Guide. Select the HTTP status code that you want CloudFront to return to the viewer along with the custom error page. Tags: AWS generates a cost allocation report as a comma-separated value (CSV file) with your usage and costs aggregated by your active tags. You can apply tags that represent business categories (such as cost centers, application names, or owners) to organize your costs across multiple services. Tag Restrictions The following basic restrictions apply to tags: Maximum number of tags per resource – 10 Maximum key length – 128 Unicode characters Maximum value length – 256 Unicode characters Valid values for key and value – a-z, A-Z, 0-9, space, and the following characters: _ . : / = + - and @ Tag keys and values are case sensitive Don't use aws: as a prefix for keys; it's reserved for AWS use
- #28 Distributions: A distribution specifies the location or locations of the original version of your files. A distribution has a unique CloudFront.net domain name (e.g. abc123.cloudfront.net) that you can use to reference your objects through the global network of edge locations. If you wish, you can also map your own domain name (e.g. www.example.com) to your distribution. You can create distributions to either download your content using the HTTP or HTTPS protocols, or stream your content using the RTMP protocol.
- #29 Distributions: A distribution specifies the location or locations of the original version of your files. A distribution has a unique CloudFront.net domain name (e.g. abc123.cloudfront.net) that you can use to reference your objects through the global network of edge locations. If you wish, you can also map your own domain name (e.g. www.example.com) to your distribution. You can create distributions to either download your content using the HTTP or HTTPS protocols, or stream your content using the RTMP protocol.
- #30 HELPS ALL KINDS OF CONTENT. THAT’S WHY WE ARE MAKING THIS A DEFAULT FEATURE OF OUR CDN. Examples include user generated content (UGC) such as video, photos, or artwork; e-commerce assets such as product photos and videos; and news/event related content that may suddenly find new popularity. tends to become long tail over time, suffering from cache misses at the edge locations. A new default CloudFront feature that brings more of your content close to your viewers, even when the content is not popular to stay at our edge caches. This helps improve performance for your viewers.
- #31 The request will go back to your origin only when the object is not cached at either the edge locations or the regional edge cache. This helps lower the load on your origin resources.
- #32 Customers can calculate the cache-hit ratios using the following metrics on the console– hitcount, misscount, total bytes, bytes from misses etc. If there are any questions on dynamic content or proxy requests, Content which we can determine as dynamic at request time does not flow through the mid-tier, but goes directly to the origin. Such content is defined as having a cache-behavior configured to forward all headers. Proxy methods PUT/POST/PATCH/OPTIONS/DELETE flows directly to the origin from the Edge locations and does not proxy through the mid-tier.
- #33 Three PoPs in Japan – two in Tokyo and one in Osaka We differ from traditional CDNs who may have thousands of edge locations by strategically placing our PoP locations globally. Due to improved network connectivity and peering, modern CDNs are just as effective in availability and performance without the need to have thousands of edge locations.
- #35 Highlight the cost aspects of this
- #36 Default Architectures Performance Scale Cost Security Static and Dynamic Content I am now typing some stuff in the background.
- #41 - Route users to the POP’s closest to them, instead of back to one central server - All without the operational burden of managing and deploying code in multiple locations
- #45 SSL/TLS certificates provisioned through AWS Certificate Manager are free. You pay only for the AWS resources you create to run your website or application. For the latest ACM pricing information, see the AWS Certificate Manager Service Pricing page on the AWS website.
- #49 On Demand Pricing -Published On Line and Available for Modelling with our Simple Monthly Calculator -Free Tier: 50 GB Data Transfer Out and 2,000,000 HTTP and HTTPS Requests each month for one year Reserved Capacity Pricing Price Classes Common to All Pricing Programs
- #50 Evolution of how we measure performance. Talk about inaccuracy of backbone and last mile and how we now rely on RUM
- #51 We not only build for performance, we also build for reliability and availability, and are a leader in Availability among top tier of CDNs. Globally, the CDN performs at the highest level of availability.
- #52 Main Point: For static/cachable content, CloudFront performs among the top tier of CDNs. CloudFront is the CDN shown in “pink”. The 50th percentile measurement is
- #53 We saw earlier how CloudFront was able to handle a large DDoS attack.
- #54 Logging delivered as cloudwatch can give us additional information outside the six Flash talks on monitoring and alarms
- #55 Suite of CloudFront reports include Usage Charts Cache Statistics & Popular Objects Browser, Operating Systems, Devices, Locations, Top Referrers Requests, Bytes Downloaded, Bytes Uploaded, 4xx Errors, 5xx Errors & Total Error Rate Choose daily, hourly, 5-min, or 1-min granularity
- #57 Getting started with Amazon CloudFront is easy to do and we offer a multitude of resources to get you on your way. First, check out the Amazon CloudFront Developer Guide available on the AWS website and on Kindle as a free e-book. In the document you’ll find detailed information on how to use the service, how it works, code samples and links to valuable resources. Of course there is no other learning experience than actually building something yourself. Get first hand experience by working through one of our tutorials such as… -Streaming videos to millions of mobile app users via Amazon CloudFront CDN -Deploy preconfigured protections using AWS WAF Find answers to your questions on the AWS Blog and learn from our CloudFront experts at Office Hours hosted monthly on the Webinar and Video section of the CloudFront page. We are here to help!
- #58 This year we are happy to announce the CloudFront Partner Program. This program validates and certifies key AWS partners who can enable CloudFront CDN specific workloads for AWS customers We are excited to launch with 23 partners at Re:Invent who have been through a detailed audit and shown the ability and success to deliver both enablement and ongoing management of CloudFront for customers You can find the full list of partners by region in the list below.
- #59 For those of our partners out there today who are interested in becoming a CloudFront partner we have several benefits: Listing on CloudFront Website Technical, Sales and Marketing Support Flexible CloudFront Pricing Options POC Funding Links to Blog Posts Funded Case Studies Early Entry Into Private Beta’s Access to Exclusive Programs and Promotions If this is something you are interested in and have customers who utilize CDN specific workloads please reach out to us via the email alias seen below.
- #60 Add MapBox
- #62 GoPro Plus = new cloud subscription service that brings the GoPro experience together Access your GoPro footage from anywhere so you can create and share your stories (videos/photos) Unlocks additional benefits with apps (e.g. additional soundtracks in Quik for desktop) What we’ve launched: Two new mobile apps: Capture (aka GoPro mobile app) Quik for mobile One new desktop app: Quik for desktop (aka GoPro desktop app) New cloud subscription service: GoPro Plus (available in the U.S. initially) All of these are compatible with previous GoPro cameras (e.g. HERO4) All apps are free and standalone Cloud service offers free trial and unlocks additional benefits for the apps