It is very important to ensure that the performance of your acquired AWS services is up to the mark; and if not, make sure you have a comprehensive strategy or solution to put the performance factor in place to improve the same.
Leveraging Centilytics for that matter is a great option where the “Performance Optimizer” feature checks the usage limits of your service(s), ensures your application makes the most out of provisioned throughput and monitors for overutilized instances.
1. High Utilization Amazon EC2 Instances
To ensure you make the most out of your instances, this check examines for Amazon Elastic Compute Cloud (Amazon EC2) instances that were running in the last 14 days and alarms you if the daily CPU utilization exceeds 90% on the 4th day or more. Though steady, high EC2 utilization can indicate improved, stable performance, it can also mean that an application does not have enough resources.
2. Service Limits
This one checks for the service usage and gives alerts if the service limit exceeds 80%. Since the associated values depend on a snapshot, it is possible that your current usage may vary. There might be some cases where your service usage will be greater than the defined limit for a certain timeframe.
3. Large Number of Rules in an EC2 Security Group
Each and every Amazon Elastic Compute Cloud (EC2) security group is checked for an excessive number of rules. On the off chance that a security group has an unnecessary number of rules, performance is likely to be sullied.
4. Large Number of EC2 Security Group Rules Applied to an Instance
The “Performance Optimizer” module of Centilytics has this check that thoroughly examines for Amazon Elastic Compute Cloud (EC2) instances that have several different security group rules. Else, you may have to comprise with degraded performance if an instance has an excessive number of rules.
5. Amazon Route 53 Alias Resource Record Sets
The resource record sets routing DNS queries to respective AWS resources can be reformed to alias resource record sets. This check looks for such resource record sets. An alias resource record set is a unique Amazon Route 53 record type that routes DNS queries to an AWS resource (such as, an ELB load balancer or an S3 bucket) else, they are routed to another Route 53 resource record set.
AWS Cost Saving Tip:
When you utilize alias resource record sets, Route 53 routes your DNS queries to AWS resources for nothing out of pocket.
6. Overutilized Amazon EBS Magnetic Volumes
This check looks for Amazon Elastic Block Store (EBS) Magnetic volumes that have been possibly over-utilized and might profit by a more effective configuration. A magnetic volume is designed for applications with workaday or bursty I/O requirements where the IOPS rate is not failsafe. It delivers around 100 IOPS by and large, with a best-exertion ability to torrent to several IOPS. You can utilize a Provisioned IOPS (SSD) volume for reliably higher IOPS. For bursty IOPS, utilize a General Purpose (SSD) volume.
7. Amazon EBS Provisioned IOPS (SSD) Volume Attachment Configuration
You may have Provisioned IOPS (SSD) volumes attached to an Amazon Elastic Compute Cloud (EC2) instance that is not optimized for Amazon EBS. Centilytics provides a performance check for this where such Provisioned IOPS (SSD) volumes are examined. Provisioned IOPS volumes in the Amazon Elastic Block Store (EBS) are intended to deliver the expected performance when they are attached to an EBS-efficient instance only.
8. Amazon CloudFront Content Delivery Optimization
This check optimizes your performance by examining for the possibilities where data transfer from Amazon Simple Storage Service (Amazon S3) buckets could be accelerated using CloudFront. A high ratio of “data transfer out” to the “data stored in S3 bucket” indicates that CloudFront could be beneficial for you for delivering data.
For a heads-up;
Amazon CloudFront is the global content delivery service AWS provides to speed up the distribution your static as well dynamic content to your users. Once CloudFront is configured for your content delivery, the distribution requests are routed to the nearest AWS edge location where content is cached to accelerate the delivery to your users with the best performance possible.
9. CloudFront Header Forwarding and Cache Hit Ratio
The HTTP request headers that CloudFront receives from the client server at present is checked and is forwarded to the origin server. A few headers, for example, Date or User-Agent, essentially decrease the cache hit ratio (the share of requests that are served from a CloudFront edge store). This increases the load on your origin server and hampers performance on the grounds that CloudFront should forward more requests to your origin.
10. Amazon EC2 to EBS Throughput Optimization
Amazon EBS volumes whose performance are likely to be hampered by the maximum throughput capacity of the Amazon EC2 instance they are attached to, are examined to ensure that the maximum throughput of an EC2 instance remains greater than the total maximum throughput of the attached EBS volumes. This optimizes your EC2 to EBS throughput.
11. CloudFront Alternate Domain Names
Inspects content deliveries of CloudFront to figure out alternate domain names that are configured with incorrect DNS settings. On the off chance that a CloudFront delivery incorporates alternate domain names, the DNS configuration for the respective domains must route DNS queries to that distribution.