Find answers, ask questions, and connect with our
community around the world.

Home Forums AWS AWS Certified Solutions Architect Associate 4. Question Category: CSAA – Design High-Performing Architectures Reply To: 4. Question Category: CSAA – Design High-Performing Architectures

  • Neil-TutorialsDojo

    Member
    March 22, 2024 at 2:04 pm

    Hi Denzil,

    Thank you for posting here.

    To clarify the answer technically, configuring a scheduled scaling policy for the Auto Scaling group means setting up a rule to automatically adjust the number of EC2 instances in the group based on a schedule. In this case, the schedule would be set to launch additional instances before the start of office hours, such as 8:00 AM, to ensure there are enough resources available when users begin accessing the CRM application at 9:00 AM. This helps alleviate the performance degradation experienced during peak usage times.

    Regarding your question about CloudWatch and CloudTrail, these services can indeed monitor the application’s performance and trigger actions based on predefined alarms or events. If performance degradation, such as increased CPU or memory usage, triggers alarms in CloudWatch, it could trigger the scaling policy to add more instances to the Auto Scaling group.

    Regarding the customers and office staff logging in, it is indeed a possible cause of the slowness, which is caused by the high CPU and memory usage.

    For instance termination and cost optimization, in real-world scenarios, it’s common to employ cost optimization strategies. Instances launched for peak hours could be terminated or stopped during off-peak times to save costs. However, this depends on the specific needs and usage patterns of the application. If the performance issues persist beyond the initial hours and require continuous scaling, it might be more cost-effective to keep the instances running.

    If an instance is stopped or terminated, AWS does not necessarily restart the same physical instance. The auto-scaling group maintains the desired capacity and launches new instances as needed, potentially from a different Availability Zone for high availability.

    Lastly, for persistent application data, EBS volumes could be attached that remain even if instances are replaced. This ensures data availability when instances are stopped, terminated, or replaced by auto-scaling activities.

    I hope this helps. If you have any more inquiries, do not hesitate to ask.

    Regards,

    Neil @ Tutorials Dojo