# AWS Certificate Manager AWS service for provisioning, managing, and renewing public and private SSL/TLS certificates. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Bring your own client certificate for backend mTLS in Amazon API Gateway DevFeed: [Bring your own client certificate for backend mTLS in Amazon API Gateway]() Original publisher: [Read original article]() Author: Biswanath Mukherjee Published: 2026-09-08T21:46:39Z Content type: tutorial Language: en Sources: [AWS Compute Blog]() Topics: [Amazon API Gateway](), [AWS Certificate Manager](), [Amazon Elastic Container Service](), [nginx]() Tags: [amazon-api-gateway](), [amazon-elastic-container-service](), [announcements](), [architecture](), [authentication](), [aws-certificate-manager](), [aws-fargate](), [intermediate-200](), [rest-api](), [tls]() ### AI overview This tutorial shows how to configure Amazon API Gateway to present a third-party or AWS Private CA-issued client certificate for outbound mTLS to an Amazon ECS backend. ### Source excerpt Enterprises that use Amazon API Gateway often want to bring their own client certificate for backend mutual TLS (mTLS) authentication. With API Gateway, you can now use a third-party or AWS Private CA-issued client certificate for the outbound mTLS handshake. In this post, you build a REST API with an outbound mTLS connection to an Amazon ECS backend. ## AWS Certificate Manager will discontinue email validation to prove domain validation for certificates DevFeed: [AWS Certificate Manager will discontinue email validation to prove domain validation for certificates]() Original publisher: [Read original article]() Author: Adam Aboudi Published: 2026-08-13T21:23:00Z Content type: article Language: en Sources: [AWS Security Blog]() Topics: [AWS Certificate Manager](), [Amazon Web Services](), [Command-line interface]() Tags: [announcements](), [aws](), [aws-certificate-manager](), [aws-management-console](), [blog](), [cli](), [dns](), [foundational-100](), [security-blog](), [security-identity-compliance](), [validation]() ### AI overview AWS Certificate Manager will discontinue support for email-validated public certificates by September 30, 2027. Customers using email validation must migrate to DNS validation, ahead of the CA/B Forum's March 15, 2028 deadline. The article explains the rationale, timeline, and how to identify affected certificates in the ACM console or AWS CLI. ### Source excerpt Today, we're announcing that AWS Certificate Manager (ACM) will discontinue support for email-validated public certificates by September 30, 2027. If you use email validation for your ACM public certificates, you need to migrate to DNS validation before that date. This change aligns with the Certification Authority/Browser (CA/B) Forum's industry-wide deprecation of email-based domain validation and [...] ## Preparing for Shorter SSL/TLS Certificate Lifetimes DevFeed: [Preparing for Shorter SSL/TLS Certificate Lifetimes]() Original publisher: [Read original article]() Author: Emily Huang Published: 2026-03-06T16:50:10Z Content type: article Language: en Sources: [Heroku]() Topics: [Heroku](), [TLS (Transport Layer Security)](), [certificates](), [AWS Certificate Manager](), [maintenance](), [Security]() Tags: [automation](), [certificates](), [heroku](), [maintenance](), [news](), [security](), [ssl](), [tls]() ### AI overview Heroku explains that publicly trusted SSL/TLS certificates will have shorter maximum lifetimes, with a 200-day maximum beginning March 15, 2026. Users who manually manage certificates for Heroku applications will need more frequent renewals, while Heroku Automated Certificate Management handles certificate renewal automatically. ### Source excerpt The web browser and certificate authority industry is shortening the maximum allowed lifetime of TLS certificates. These changes will improve security on the Web, but you may have to change certificate maintenance practices for apps you run on Heroku. The good news is that if you're using Heroku Automated Certificate Management, no changes are required: [...] The post Preparing for Shorter SSL/TLS Certificate Lifetimes appeared first on Heroku. ## Vapor: Multi-level Subdomains DevFeed: [Vapor: Multi-level Subdomains]() Original publisher: [Read original article]() Author: Joe Dixon Published: 2023-06-28T12:35:00Z Content type: release Language: en Sources: [Laravel Blog]() Topics: [Vapor](), [AWS Certificate Manager](), [Deployment](), [Command-line interface](), [Amazon API Gateway]() Tags: [api-gateway](), [aws-certificate-manager](), [cli](), [deployment](), [feature](), [new-feature]() ### AI overview Vapor now supports deploying applications to multi-level subdomains. Users must explicitly include the subdomain in an AWS Certificate Manager certificate and Vapor domain configuration, then perform a full deployment using the Vapor CLI. ### Source excerpt Vapor has always made it straightforward to deploy your application to a custom domain, subdomain, or even wildcard subdomain. However, it's only been possible to utilize single-level subdomains - me... ## Why Websites Should Use HTTPS for Privacy and Security DevFeed: [Why Websites Should Use HTTPS for Privacy and Security]() Original publisher: [Read original article]() Author: umer Published: 2017-01-18T00:00:00Z Content type: opinion Language: en Sources: [Code Ahoy - Articles]() Topics: [Security](), [HTTP](), [Web](), [AWS Certificate Manager](), [Google](), [Chrome](), [Firefox](), [Mozilla]() Tags: [aws-certificate-manager](), [certificates](), [chrome](), [cloud](), [firefox](), [google](), [http](), [mozilla](), [security]() ### AI overview The article argues that websites should use HTTPS to reduce exposure of users' communications and protect privacy. It describes Google Chrome and Firefox warnings for some HTTP pages and notes that free HTTPS certificates are available through Let's Encrypt and AWS Certificate Manager. ### Source excerpt We live in a day and age where we simply cannot take our right to privacy for granted. When we communicate over unprotected channels, we expose our messages to everyone who happens to be along the way: The WiFi hotspots, corporate IT providers, ISPs, cloud providers, can listen in to our communication. We leave a trail of digital footprints behind. When aggregated, it can reveal information about ourselves. Eavesdroppers and intruders can make inferences about our behaviors and intentions: ISPs can determine what types of news stories we are interested in, employers can monitor our activities even on personal devices at work, look at our searches, see our messages, all when we communicate over unprotected channels. Google has been urging site owners to switch to HTTPS for many years now. They started using HTTPS as a ranking indicator for their search results. To tighten the screws, Chrome, starting with version 56 that is coming soon, will start showing "not secure" alerts on sites that collect login or credit card information over HTTP. Firefox will also start displaying a red icon in the address bar as well as an in-context warning for pages that ask users to login over HTTP. While I don't know the real reason that compel Google to drive the HTTPS campaign, it's a great direction for the future of the web, a direction that we should all support. So how do you make your website secure? It's way easier to secure sites with HTTPS these days than it used to be. In the past, obtaining a digital certificate that is required for HTTPS required paperwork and hundreds of dollars. This is no longer the case. Let's Encrypt is a certificate authority that provides FREE certificates to anyone. It's backed by organizations such as Mozilla, Facebook and Google to name a few. Let's Encrypt makes it possible for anyone to have an HTTPS website for free. As an alternative, if you host your servers on the AWS, Certificate Manager provides free certificates and handle certificate re