AWS elasticbeanstalk documentation change
Summary
Fixed typos in 'terminate' and 'listener' words
Security assessment
Minor typo corrections with no security implications. Does not alter security-related content.
Diff
diff --git a/elasticbeanstalk/latest/dg/configuring-https.md b/elasticbeanstalk/latest/dg/configuring-https.md index 8b96228b8..4d616121e 100644 --- a//elasticbeanstalk/latest/dg/configuring-https.md +++ b//elasticbeanstalk/latest/dg/configuring-https.md @@ -15 +15 @@ If you don't own a domain name, you can still use HTTPS with a self-signed certi -A load balancer distributes requests to the EC2 instances running your application. A load balancer also eliminates the need to expose your instances directly to the internet. The simplest way to use HTTPS with an Elastic Beanstalk multi-instance environment is to configure a secure listener for the load balancer. The connection between the client and the load balancer remains secure, so you can configure the load balancer to termiante HTTPS. The back end connections between the load balancer and EC2 instances use HTTP, so no additional configuration of the instances is required. For detailed instructions to configure a secure listenter, see [Configuring HTTPS Termination at the load balancer](./configuring-https-elb.html). +A load balancer distributes requests to the EC2 instances running your application. A load balancer also eliminates the need to expose your instances directly to the internet. The simplest way to use HTTPS with an Elastic Beanstalk multi-instance environment is to configure a secure listener for the load balancer. The connection between the client and the load balancer remains secure, so you can configure the load balancer to terminate HTTPS. The back end connections between the load balancer and EC2 instances use HTTP, so no additional configuration of the instances is required. For detailed instructions to configure a secure listenter, see [Configuring HTTPS Termination at the load balancer](./configuring-https-elb.html).