# 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.

## Private certificate authority support in Amazon Bedrock AgentCore Identity

DevFeed: [Private certificate authority support in Amazon Bedrock AgentCore Identity](<https://devfeed.tech/articles/private-certificate-authority-support-in-amazon-bedrock-agentcore-identity-141213.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/private-certificate-authority-support-in-amazon-bedrock-agentcore-identity/>)

Author: Aastha Paul

Published: 2026-11-18T20:53:41Z

Content type: tutorial

Language: en

Sources: [Artificial Intelligence](<https://devfeed.tech/sources/artificial-intelligence.md>)

Topics: [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [certificates](<https://devfeed.tech/topics/certificates.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [AWS Certificate Manager](<https://devfeed.tech/topics/aws-certificate-manager.md>), [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [agents](<https://devfeed.tech/tags/agents.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-vpc-lattice](<https://devfeed.tech/tags/amazon-vpc-lattice.md>), [application-load-balancer](<https://devfeed.tech/tags/application-load-balancer.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [aws](<https://devfeed.tech/tags/aws.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [certificate-authorities](<https://devfeed.tech/tags/certificate-authorities.md>), [certificate-authority](<https://devfeed.tech/tags/certificate-authority.md>), [identity](<https://devfeed.tech/tags/identity.md>), [identity-providers](<https://devfeed.tech/tags/identity-providers.md>), [idp](<https://devfeed.tech/tags/idp.md>), [private](<https://devfeed.tech/tags/private.md>), [self-hosted](<https://devfeed.tech/tags/self-hosted.md>), [support](<https://devfeed.tech/tags/support.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [trust](<https://devfeed.tech/tags/trust.md>)

### AI overview

Amazon Bedrock AgentCore Identity can validate self-hosted private IdPs using a PEM root or intermediate CA certificate stored in Secrets Manager or S3 and referenced by a credential provider. The provider must use a private endpoint and VPC Lattice; the certificate must be valid, PEM encoded, no larger than 16 KB, and stored in the same Region. Secrets Manager also requires the same account, while cross-account S3 requires a bucket owner account ID and access policy. AgentCore reads the certificate at provider creation or update, so changes to the stored file require an update call that includes certificateConfigurations. To rotate with less downtime, trust both old and new CAs, update the IdP server certificate, then remove the old CA and update again. CloudWatch exposes EarliestCertificateDaysToExpiry. AgentCore does not check CRLs or OCSP, so trust persists until the server certificate expires or its CA is removed. Protect write access to the trust store; the certificate itself contains no private key.

### Source excerpt

Amazon Bedrock AgentCore Identity now supports private certificate authorities (CAs), so your agents can connect to self-hosted identity providers that use a private CA. This post shows how to issue an IdP certificate with AWS Private CA, configure a credential provider to trust it, rotate the CA, and protect the certificate.

## Your SSL certificates can now last 200 days at most: The real risk isn't renewal

DevFeed: [Your SSL certificates can now last 200 days at most: The real risk isn't renewal](<https://devfeed.tech/articles/your-ssl-certificates-can-now-last-200-days-at-most-the-real-risk-isn-t-renewal-133712.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/ssl-certificate-lifespan-200-days-renewal/>)

Author: SitePoint Sponsors

Published: 2026-11-14T06:07:40Z

Content type: article

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [AWS Certificate Manager](<https://devfeed.tech/topics/aws-certificate-manager.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>)

Tags: [automated](<https://devfeed.tech/tags/automated.md>), [automatic](<https://devfeed.tech/tags/automatic.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [certificates](<https://devfeed.tech/tags/certificates.md>), [expire](<https://devfeed.tech/tags/expire.md>), [fail](<https://devfeed.tech/tags/fail.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [risk](<https://devfeed.tech/tags/risk.md>), [security](<https://devfeed.tech/tags/security.md>), [ssl](<https://devfeed.tech/tags/ssl.md>), [ssl-certificates](<https://devfeed.tech/tags/ssl-certificates.md>)

### AI overview

Certificate lifetimes are capped at 200 days now, fall to 100 days in March 2027, then 47 days in 2029. The shorter schedule chiefly affects manually renewed certificates; managed hosting and CDN setups that already renew automatically may see little change. Automation can fail quietly when credentials or validation break, a renewed certificate is not activated, timers are too long, or certificates sit on systems the automation does not cover. An expired certificate can block visitors and break checkouts, logins, and integrations. The excerpt recommends inventorying certificates and owners, replacing fixed renewal timers with lifetime-based timing, and checking certificates externally as visitors receive them. It proposes warning at about one quarter of certificate life remaining and escalating at one tenth, rather than using fixed 30-day and seven-day alerts. Site24x7 is presented as one cloud monitoring option that reads installed certificates and tracks expiry details.

### Source excerpt

SSL certificates now last 200 days at most, dropping to 47 by 2029. See why automated renewals still fail quietly and how to monitor certificates before they expire. Continue reading Your SSL certificates can now last 200 days at most: The real risk isn't renewal on SitePoint.

## HTTPS and TLS

DevFeed: [HTTPS and TLS](<https://devfeed.tech/articles/https-and-tls-89175.md>)

Original publisher: [Read original article](<https://specification.website/spec/security/https-tls/>)

Author: Joost de Valk

Published: 2026-10-15T00:00:00Z

Content type: tutorial

Language: en

Sources: [The Website Specification](<https://devfeed.tech/sources/the-website-specification.md>)

Topics: [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [AWS Certificate Manager](<https://devfeed.tech/topics/aws-certificate-manager.md>), [let's encrypt](<https://devfeed.tech/topics/let-s-encrypt.md>), [Certificate Transparency](<https://devfeed.tech/topics/certificate-transparency.md>)

Tags: [1-3](<https://devfeed.tech/tags/1-3.md>), [acme](<https://devfeed.tech/tags/acme.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [diffie-hellman](<https://devfeed.tech/tags/diffie-hellman.md>), [ecdh](<https://devfeed.tech/tags/ecdh.md>), [exchange](<https://devfeed.tech/tags/exchange.md>), [http](<https://devfeed.tech/tags/http.md>), [https](<https://devfeed.tech/tags/https.md>), [over](<https://devfeed.tech/tags/over.md>), [redirect](<https://devfeed.tech/tags/redirect.md>), [required](<https://devfeed.tech/tags/required.md>), [security](<https://devfeed.tech/tags/security.md>), [serve](<https://devfeed.tech/tags/serve.md>), [tls](<https://devfeed.tech/tags/tls.md>)

### AI overview

This tutorial explains HTTPS and TLS, including which protocol versions to enable, how to configure certificates and redirects, and how to verify a server. It also describes TLS 1.2 key-exchange changes and hybrid post-quantum key agreement for TLS 1.3, while distinguishing that work from the separate migration of certificate authentication.

### Source excerpt

Serve every page over HTTPS using TLS 1.2 or 1.3, redirect plain HTTP to HTTPS, and disable obsolete SSL and early TLS versions on every host you control.

## Let's Encrypt to Cut SSL Certificate Lifetimes to 64 Days in February 2027

DevFeed: [Let's Encrypt to Cut SSL Certificate Lifetimes to 64 Days in February 2027](<https://devfeed.tech/articles/let-s-encrypt-to-cut-ssl-certificate-lifetimes-to-64-days-in-february-2027-85190.md>)

Original publisher: [Read original article](<https://it.slashdot.org/story/26/10/12/0211238/lets-encrypt-to-cut-ssl-certificate-lifetimes-to-64-days-in-february-2027>)

Author: EditorDavid

Published: 2026-10-12T03:09:00Z

Content type: news

Language: en

Sources: [Slashdot](<https://devfeed.tech/sources/slashdot.md>)

Topics: [AWS Certificate Manager](<https://devfeed.tech/topics/aws-certificate-manager.md>), [certificates](<https://devfeed.tech/topics/certificates.md>), [Certificate Transparency](<https://devfeed.tech/topics/certificate-transparency.md>)

Tags: [encryption](<https://devfeed.tech/tags/encryption.md>), [security](<https://devfeed.tech/tags/security.md>), [tls](<https://devfeed.tech/tags/tls.md>)

### AI overview

Let's Encrypt plans to reduce its default TLS certificate lifetime from 90 days to 64 days starting February 10, 2027, with a further reduction to 45 days planned for 2028. Existing certificates will remain valid until they expire, and the transition will not revoke valid certificates. Administrators with hardcoded renewal intervals should review their configurations; staging certificates will be available for testing from October 14, 2026. The article also reports shorter reuse periods for domain authorizations.

### Source excerpt

Let's Encrypt "will shorten the default validity period of its TLS certificates from 90 days to 64 days, starting February 10, 2027," reports the blog Linuxiac: All certificates issued or renewed from that date will have a 64-day lifespan unless users explicitly select one of the shorter options already available: 45 or six days. Existing certificates will remain valid until their expiration dates. Let's Encrypt expects the final 90-day certificate to expire on May 11, 2027. The organization also confirmed no valid certificates will be revoked during the transition. To help administrators prepare, Let's Encrypt will introduce 64-day certificates in its staging environment on October 14, 2026, allowing users to test their renewal setups before the change reaches production. The move is part of a broader effort to improve web security by reducing how long compromised or incorrectly issued certificates remain usable... Looking further ahead, the organization plans to reduce the default certificate lifetime again, this time to 45 days in 2028. That makes the upcoming 64-day limit an intermediate step rather than the final destination. "Administrators using cron jobs or scripts with hardcoded renewal intervals should review their configurations," the article suggests. "Another upcoming change concerns domain validation. Let's Encrypt will reduce the period during which a previously completed domain authorization can be reused from 30 days to 10 days. In 2028, that period will shrink further to just seven hours." Read more of this story at Slashdot.

## Building a certificate authority for the whole Internet

DevFeed: [Building a certificate authority for the whole Internet](<https://devfeed.tech/articles/building-a-certificate-authority-for-the-whole-internet-61628.md>)

Original publisher: [Read original article](<https://blog.cloudflare.com/cloudflare-certificate-authority/>)

Author: Steve Goldsmith

Published: 2026-09-29T13:00:00Z

Content type: news

Language: en

Sources: [Cloudflare Blog](<https://devfeed.tech/sources/cloudflare-blog.md>)

Topics: [enterprise certificate authority certificates](<https://devfeed.tech/topics/enterprise-certificate-authority-certificates.md>), [Certificate Transparency](<https://devfeed.tech/topics/certificate-transparency.md>), [AWS Certificate Manager](<https://devfeed.tech/topics/aws-certificate-manager.md>), [Web](<https://devfeed.tech/topics/web.md>), [SSL](<https://devfeed.tech/topics/ssl.md>), [digital sovereignty](<https://devfeed.tech/topics/digital-sovereignty.md>)

Tags: [birthday-week](<https://devfeed.tech/tags/birthday-week.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [cryptography](<https://devfeed.tech/tags/cryptography.md>), [merkle-tree](<https://devfeed.tech/tags/merkle-tree.md>), [post-quantum](<https://devfeed.tech/tags/post-quantum.md>), [security](<https://devfeed.tech/tags/security.md>), [ssl](<https://devfeed.tech/tags/ssl.md>), [tls](<https://devfeed.tech/tags/tls.md>)

### AI overview

Cloudflare is applying to become a public certificate authority, seeking inclusion in major browser root programs and agreeing to acquire a trusted GlobalSign root to expand certificate reach. It also plans to pursue post-quantum certificates, but has not begun issuing certificates.

### Source excerpt

Twelve years after launching Universal SSL, Cloudflare is applying to become a certificate authority. By combining an established root, an ACME-first approach, and Merkle Tree Certificates, we are building a post-quantum CA for the open web.

## AWS Elastic Beanstalk introduces Cluster Mode

DevFeed: [AWS Elastic Beanstalk introduces Cluster Mode](<https://devfeed.tech/articles/aws-elastic-beanstalk-introduces-cluster-mode-42086.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/aws/aws-elastic-beanstalk-introduces-cluster-mode/>)

Author: Channy Yun (윤석찬)

Published: 2026-09-17T19:20:21Z

Content type: release

Language: en

Sources: [AWS News Blog](<https://devfeed.tech/sources/aws-news-blog.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Provisioning](<https://devfeed.tech/topics/provisioning.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [AWS Certificate Manager](<https://devfeed.tech/topics/aws-certificate-manager.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [application](<https://devfeed.tech/tags/application.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-certificate-manager](<https://devfeed.tech/tags/aws-certificate-manager.md>), [aws-elastic-beanstalk](<https://devfeed.tech/tags/aws-elastic-beanstalk.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [code](<https://devfeed.tech/tags/code.md>), [compute](<https://devfeed.tech/tags/compute.md>), [container](<https://devfeed.tech/tags/container.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [dockerfiles](<https://devfeed.tech/tags/dockerfiles.md>), [https](<https://devfeed.tech/tags/https.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [launch](<https://devfeed.tech/tags/launch.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [news](<https://devfeed.tech/tags/news.md>), [provisioning](<https://devfeed.tech/tags/provisioning.md>)

### AI overview

AWS Elastic Beanstalk introduces a fully managed Cluster Mode that runs multiple applications on shared infrastructure powered by Amazon EKS. It also highlights AI-assisted environment analysis, GitHub Actions deployment, observability, traffic-splitting deployments with rollback, autoscaling, secrets management, and HTTPS by default.

### Source excerpt

Run an application on AWS Elastic Beanstalk Cluster Mode without provisioning or operating the compute underneath it. You provide a container image or source code; Elastic Beanstalk with service-operated compute creates and operates the environment that runs it.

## Scale multi-tenant SaaS with per-tenant version pinning using Amazon CloudFront

DevFeed: [Scale multi-tenant SaaS with per-tenant version pinning using Amazon CloudFront](<https://devfeed.tech/articles/scale-multi-tenant-saas-with-per-tenant-version-pinning-using-amazon-cloudfront-49984.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/dotnet/scale-multi-tenant-saas-with-per-tenant-version-pinning-using-amazon-cloudfront/>)

Author: Akber Rizwan Shaik

Published: 2026-09-15T18:14:41Z

Content type: tutorial

Language: en

Sources: [.NET on AWS Blog](<https://devfeed.tech/sources/net-on-aws-blog.md>)

Topics: [Software as a service](<https://devfeed.tech/topics/saas.md>), [releases](<https://devfeed.tech/topics/releases.md>), [Amazon Elastic Container Service](<https://devfeed.tech/topics/amazon-elastic-container-service.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>), [ASP.NET](<https://devfeed.tech/topics/aspnet.md>), [AWS Certificate Manager](<https://devfeed.tech/topics/aws-certificate-manager.md>), [Parameter](<https://devfeed.tech/topics/parameter.md>), [container](<https://devfeed.tech/topics/container.md>)

Tags: [amazon-cloudfront](<https://devfeed.tech/tags/amazon-cloudfront.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-elastic-container-service](<https://devfeed.tech/tags/amazon-elastic-container-service.md>), [application-load-balancer](<https://devfeed.tech/tags/application-load-balancer.md>), [asp-net](<https://devfeed.tech/tags/asp-net.md>), [aws-certificate-manager](<https://devfeed.tech/tags/aws-certificate-manager.md>), [downtime](<https://devfeed.tech/tags/downtime.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [load-balancer](<https://devfeed.tech/tags/load-balancer.md>), [net](<https://devfeed.tech/tags/net.md>), [parameter](<https://devfeed.tech/tags/parameter.md>), [saas](<https://devfeed.tech/tags/saas.md>), [scale](<https://devfeed.tech/tags/scale.md>), [uncategorized](<https://devfeed.tech/tags/uncategorized.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

This tutorial presents an architecture for per-tenant version pinning in multi-tenant SaaS applications. It uses CloudFront multi-tenant distributions, a version parameter, DynamoDB as a tenant catalog, and version-specific ASP.NET deployments on Amazon ECS to support incremental releases, tenant onboarding, regional routing, custom domains, and zero-downtime version switching.

### Source excerpt

Multi-tenant SaaS providers often need to control which application version each tenant runs, a practice called per-tenant version pinning, so they can roll out new releases incrementally and move tenants between versions without downtime and manual changes. A common approach is to configure the Application Load Balancer with hostname-based routing rules, but this doesn't scale. [...]

## 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](<https://devfeed.tech/articles/bring-your-own-client-certificate-for-backend-mtls-in-amazon-api-gateway-4658.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/bring-your-own-client-certificate-for-backend-mtls-in-amazon-api-gateway/>)

Author: Biswanath Mukherjee

Published: 2026-09-08T21:46:39Z

Content type: tutorial

Language: en

Sources: [AWS Compute Blog](<https://devfeed.tech/sources/aws-compute-blog.md>)

Topics: [Amazon API Gateway](<https://devfeed.tech/topics/amazon-api-gateway.md>), [AWS Certificate Manager](<https://devfeed.tech/topics/aws-certificate-manager.md>), [Amazon Elastic Container Service](<https://devfeed.tech/topics/amazon-elastic-container-service.md>), [nginx](<https://devfeed.tech/topics/nginx.md>)

Tags: [amazon-api-gateway](<https://devfeed.tech/tags/amazon-api-gateway.md>), [amazon-elastic-container-service](<https://devfeed.tech/tags/amazon-elastic-container-service.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [aws-certificate-manager](<https://devfeed.tech/tags/aws-certificate-manager.md>), [aws-fargate](<https://devfeed.tech/tags/aws-fargate.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>), [tls](<https://devfeed.tech/tags/tls.md>)

### 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](<https://devfeed.tech/articles/aws-certificate-manager-will-discontinue-email-validation-to-prove-domain-validation-for-certificates-4676.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/security/aws-certificate-manager-will-discontinue-email-validation-to-prove-domain-validation-for-certificates/>)

Author: Adam Aboudi

Published: 2026-08-13T21:23:00Z

Content type: article

Language: en

Sources: [AWS Security Blog](<https://devfeed.tech/sources/aws-security-blog.md>)

Topics: [AWS Certificate Manager](<https://devfeed.tech/topics/aws-certificate-manager.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>)

Tags: [announcements](<https://devfeed.tech/tags/announcements.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-certificate-manager](<https://devfeed.tech/tags/aws-certificate-manager.md>), [aws-management-console](<https://devfeed.tech/tags/aws-management-console.md>), [blog](<https://devfeed.tech/tags/blog.md>), [cli](<https://devfeed.tech/tags/cli.md>), [dns](<https://devfeed.tech/tags/dns.md>), [foundational-100](<https://devfeed.tech/tags/foundational-100.md>), [security-blog](<https://devfeed.tech/tags/security-blog.md>), [security-identity-compliance](<https://devfeed.tech/tags/security-identity-compliance.md>), [validation](<https://devfeed.tech/tags/validation.md>)

### 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 [...]

## How to set up a Custom Domain for FusionAuth using AWS CloudFront

DevFeed: [How to set up a Custom Domain for FusionAuth using AWS CloudFront](<https://devfeed.tech/articles/how-to-set-up-a-custom-domain-for-fusionauth-using-aws-cloudfront-43253.md>)

Original publisher: [Read original article](<https://fusionauth.io/blog/cloudfront>)

Author: Mark Robustelli

Published: 2025-03-21T00:00:00Z

Content type: tutorial

Language: en

Sources: [FusionAuth](<https://devfeed.tech/sources/fusionauth-blog.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [AWS Certificate Manager](<https://devfeed.tech/topics/aws-certificate-manager.md>), [SSL](<https://devfeed.tech/topics/ssl.md>), [domain](<https://devfeed.tech/topics/domain.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [cloudfront](<https://devfeed.tech/tags/cloudfront.md>), [configure](<https://devfeed.tech/tags/configure.md>), [distribution](<https://devfeed.tech/tags/distribution.md>), [dns](<https://devfeed.tech/tags/dns.md>), [guide](<https://devfeed.tech/tags/guide.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [setup](<https://devfeed.tech/tags/setup.md>), [ssl](<https://devfeed.tech/tags/ssl.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>)

### AI overview

A tutorial for configuring a custom domain for a hosted FusionAuth instance through AWS CloudFront. It covers obtaining an SSL certificate with AWS Certificate Manager, validating it through DNS, and creating a CloudFront distribution.

### Source excerpt

Learn how to configure a custom domain for FusionAuth using AWS CloudFront. This guide covers SSL certificate setup, DNS configuration, and distribution settings.

## GitHub Actions - OIDC integration with AWS no longer requires pinning of intermediate TLS certificates

DevFeed: [GitHub Actions - OIDC integration with AWS no longer requires pinning of intermediate TLS certificates](<https://devfeed.tech/articles/github-actions-oidc-integration-with-aws-no-longer-requires-pinning-of-intermediate-tls-certificates-73451.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2023-07-13-github-actions-oidc-integration-with-aws-no-longer-requires-pinning-of-intermediate-tls-certificates>)

Author: Allison

Published: 2023-07-13T21:01:38Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [AWS Certificate Manager](<https://devfeed.tech/topics/aws-certificate-manager.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [aws](<https://devfeed.tech/tags/aws.md>), [certificates](<https://devfeed.tech/tags/certificates.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [openid-connect](<https://devfeed.tech/tags/openid-connect.md>), [tls](<https://devfeed.tech/tags/tls.md>)

### AI overview

GitHub Actions OIDC integration with AWS now trusts GitHub Actions' trusted root certificate authorities instead of relying on pinned intermediary certificate thumbprints. GitHub says no action is needed from customers.

### Source excerpt

GitHub Actions - OpenId Connect (OIDC) integration with AWS is now optimized to avoid pinning any intermediary certificate thumbprints. While configuring GitHub as an OIDC IdP (ID Provider), AWS now...

## Vapor: Multi-level Subdomains

DevFeed: [Vapor: Multi-level Subdomains](<https://devfeed.tech/articles/vapor-multi-level-subdomains-3962.md>)

Original publisher: [Read original article](<https://laravel.com/blog/vapor-multi-level-subdomains>)

Author: Joe Dixon

Published: 2023-06-28T12:35:00Z

Content type: release

Language: en

Sources: [Laravel Blog](<https://devfeed.tech/sources/laravel-blog.md>)

Topics: [Vapor](<https://devfeed.tech/topics/swift-vapor.md>), [AWS Certificate Manager](<https://devfeed.tech/topics/aws-certificate-manager.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>), [Amazon API Gateway](<https://devfeed.tech/topics/amazon-api-gateway.md>)

Tags: [api-gateway](<https://devfeed.tech/tags/api-gateway.md>), [aws-certificate-manager](<https://devfeed.tech/tags/aws-certificate-manager.md>), [cli](<https://devfeed.tech/tags/cli.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [feature](<https://devfeed.tech/tags/feature.md>), [new-feature](<https://devfeed.tech/tags/new-feature.md>)

### 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...

## Getting Partial AWS Account IDs for any Cloudfront Website

DevFeed: [Getting Partial AWS Account IDs for any Cloudfront Website](<https://devfeed.tech/articles/getting-partial-aws-account-ids-for-any-cloudfront-website-41997.md>)

Original publisher: [Read original article](<https://arkadiyt.com/2021/07/09/getting-partial-aws-account-ids-for-any-cloudfront-website/>)

Published: 2021-07-09T07:00:00Z

Content type: article

Language: en

Sources: [Arkadiy Tetelman](<https://devfeed.tech/sources/arkadiy-tetelman.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [AWS Certificate Manager](<https://devfeed.tech/topics/aws-certificate-manager.md>), [bug](<https://devfeed.tech/topics/bug.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [private key](<https://devfeed.tech/topics/private-key.md>), [public key](<https://devfeed.tech/topics/public-key.md>), [domain](<https://devfeed.tech/topics/domain.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [bug](<https://devfeed.tech/tags/bug.md>), [certificates](<https://devfeed.tech/tags/certificates.md>), [domain](<https://devfeed.tech/tags/domain.md>), [private-key](<https://devfeed.tech/tags/private-key.md>), [public-key](<https://devfeed.tech/tags/public-key.md>), [ssl](<https://devfeed.tech/tags/ssl.md>), [tls](<https://devfeed.tech/tags/tls.md>), [website](<https://devfeed.tech/tags/website.md>)

### AI overview

This article explains how a bug in AWS Certificate Manager could bypass CloudFront's TLS-certificate requirement for looking up partial AWS account and distribution IDs associated with a domain. It describes manipulating RSA private-key parameters to match a public certificate.

### Source excerpt

Yesterday Amazon released a new Cloudfront API that returns partial AWS account ids and Cloudfront distribution ids associated with some given domain name, to help you determine which of your own AWS accounts serves traffic for that domain. In Cloudfront, a domain alias can only be associated with a single distribution globally across all AWS accounts, and for companies that have a lot of assets it can be difficult to track down which account owns a given domain - this API helps solve that problem. Of course it would be problematic if we could lookup account ids (even partial ones) for arbitrary websites, so to help protect against this information leakage Amazon requires you to have a valid TLS certificate for the domain name you want to query. This is called out in their documentation: To list conflicting aliases, you provide the alias to search and the ID of a distribution in your account that has an attached SSL/TLS certificate that includes the provided alias. As it turns out it's possible to completely bypass this restriction, because ACM has a bug that lets you import certificates without a valid private key. Most people are aware that RSA consists of a public and private keypair which correspond to each other, with the public key completely derived from the private key. That is - if you give me only a private key, I can easily give you the public key that matches the private one. However what some people find surprising is that even though the public key is derived, the private key contains a full copy of the public key (the N and e parameters, in RSA parlance) in order to save on computation time. So if we want to find the partial AWS account id for some domain, we can fetch the real public certificate for that domain, generate a random private key, and update the precomputed public key parameters on our private key to be the same as the public key on the certificate we want to impersonate. ACM has a bug in that it does not validate the private key truly co

## Deploying EFF's Certbot in AWS Lambda

DevFeed: [Deploying EFF's Certbot in AWS Lambda](<https://devfeed.tech/articles/deploying-eff-s-certbot-in-aws-lambda-41992.md>)

Original publisher: [Read original article](<https://arkadiyt.com/2018/01/26/deploying-effs-certbot-in-aws-lambda/>)

Published: 2018-01-26T08:00:00Z

Content type: tutorial

Language: en

Sources: [Arkadiy Tetelman](<https://devfeed.tech/sources/arkadiy-tetelman.md>)

Topics: [AWS Lambda](<https://devfeed.tech/topics/aws-lambda.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Python](<https://devfeed.tech/topics/python.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [Amazon Route 53](<https://devfeed.tech/topics/amazon-route-53.md>), [AWS Certificate Manager](<https://devfeed.tech/topics/aws-certificate-manager.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [certificates](<https://devfeed.tech/tags/certificates.md>), [configure](<https://devfeed.tech/tags/configure.md>), [dns](<https://devfeed.tech/tags/dns.md>), [ec2](<https://devfeed.tech/tags/ec2.md>), [gcc](<https://devfeed.tech/tags/gcc.md>), [iam](<https://devfeed.tech/tags/iam.md>), [openssl](<https://devfeed.tech/tags/openssl.md>), [python](<https://devfeed.tech/tags/python.md>), [security](<https://devfeed.tech/tags/security.md>), [ssh](<https://devfeed.tech/tags/ssh.md>), [tls](<https://devfeed.tech/tags/tls.md>), [wget](<https://devfeed.tech/tags/wget.md>), [x86-64](<https://devfeed.tech/tags/x86-64.md>)

### AI overview

A tutorial explains how to deploy EFF's Certbot in AWS Lambda to automate TLS certificate renewal. It covers packaging Certbot and its Python dependencies, creating an IAM role, scheduling daily execution, and importing renewed certificates into Amazon Certificate Manager.

### Source excerpt

This post describes the steps needed to deploy Certbot (a well-maintained LetsEncrypt/ACME client) inside AWS Lambda. The setup used below is now powering 100% automated TLS certificate renewals for this website - the lambda runs once a day and if there's less than 30 days remaining on my existing cert it will provision a new one and import it to be served by my CDN. The post is broken down into 3 sections: building a self-contained, deployable zip file that includes certbot and its dependencies (the bulk of the work) creating an IAM role for the lambda function that gives it the necessary permissions to execute creating a CloudWatch timer that triggers the lambda function once a day Building a self-contained certbot zip file Certbot is written in python and supports both python 2 & 3. We're going to use Lambda's python 3.6.1 runtime, and to make sure all our packages and dependencies work in the Lambda environment we'll perform all the installation steps in an environment identical to the Lambda one. Amazon's documentation states: The underlying AWS Lambda execution environment is based on the following: Public Amazon Linux AMI version (AMI name: amzn-ami-hvm-2017.03.1.20170812-x86_64-gp2) which can be accessed here. So we'll need to bring up an EC2 instance like that. Step 1: Launch an EC2 instance with the amzn-ami-hvm-2017.03.1.20170812-x86_64-gp2 AMI. You can use the cheapest instance with all the default settings - it will not require any IAM permissions or security group configuration. Step 2: SSH onto the instance and install python3 (it's not installed by default): # Install python 3.6.1 sudo yum install -y gcc zlib zlib-devel openssl openssl-devel wget https://www.python.org/ftp/python/3.6.1/Python-3.6.1.tgz tar -xzvf Python-3.6.1.tgz cd Python-3.6.1 && ./configure && make sudo make install Step 3: Install virtualenv to isolate all the python dependencies, install certbot, and zip it up: # Install & activate virtualenv sudo /usr/local/bin/pip3 install virt

## Why Websites Should Use HTTPS for Privacy and Security

DevFeed: [Why Websites Should Use HTTPS for Privacy and Security](<https://devfeed.tech/articles/if-your-site-isn-t-using-https-you-are-doing-it-wrong-24967.md>)

Original publisher: [Read original article](<https://codeahoy.com/2017/01/18/if-your-site-isnt-using-https-you-are-doing-it-wrong/>)

Author: umer

Published: 2017-01-18T00:00:00Z

Content type: opinion

Language: en

Sources: [Code Ahoy - Articles](<https://devfeed.tech/sources/code-ahoy-articles.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [HTTP](<https://devfeed.tech/topics/http.md>), [Web](<https://devfeed.tech/topics/web.md>), [AWS Certificate Manager](<https://devfeed.tech/topics/aws-certificate-manager.md>), [Google](<https://devfeed.tech/topics/google.md>), [Firefox](<https://devfeed.tech/topics/firefox.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [Mozilla](<https://devfeed.tech/topics/mozilla.md>)

Tags: [aws-certificate-manager](<https://devfeed.tech/tags/aws-certificate-manager.md>), [certificates](<https://devfeed.tech/tags/certificates.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [firefox](<https://devfeed.tech/tags/firefox.md>), [google](<https://devfeed.tech/tags/google.md>), [http](<https://devfeed.tech/tags/http.md>), [mozilla](<https://devfeed.tech/tags/mozilla.md>), [security](<https://devfeed.tech/tags/security.md>)

### 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

## Improving GitHub's SSL setup

DevFeed: [Improving GitHub's SSL setup](<https://devfeed.tech/articles/improving-github-s-ssl-setup-69908.md>)

Original publisher: [Read original article](<https://github.blog/news-insights/the-library/improving-github-s-ssl-setup/>)

Author: Dirkjan Bussink

Published: 2014-12-24T04:08:36Z

Content type: news

Language: en

Sources: [GitHub Blog](<https://devfeed.tech/sources/github-engineering.md>)

Topics: [AWS Certificate Manager](<https://devfeed.tech/topics/aws-certificate-manager.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [configuration](<https://devfeed.tech/tags/configuration.md>), [github](<https://devfeed.tech/tags/github.md>), [github-api](<https://devfeed.tech/tags/github-api.md>), [news-insights](<https://devfeed.tech/tags/news-insights.md>), [security](<https://devfeed.tech/tags/security.md>), [ssl](<https://devfeed.tech/tags/ssl.md>), [the-library](<https://devfeed.tech/tags/the-library.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

GitHub said it would remove RC4 support from its SSL configuration on github.com and the GitHub API on January 5, 2015, citing cryptographic weaknesses and risks to users' data. The change would prevent Internet Explorer on Windows XP from accessing the site; GitHub recommended upgrading Windows or using Chrome or Firefox, while the Git client would continue to work.

### Source excerpt

To keep GitHub as secure as possible for every user, we will remove RC4 support in our SSL configuration on github.com and in the GitHub API on January 5th 2015....

## Introducing Forward Secrecy and Authenticated Encryption Ciphers

DevFeed: [Introducing Forward Secrecy and Authenticated Encryption Ciphers](<https://devfeed.tech/articles/introducing-forward-secrecy-and-authenticated-encryption-ciphers-70075.md>)

Original publisher: [Read original article](<https://github.blog/news-insights/the-library/introducing-forward-secrecy-and-authenticated-encryption-ciphers/>)

Author: Dirkjan Bussink

Published: 2014-01-01T01:01:11Z

Content type: article

Language: en

Sources: [GitHub Blog](<https://devfeed.tech/sources/github-engineering.md>)

Topics: [AWS Certificate Manager](<https://devfeed.tech/topics/aws-certificate-manager.md>), [Encryption](<https://devfeed.tech/topics/encryption.md>)

Tags: [encryption](<https://devfeed.tech/tags/encryption.md>), [github](<https://devfeed.tech/tags/github.md>), [news-insights](<https://devfeed.tech/tags/news-insights.md>), [ssl](<https://devfeed.tech/tags/ssl.md>), [the-library](<https://devfeed.tech/tags/the-library.md>), [traffic](<https://devfeed.tech/tags/traffic.md>)

### AI overview

GitHub describes updating the SSL setup on systems serving its traffic to support Forward Secrecy and Authenticated Encryption Ciphers. It notes that Chrome supports the ciphers and points readers to the EFF and SSL Labs for more information.

### Source excerpt

As of yesterday we've updated our SSL setup on the systems that serve traffic for GitHub. The changes introduce support for Forward Secrecy and Authenticated Encryption Ciphers. So what is...

## Sidejack Prevention Phase 2: SSL Everywhere

DevFeed: [Sidejack Prevention Phase 2: SSL Everywhere](<https://devfeed.tech/articles/sidejack-prevention-phase-2-ssl-everywhere-70700.md>)

Original publisher: [Read original article](<https://github.blog/news-insights/the-library/sidejack-prevention-phase-2-ssl-everywhere/>)

Author: Risk Olson

Published: 2010-11-04T03:07:28Z

Content type: news

Language: en

Sources: [GitHub Blog](<https://devfeed.tech/sources/github-engineering.md>)

Topics: [SSL](<https://devfeed.tech/topics/ssl.md>), [Security, Privacy and Abuse Prevention](<https://devfeed.tech/topics/security-privacy-and-abuse-prevention.md>), [AWS Certificate Manager](<https://devfeed.tech/topics/aws-certificate-manager.md>)

Tags: [https](<https://devfeed.tech/tags/https.md>), [news-insights](<https://devfeed.tech/tags/news-insights.md>), [security](<https://devfeed.tech/tags/security.md>), [ssl](<https://devfeed.tech/tags/ssl.md>), [the-library](<https://devfeed.tech/tags/the-library.md>)

### AI overview

GitHub describes the second phase of its sidejack prevention work: serving every site request over HTTPS with a secure cookie. Some resources were still served from other sites, causing SSL warnings, and GitHub said it would address those insecure assets next.

### Source excerpt

Last Tuesday, we rolled out a secure cookies for all SSL-protected pages. This meant that all private repositories, user dashboards, all admin settings (even for free users and repositories) were...