In my journey through the cloud I often come across great new initiatives. The interesting fact is that although the cloud is a pure revolution terms such as SLA, TCO and ROI remain valid, new methodologies and techniques are presented to support them in the cloud.
Scaling is one of the most important factors for Cloud Services. It allows the user to optimize the cost by providing resources only when required. Amazon Cloud Auto Scaling�?provides horizontal scaling by automatically adding or removing the computer resources for the application hosted on AWS. The changes are on demand based on the triggers configured by the user.
Consider the following scenario: when the user’s web application is hosted on AWS and there is a sudden increase of traffic to that website. If the user fails to scale up based on the need, the application may fail or give a slow response. If the user has configured parameters such that AWS adds more application resources (EC2 Instances) when the traffic increases the application will continue to respond with the same performance as before.
The present guide demonstrates how to install Auto Scaling CLI on a Windows machine.
In part one I described the AWS EBS snapshot mechanism. In this part I will drill deeper on how to calculate the EBS snapshot cost. I �?will show how to be able to do a rough estimation or even to perform�?an accurate cost analysis using monitoring tools.
In order to estimate how large your EBS snapshots will be, you need to know how much your volumes are changing.�?One way would be to guesstimate,we can use a simple thumb rule that is often used in- backup planning: A typical data volume of a production server changes about 3% a day. Let’s try and calculate the cost. Assuming a 1TB EBS volume, that is 70% full at first. We take snapshots and keep them for 30 days. So, the first full will be taking 700GB (70% of 1TB). For the incremental snapshots we can multiply 30 (days) by 30GB (3% of 1TB) and we reach 900GB. Add them together and we reach about 1.6TB of total snapshot storage. AWS compresses the snapshots when they are stored in S3.
AWS CloudFront is a content distribution service offered by AWS to speed up the distribution of static content, such as media files, html, js, css, etc. CloudFront provides the log file option to log the end user access request data, its status and other relevant information. The log file will be stored in the S3 bucket. The log file can be in the same bucket as the distribution origin or it can also be in a separate bucket. The user can configure the same bucket for multiple distributions. The user can specify the prefix to the log file to distinguish the distribution details. The CloudFront stores the data to the log file periodically. Each log record will have the user access details, such as the date, time, the edge location information which served the content, the bytes from the server to the client, the client IP, the protocol (HTTP/s), the query string, and more.
The user account where the CloudFront distribution is located should have full access to the S3 bucket. If the bucket belongs to some other AWS account, provide the access rights.
The present guide demonstrates how to enable logging for the CloudFront download or the streaming distribution.
AWS CloudFront is a content distribution service offered by AWS to speed up the distribution of static content, such as media files, html, js, css, etc. CloudFront serves its content through its ever growing edge locations network. The AWS CloudFront serves its content from the origin server configured during the distribution configuration. For the download distribution, CloudFront supports custom origins similar to a storage device such as an HTTP server. CloudFront supports the AWS services, such as EC2, and ELB as the custom origin. While working with the custom origin, the following is recommended:
The CloudFront streaming distribution does not support the custom origin functionality.
The present guide demonstrates how to create a download distribution for the AWS CloudFront using AWS EC2 as the custom origin.
AWS CloudFront is a content distribution service offered by AWS to speed up the distribution of static content, such as media files, html, js, css, etc. CloudFront can stream media files using the Adobe Real-Time Messaging Protocol (RTMP). It is required that the streams file is on AWS S3 and should not be served from any other origin. The user can stream the file using a JWPlayer, Adobe Flash player or flow player. The user can create a streaming distribution. The end user can view the streamed media file using the player specified by the user.
The AWS allows creating multiple streaming distributions for a single bucket and the user can stream the media objects using any of the valid streaming distributions.
The present guide demonstrates how to list, view or update an existing streaming distribution.
Newvem has partnered with CloudAcademy and is now sponsoring an AWS trivia game
We invite you to stop by and test your AWS knowledge.
We established the Newvem community in order to crowd-source cloud knowledge and support. While trying to understand the level of proficiency of current AWS cloud users, we found many users just getting started while many more have been architecting and developing for the Amazon cloud from the beginning.
The cloud enables great agility and can reduce costs if used right. But does it also manage risk? In fact, the cloud contains the same traditional hosting risks as well as specific related risks to your production environment running on the cloud. With IaaS dynamic environment you pay only for what you use enabling alignment with actual real-time demand. The cloud instance is a temporary resource that is created from a gold master image automatically and on demand. This basic cloud automation capability makes traditional patching redundant and fast provisioning extremely easy. It is an important consideration that changes some basic security deployment perceptions when moving from traditional infrastructure to the cloud.
Cloud computing comes with amazing financial benefits for the organization…assuming it’s done right.�?In this presentation, Adrian Cockcroft of Netflix explains how a rapid innovation cycle encourages�?faster returns and a more economic cloud. He posits that lowering the cost of failure will create a more�?innovative organization and culture – but how?
AWS CloudFront is a content distribution service offered by AWS to serve low latency content with high data speed. CloudFront caches the object to its edge location. The user can configure how long an object can stay in the cache. When creating a CloudFront download distribution, it allows the user to configure the caching behavior for the different path patterns: E.g. one cache behavior is for all .css files while the other is for all .jpg files. When a new distribution is created, CloudFront forwards all requests to the origin specified during the creation of the distribution. The user can add another caching behavior for a different path pattern.
The present guide demonstrates how to configure the cache behavior for a download distribution.
