{"_id":"58e653a72d16b42f00772ced","parentDoc":null,"project":"55faf11ba62ba1170021a9a7","__v":0,"category":{"_id":"55faf8f4d0e22017005b8272","__v":7,"pages":["55fafa11d0e22017005b8276","55fafa21a62ba1170021a9bb","55fafa2f825d5f19001fa3a9","5637b7e140ec300d00338947","5637f27244f1870d009d1acf","564672ffc454ee0d00cbe476","564a046ee2efd717002afd11"],"version":"55faf11ba62ba1170021a9aa","project":"55faf11ba62ba1170021a9a7","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-09-17T17:31:32.786Z","from_sync":false,"order":0,"slug":"get-started","title":"GET STARTED"},"user":"5767bc73bb15f40e00a28777","version":{"_id":"55faf11ba62ba1170021a9aa","project":"55faf11ba62ba1170021a9a7","__v":37,"createdAt":"2015-09-17T16:58:03.490Z","releaseDate":"2015-09-17T16:58:03.490Z","categories":["55faf11ca62ba1170021a9ab","55faf8f4d0e22017005b8272","55faf91aa62ba1170021a9b5","55faf929a8a7770d00c2c0bd","55faf932a8a7770d00c2c0bf","55faf94b17b9d00d00969f47","55faf958d0e22017005b8274","55faf95fa8a7770d00c2c0c0","55faf96917b9d00d00969f48","55faf970a8a7770d00c2c0c1","55faf98c825d5f19001fa3a6","55faf99aa62ba1170021a9b8","55faf99fa62ba1170021a9b9","55faf9aa17b9d00d00969f49","55faf9b6a8a7770d00c2c0c3","55faf9bda62ba1170021a9ba","5604570090ee490d00440551","5637e8b2fbe1c50d008cb078","5649bb624fa1460d00780add","5671974d1b6b730d008b4823","5671979d60c8e70d006c9760","568e8eef70ca1f0d0035808e","56d0a2081ecc471500f1795e","56d4a0adde40c70b00823ea3","56d96b03dd90610b00270849","56fbb83d8f21c817002af880","573c811bee2b3b2200422be1","576bc92afb62dd20001cda85","5771811e27a5c20e00030dcd","5785191af3a10c0e009b75b0","57bdf84d5d48411900cd8dc0","57ff5c5dc135231700aed806","5804caf792398f0f00e77521","58458b4fba4f1c0f009692bb","586d3c287c6b5b2300c05055","58ef66d88646742f009a0216","58f5d52d7891630f00fe4e77"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2017-04-06T14:41:43.262Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":3,"body":"## Overview\n\nCloud infrastructure costs on the CGC are based off of task execution and file storage.\n\nWhen you run a task on the CGC, we use one or more compute instances from the CGC's underlying cloud infrastructure provider to process the data. Also, when you add your own files to the CGC and put them in a project, they are housed in cloud storage. Therefore, there are two types of costs you are billed for per month:\n* Compute costs\n* Storage costs\n\n## About compute costs\n\nCompute costs depend on the cloud infrastructure provider. On CGC, Amazon Web Services (AWS) provides the cloud infrastructure and its [Elastic Compute Cloud (EC2)](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts.html) dedicated instances are used to perform computation tasks. Please note that the compute instance costs are passed along with no extra charge or fee for accessing the cloud services through the CGC.\n\nThe following table shows the compute service and charging unit for AWS:\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Cloud service provider\",\n    \"h-1\": \"Service name\",\n    \"h-2\": \"Charging unit\",\n    \"0-0\": \"Amazon Web Services (AWS US East)\",\n    \"0-1\": \"EC2\",\n    \"0-2\": \"per Hour\"\n  },\n  \"cols\": 3,\n  \"rows\": 1\n}\n[/block]\n## Compute Costs: Amazon Web Services\n\n### Amazon EC2 Dedicated Instances\n\nThe CGC performs computation tasks using Amazon EC2 virtual computing environments, known as instances. There are various types of instances that have different configurations of CPU, memory, storage and networking capacity. See the list of [available Amazon Web Services US East instances](doc:list-of-available-amazon-web-services-instances) which are used to run tasks on the CGC.\n\nAn important difference between compute instances is their price. AWS charges for the use of their compute instances on a per hour basis. The hourly rate depends on the instance type used and is shown in the following [price list](https://aws.amazon.com/ec2/purchasing-options/dedicated-instances/) (select **US East (N. Virginia)** from the **Region** dropdown menu).\n\nAll public workflows on the CGC are set up to use instances that offer the optimal ratio of price and compute power, while you are also able to [perform optimization](doc:set-computation-instances) for your applications that you want to use on the CGC.\n\n## Storage Costs\n\nStorage is billed for all files that belong to your projects. This includes the files you upload to the CGC and files that are produced as results of analyses. As AWS is the cloud infrastructure provider for CGC, the storage service is [Amazon Simple Storage Service (Amazon S3)](https://aws.amazon.com/s3/).\n\n<a name=\"storagetable\"></a>\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Cloud service provider\",\n    \"h-1\": \"Service name\",\n    \"h-2\": \"Charging unit\",\n    \"0-0\": \"Amazon Web Services\\n(AWS US East)\",\n    \"0-1\": \"Amazon Simple Storage Service (S3)\",\n    \"0-2\": \"per GB-Month\"\n  },\n  \"cols\": 3,\n  \"rows\": 1\n}\n[/block]\nPlease keep in mind that file storage is not charged twice for the same file. If a file is present in more than one of your projects that belong to one billing group, storage will be charged only once. When we calculate your monthly storage cost, we collect all files across all projects belonging to a single billing group, and then bill only once for each individual file within that billing group. A file is billed once regardless of which project it was uploaded to or how many times it was copied across any number of projects.\n\nHowever, note the following scenarios in which we actually do bill for multiple appearances of a single file:\n\n* **When a file is copied to a project belonging to a different billing group**: in this scenario, both billing groups are treated as \"owning\" a file, and both will pay for one copy. Again, each billing group may have multiple copies of that file in any number of projects, and will only pay once.\n* **When a file is re-uploaded**: we do not detect for content equality, so if you upload the same file twice, the CGC sees (and bills for) two different files.\n* **When a file is archived and restored**: restoring a file is considered as creating a temporary copy that can be worked on. While a file is restored, we bill both for keeping the archived copy and the one in active storage that can be used as input.\n\nYou are not charged for storing public files from our [Public reference files repository](doc:file-repositories-on-the-cgc) or from our [public datasets](doc:about-datasets) when you copy them into your project. However, you are responsible for the costs of any files derived from processing these public files. For instance, if you remap reads, you are charged for the storage of the resulting BAM files.\n\n## Sample storage cost calculation\n[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"Please note that the calculation is for information purposes only and is made according to the prices at the time of writing this page. To find out the current prices, visit the [Amazon S3 pricing page](https://aws.amazon.com/s3/pricing/). Make sure to select **US East (N. Virginia)** from the **Region** dropdown menu.\"\n}\n[/block]\nAs shown in the table [above](#storagetable), storage is charged on a per GB per month basis. This example shows how the total number of GB per month is calculated, given that the amount of data stored is likely to vary during one month.\n\nAssume you store 100 GB (107,374,182,400 bytes) of data for 15 days in March, and 100 TB (109,951,162,777,600 bytes) of data for the final 16 days in March.\n\nAt the end of March, you would have the following usage in Byte-Hours: Total Byte-Hour usage= [107,374,182,400 bytes x 15 days x 24 hours per day] + [109,951,162,777,600 bytes x 16 days x 24 hours per day] = 42,259,901,212,262,400 Byte-Hours.\n\nLet’s convert this to GB-Months: 42,259,901,212,262,400 Byte-Hours / 1,073,741,824 bytes per GB / 744 hours per month = 52,900 GB-Months\n\nBased on the calculated number of GB-Months, we will do cost calculation for Amazon S3.\n\n## Sample Calculation: Amazon Web Services (Amazon S3)\n\nAmazon S3 storage has three pricing tiers depending on the amount of data stored. This is a calculation of the monthly cost based on the amount of GB-Months calculated above:\n\n* **First 50 TB per month**: 51,200 GB (50 x 1024) x $0.023 = $1,177.60\n* **Next 450 TB per month**: 1,700 GB (remainder) x $0.022 = $37.40\n* **Over 500 TB per month**: 0 GB = $0.00\n\n**Total Storage Cost** = $1,177.60 + $37.40 + $0.00 = **$1,215.00**","excerpt":"","slug":"about-pricing","type":"basic","title":"Cloud infrastructure pricing"}

Cloud infrastructure pricing


## Overview Cloud infrastructure costs on the CGC are based off of task execution and file storage. When you run a task on the CGC, we use one or more compute instances from the CGC's underlying cloud infrastructure provider to process the data. Also, when you add your own files to the CGC and put them in a project, they are housed in cloud storage. Therefore, there are two types of costs you are billed for per month: * Compute costs * Storage costs ## About compute costs Compute costs depend on the cloud infrastructure provider. On CGC, Amazon Web Services (AWS) provides the cloud infrastructure and its [Elastic Compute Cloud (EC2)](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts.html) dedicated instances are used to perform computation tasks. Please note that the compute instance costs are passed along with no extra charge or fee for accessing the cloud services through the CGC. The following table shows the compute service and charging unit for AWS: [block:parameters] { "data": { "h-0": "Cloud service provider", "h-1": "Service name", "h-2": "Charging unit", "0-0": "Amazon Web Services (AWS US East)", "0-1": "EC2", "0-2": "per Hour" }, "cols": 3, "rows": 1 } [/block] ## Compute Costs: Amazon Web Services ### Amazon EC2 Dedicated Instances The CGC performs computation tasks using Amazon EC2 virtual computing environments, known as instances. There are various types of instances that have different configurations of CPU, memory, storage and networking capacity. See the list of [available Amazon Web Services US East instances](doc:list-of-available-amazon-web-services-instances) which are used to run tasks on the CGC. An important difference between compute instances is their price. AWS charges for the use of their compute instances on a per hour basis. The hourly rate depends on the instance type used and is shown in the following [price list](https://aws.amazon.com/ec2/purchasing-options/dedicated-instances/) (select **US East (N. Virginia)** from the **Region** dropdown menu). All public workflows on the CGC are set up to use instances that offer the optimal ratio of price and compute power, while you are also able to [perform optimization](doc:set-computation-instances) for your applications that you want to use on the CGC. ## Storage Costs Storage is billed for all files that belong to your projects. This includes the files you upload to the CGC and files that are produced as results of analyses. As AWS is the cloud infrastructure provider for CGC, the storage service is [Amazon Simple Storage Service (Amazon S3)](https://aws.amazon.com/s3/). <a name="storagetable"></a> [block:parameters] { "data": { "h-0": "Cloud service provider", "h-1": "Service name", "h-2": "Charging unit", "0-0": "Amazon Web Services\n(AWS US East)", "0-1": "Amazon Simple Storage Service (S3)", "0-2": "per GB-Month" }, "cols": 3, "rows": 1 } [/block] Please keep in mind that file storage is not charged twice for the same file. If a file is present in more than one of your projects that belong to one billing group, storage will be charged only once. When we calculate your monthly storage cost, we collect all files across all projects belonging to a single billing group, and then bill only once for each individual file within that billing group. A file is billed once regardless of which project it was uploaded to or how many times it was copied across any number of projects. However, note the following scenarios in which we actually do bill for multiple appearances of a single file: * **When a file is copied to a project belonging to a different billing group**: in this scenario, both billing groups are treated as "owning" a file, and both will pay for one copy. Again, each billing group may have multiple copies of that file in any number of projects, and will only pay once. * **When a file is re-uploaded**: we do not detect for content equality, so if you upload the same file twice, the CGC sees (and bills for) two different files. * **When a file is archived and restored**: restoring a file is considered as creating a temporary copy that can be worked on. While a file is restored, we bill both for keeping the archived copy and the one in active storage that can be used as input. You are not charged for storing public files from our [Public reference files repository](doc:file-repositories-on-the-cgc) or from our [public datasets](doc:about-datasets) when you copy them into your project. However, you are responsible for the costs of any files derived from processing these public files. For instance, if you remap reads, you are charged for the storage of the resulting BAM files. ## Sample storage cost calculation [block:callout] { "type": "info", "body": "Please note that the calculation is for information purposes only and is made according to the prices at the time of writing this page. To find out the current prices, visit the [Amazon S3 pricing page](https://aws.amazon.com/s3/pricing/). Make sure to select **US East (N. Virginia)** from the **Region** dropdown menu." } [/block] As shown in the table [above](#storagetable), storage is charged on a per GB per month basis. This example shows how the total number of GB per month is calculated, given that the amount of data stored is likely to vary during one month. Assume you store 100 GB (107,374,182,400 bytes) of data for 15 days in March, and 100 TB (109,951,162,777,600 bytes) of data for the final 16 days in March. At the end of March, you would have the following usage in Byte-Hours: Total Byte-Hour usage= [107,374,182,400 bytes x 15 days x 24 hours per day] + [109,951,162,777,600 bytes x 16 days x 24 hours per day] = 42,259,901,212,262,400 Byte-Hours. Let’s convert this to GB-Months: 42,259,901,212,262,400 Byte-Hours / 1,073,741,824 bytes per GB / 744 hours per month = 52,900 GB-Months Based on the calculated number of GB-Months, we will do cost calculation for Amazon S3. ## Sample Calculation: Amazon Web Services (Amazon S3) Amazon S3 storage has three pricing tiers depending on the amount of data stored. This is a calculation of the monthly cost based on the amount of GB-Months calculated above: * **First 50 TB per month**: 51,200 GB (50 x 1024) x $0.023 = $1,177.60 * **Next 450 TB per month**: 1,700 GB (remainder) x $0.022 = $37.40 * **Over 500 TB per month**: 0 GB = $0.00 **Total Storage Cost** = $1,177.60 + $37.40 + $0.00 = **$1,215.00**