AWS elasticbeanstalk documentation change
Summary
Updated terminology from 'Auto Scaling' to 'Amazon EC2 Auto Scaling' and 'Elastic Load Balancing' to 'ELB' for service name consistency
Security assessment
The changes involve branding updates to use full service names (Amazon EC2 Auto Scaling) and abbreviations (ELB). No security vulnerabilities, mitigations, or new security features are introduced. The SSL/TLS encryption context remains unchanged except for terminology.
Diff
diff --git a/elasticbeanstalk/latest/dg/concepts.concepts.design.md b/elasticbeanstalk/latest/dg/concepts.concepts.design.md index 2a903ad55..7d471408e 100644 --- a//elasticbeanstalk/latest/dg/concepts.concepts.design.md +++ b//elasticbeanstalk/latest/dg/concepts.concepts.design.md @@ -15 +15 @@ When operating in a physical hardware environment, in contrast to a cloud enviro -By migrating to the cloud, you can make your infrastructure align well with demand by leveraging the elasticity of cloud. Elasticity helps to streamline resource acquisition and release. With it, your infrastructure can rapidly scale in and scale out as demand fluctuates. To use it, configure your Auto Scaling settings to scale up or down based on the metrics for the resources in your environment. For example, you can set metrics such as server utilization or network I/O. You can use Auto Scaling for compute capacity to be added automatically whenever usage rises and for it to be removed whenever usage drops. You can publish system metrics (for example, CPU, memory, disk I/O, and network I/O) to Amazon CloudWatch. Then, you can use CloudWatch to configure alarms to trigger Auto Scaling actions or send notifications based on these metrics. For instructions on how to configure Auto Scaling, see [Auto Scaling your Elastic Beanstalk environment instances](./using-features.managing.as.html). +By migrating to the cloud, you can make your infrastructure align well with demand by leveraging the elasticity of cloud. Elasticity helps to streamline resource acquisition and release. With it, your infrastructure can rapidly scale in and scale out as demand fluctuates. To use it, configure your Amazon EC2 Auto Scaling settings to scale up or down based on the metrics for the resources in your environment. For example, you can set metrics such as server utilization or network I/O. You can use Amazon EC2 Auto Scaling for compute capacity to be added automatically whenever usage rises and for it to be removed whenever usage drops. You can publish system metrics (for example, CPU, memory, disk I/O, and network I/O) to Amazon CloudWatch. Then, you can use CloudWatch to configure alarms to trigger Amazon EC2 Auto Scaling actions or send notifications based on these metrics. For instructions on how to configure Amazon EC2 Auto Scaling, see [Amazon EC2 Auto Scaling your Elastic Beanstalk environment instances](./using-features.managing.as.html). @@ -27 +27 @@ If ACM isn't [available in your AWS Region](https://docs.aws.amazon.com/general/ -When you configure an SSL certificate for your environment, data is encrypted between the client and the Elastic Load Balancing load balancer for your environment. By default, encryption is terminated at the load balancer, and traffic between the load balancer and Amazon EC2 instances is unencrypted. +When you configure an SSL certificate for your environment, data is encrypted between the client and the ELB load balancer for your environment. By default, encryption is terminated at the load balancer, and traffic between the load balancer and Amazon EC2 instances is unencrypted. @@ -49 +49 @@ In the unlikely situation that another user or process is already using 900, the -As a rule of thumb, you should be a pessimist when designing architecture for the cloud. Leverage the elasticity that it offers. Always design, implement, and deploy for automated recovery from failure. Use multiple Availability Zones for your Amazon EC2 instances and for Amazon RDS. Availability Zones are conceptually like logical data centers. Use Amazon CloudWatch to get more visibility into the health of your Elastic Beanstalk application and take appropriate actions in case of hardware failure or performance degradation. Configure your Auto Scaling settings to maintain your fleet of Amazon EC2 instances at a fixed size so that unhealthy Amazon EC2 instances are replaced by new ones. If you're using Amazon RDS, then set the retention period for backups, so that Amazon RDS can perform automated backups. +As a rule of thumb, you should be a pessimist when designing architecture for the cloud. Leverage the elasticity that it offers. Always design, implement, and deploy for automated recovery from failure. Use multiple Availability Zones for your Amazon EC2 instances and for Amazon RDS. Availability Zones are conceptually like logical data centers. Use Amazon CloudWatch to get more visibility into the health of your Elastic Beanstalk application and take appropriate actions in case of hardware failure or performance degradation. Configure your Amazon EC2 Auto Scaling settings to maintain your fleet of Amazon EC2 instances at a fixed size so that unhealthy Amazon EC2 instances are replaced by new ones. If you're using Amazon RDS, then set the retention period for backups, so that Amazon RDS can perform automated backups.