Amazon Web Services (AWS) dominates cloud computing, commanding 60% of the $2 billion public cloud marketplace. Here we demystify what goes on behind the scenes of AWS usage and show you how you can lower costs and increase availability with Newvem’s KnowYourCloud Analytics.
Click here to see the full inforgraphic
Keywords: infographic, visual.ly, newvem, aws, cloud, ec2, reserved instances, cloud costing, ec2 reserved instances
The pace of adoption of cloud computing is evidence not only of its powerful economic advantages but also how easy it is to get into the cloud. But many companies are finding that using the cloud effectively is not so easy. The classic assumption is that a workload in the cloud is the same workload — it’s just in the cloud. But that isn’t true.
Newvem continuously tracks and identifies your AWS EC2 resource utilization patterns on a per-instance basis, as well as on a per-instance-type basis. We also take into consideration what Reserved Instances you have purchased and the corresponding available reservations. Based on the analysis of this data, we identify how effectively you’ve been using your purchased Reserved Instances.
Newvem’s analysis of your AWS EC2 utilization patterns identifies the sustained usage of EC2 instances per instance-type in an availability zone. Such patterns reflect the baseline of utilization of that instance type in the select availability zone. If the user has Reserved Instances available, Newvem’s analysis take them into consideration, and determine whether the reservation is paying off.
Newvem analytic Indicator refers to a meaningful raw cloud usage metric or a simple calculation of these metrics. Newvem analytic service detects and records these indicators in order to generate full visibility and forecast of your cloud usage. For example number of instances or the projected costs.
Keywords: aws ec2 cloud indicator, cloud usage, aws cloud analytic service, cloud usage visibility, cloud usage forecast, aws instances.
Newvem Analytic service locates regions of interest and meaningful usage patterns and generates insights out of them. Newvem Insights are qualitative indicators or meaningful conclusions resulted of a comprehensive calculation of several indicators.
Newvem insight is a compound of the three following parts:
Keywords: cloud insight, newvem insight, suggest an insight.
Newvem continuously tracks and identifies your AWS EC2 resource utilization patterns on a per-instance basis, as well as on a per-instance-type basis. Based on these, we identify when purchasing Reserved Instances might improve your spending efficiency.
Newvem’s analysis of your AWS EC2 utilization patterns identifies the sustained usage of EC2 instances per instance-type in an availability zone. Such patterns reflect the baseline of utilization of that instance type in the select availability zone: if the user historically maintains a minimal number of instances of a given type, running in a given availability zone, for specific periods of time, in some cases it becomes more spend efficient to purchase a Reserved Instance of that instance-type in that availability zone.
The underlying utilization pattern is the fundamental usage pattern that justifies the purchase of Reserved Instances. Other considerations come into the equation when it comes to determine what type of EC2 Reserved Instances one should purchase for aligning the corresponding spending pattern with the underlying business needs.
Introduction
We have noticed that you have at least one EC2 instance behind an Elastic Load Balancer that is accepting connection from IP addresses on the port to which the ELB is directing traffic.
AWS defines a special Security Group associated with the ELB. Users can configure EC2 instances behind ELBs to receive connections to an IP port only from this special SG, thus assuring that only traffic coming from the respective ELB will reach that port. We recommend you change the security group configuration for those EC2 instances in a way that assure that those EC2 instances only accept traffic to the port targeted by the ELB, coming from this special ELB Security Group.
We would like to offer our community the opportunity to suggest additional cloud insights that you would like to see in your cloud environments. Check out our Insights Channel to learn more about Newvem’s unique insights. We also invite you to Order Your Cloud Insight and take part in developing the next killer insight together with the KnowYourCloud Community.
EBS Volumes are always charged for their provisioned storage, regardless of being attached to an EC2 instance. Therefore, when it comes to volumes that are not attached to an instance, the best practice is to keep only those volumes that will be needed in the future. Keeping volumes you don’t plan to use in the future, or those you just forgot, may contribute to unexpectedly high bills.
Furthermore, those volumes left on the side can become old data, that may be inadvertently misused in the future.
Newvem tracks the usage of your EBS Volumes and identifies those that haven’t been attached to any instance for a significant period. We suggest you consider discarding such volumes if you do not plan to use them.
In order to prevent losing important data, it is essential to back up your EBS Volumes. EBS Snapshots enable the creation of virtual copies of EBS Volumes at a specific point in time. A snapshot comprises data blocks that are incrementally saved to Simple Storage Service (S3), meaning that only the blocks on the device that have changed since your last snapshot are saved. For that reason, EBS Snapshots can be an efficient way to back-up the data in EBS Volumes.
For typical data backup procedures, EBS Snapshots offer an adequate instrument to perform backup of EBS Volumes. When using EBS Snapshots as part of a backup procedure, an important parameter to take into consideration when defining your policy is the frequency of snapshots. Factors like the type of data stored in the EBS volumes, its volatility, the amount of data, and others, are key in determining the frequency in which EBS Snapshots should be created.
