Balamuruganjeevi
commented
3 weeks ago - EC2 Instance Type Changes:
Change: After my analyses based on our current EC2 instance types and their utilization metrics. Consider switching to instance types family from T3 to T3a because both offers same performance the only difference is their processors. While T3 works on Intel and T3a works on AMD and i am not sure our application works flawlessly in AMD need to test and it offers lower cost than T3 type instances and performance is also offered same comopared to Intel, However it depends on our workload it is my consideration.
- If we are not decided to change instance types to t3a family, we can change jasper-server instance type to t3.small as my recommendation.
Impact: Positive impact on resource efficiency by aligning instances with workload demands. However, If its not fulfill our performance and worload and other needs may negatively affect performance. Need to test it if we decided to change type.
Cost-Savings: By using T3a family we can save upto 10% to 20% of cost.
Action Plan: Need to regularly monitor instance metrics. We can Perform certain load testing first to validate performance after instance type changes. And by analysing regularly in Future our needs increases have to change their types again to fulfill the requirements.
Follow-Up: Need to regularly monitor and adjust instance types based on changing workload demands.
- RDS Instance Optimization:
Change: After my analyses based on our current RDS instance types and their utilization metrics. Consider switching to instance types family from T3 to T4g like EC2 also the performance and all are same the only diffreence is their processors while T3 is works under Intel and T4g works under AWS Graviton both offers same performance. And i also nit sure about the performance and can work flawlessly under this processor and It offers lower cost than T3 type instances and performance is also offered same comopared to Intel, However it depends on our workload it is my consideration.
Impact: Positive impact is cost savings where negative impact depends on our workloads we have to implement and check first to know about the right performance.
Cost-Savings: Definitely a cost savings from 10% to 20% on the changes.
Action Plan: Need to regularly Monitor RDS performance metrics after changes happens. Regularly Analyze database workload patterns to determine optimal instance sizes and storage types. And analysing regularly in Future workloads changes have to change their types again also.
Follow-Up: After changing Instance types have to regularly review and adjust RDS instance configurations when needed based on our workload and database performance.
- Reserve Instances for Billing Discounts:
Change: Purchase Reserved Instances (RIs) for EC2 and RDS is a better way to reduce cost. where if we decided to change the instance types as mentioned above and need to again review about the RI instance types to works cost effectively, And we are not decided to change instance types then we can use RI instances as mentioned below
-
And we can purchase Reserved Instances for better cost optimisation for EC2 we can purchase 16 t3.nano RI's which will give better cost savings.
-
We can purchase Reserved instances for RDS as it will reduce the cost more than on demand, we can purchase 7 db.t3.micro RI's to meet requirements of the instances.
Impact: Positive impact on cost savings through discounted pricing.
Cost-Savings: For EC2 it will give 30% to 40% cost savings and for RDS it gives 20% to 30% cost savings compared to On-Demand pricing.
Action Plan: Need to Analyze historical EC2 usage to identify instances suitable for reservations. Utilize AWS Cost Explorer to forecast RI purchases.
Follow-Up: Regularly review RI coverage and adjust reservations based on changing usage patterns.
And however above all are just the recommendations to change the type of the instances, If we need better confirmation we need to implement it and testing it.
himeshr
1t5j0y
Optimize resource utilization (EC2, LBs, Network and RDS) for RWB.
Step 1:
Perform analysis on cost saving as well as rsource utilization optimizations that could be done
Step 2:
Submit recommendations with information on
We'll review the recommendations and provide approval for specific changes
Step 3:
Implement approved changes. Perform any other follow-up activity needed, which was identified during analysis.