Auto Scaling group availability zone should match Elastic Load Balancer availability zone

Provider: AwsService: AutoScalingSeverity: Medium

Description

This rule detects when an Auto Scaling group is in a different availability zone than an associated Elastic Load Balancer (ELB). To ensure low network latency, keep Auto Scaling groups and their ELBs in the same zone.

Suggested Action

Ensure Auto Scaling Group is in same availability zone as ELB.

Remediation Steps

  1. Open the Amazon EC2 console.
  2. From the sidebar, navigate to Load Balancing > Load Balancers.
  3. Choose your load balancer.
  4. Do one of the following:
    • Classic Load Balancer in EC2-Classic - On the Instances tab, choose Edit Availability Zones. On the Add and Remove Availability Zones page, choose the Availability Zone to add.
    • Classic Load Balancer in a VPC - On the Instances tab, choose Edit Availability Zones. On the Add and Remove Subnets page, for Available subnets, choose the add icon (+) for the subnet to add. The subnet is moved under Selected subnets.
    • Application Load Balancer - On the Description tab, for Availability Zones, choose Edit. Choose the add icon (+) for one of the subnets for the Availability Zone to add. The subnet is moved under Selected subnets.
  5. Choose Save.

Compliance Controls

FrameworkControl #Control description
EU GDPRArticle-321. Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, the controller and the processor shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate: (a) the pseudonymisation and encryption of personal data; (b) the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services; (c) the ability to restore the availability and access to personal data in a timely manner in the event of a physical or technical incident; (d) a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing. 2. In assessing the appropriate level of security account shall be taken in particular of the risks that are presented by processing, in particular from accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to personal data transmitted, stored or otherwise processed. 3. Adherence to an approved code of conduct as referred to in Article 40 or an approved certification mechanism as referred to in Article 42 may be used as an element by which to demonstrate compliance with the requirements set out in paragraph 1 of this Article. 4. The controller and processor shall take steps to ensure that any natural person acting under the authority of the controller or the processor who has access to personal data does not process them except on instructions from the controller, unless he or she is required to do so by Union or Member State law.

References

Review this link for more information about the topic.