Скачать или смотреть Create AWS SSL Certificates in Amazon Certificate Manager with Route53 and update DNS TLS HTTPS S3

SSL stands for Secure Sockets Layer. It’s a security protocol that encrypts the connection between a user's browser and a web server to ensure privacy and data integrity. When you see https:// in a URL, SSL (or its successor, TLS) is protecting the connection.

SSL vs. TLS
TLS, or Transport Layer Security, is the modern, more secure replacement for SSL. Although people often say “SSL,” they’re usually referring to TLS, as SSL has been deprecated for years.

The key difference is that TLS:

Uses stronger encryption algorithms

Fixes many security vulnerabilities found in SSL

Is more efficient and widely adopted today

In practice, websites use TLS certificates, but the term SSL certificate is still commonly used for familiarity.

How AWS Certificate Manager (ACM) Works with Route 53
AWS Certificate Manager (ACM) lets you create or import SSL/TLS certificates and manage them for services like CloudFront, API Gateway, and Elastic Load Balancing.

When used with Route 53, ACM can:

Automatically generate DNS validation records (CNAMEs) for certificate approval

Integrate with Route 53 to create and validate these DNS records automatically, making the whole certificate issuance process seamless

This is particularly helpful for validating ownership of domains you manage in Route 53.

Mapping a Domain Name to AWS Services
You can use Route 53 to map domain names (like www.example.com) to AWS services by creating DNS records (usually A or CNAME records). Here's how it works for the three services:

1. Elastic Beanstalk
Beanstalk creates an environment with an underlying load balancer (ALB).

Route 53 points to this load balancer using an Alias record.

You can assign a custom domain to your Beanstalk environment and request an ACM certificate to secure it with HTTPS.

2. S3 (Static Website Hosting)
For HTTP: Use an Alias A record to point to the S3 static website endpoint.

For HTTPS: Use CloudFront in front of the S3 bucket, request an ACM certificate, and point Route 53 to the CloudFront distribution instead of directly to S3.

3. API Gateway
Create a custom domain name in API Gateway.

Request a certificate via ACM (must be in us-east-1).

Map your API stages to this custom domain.

Then create a Route 53 Alias A record that points to the custom domain endpoint of API Gateway.

In summary:

SSL/TLS secures web traffic; TLS is the current standard.

ACM + Route 53 simplifies SSL certificate validation and domain ownership.

Route 53 ties everything together by routing user requests to services like Beanstalk, S3, or API Gateway using custom domain names and secure connections.