AWS deadline-cloud: Rewrite Deadline Cloud cost management guide with cost breakdowns
Summary
Restructures the cost management page: explains why estimates differ from actual costs, adds a table of connected-service costs, and reorganizes best practices into storage, compute, logging, PrivateLink, service-managed fleet VPC connection, and encryption key cost sections. Includes a note on customer managed KMS keys vs the free AWS owned key.
Security assessment
The change is primarily a cost-management rewrite, but it documents the encryption key options (default AWS owned key vs customer managed KMS key) and their billing implications, which is security-adjacent guidance rather than a fix for a specific vulnerability.
Evidence
You might choose to use a customer managed key to encrypt your data. When you use your own key, you incur charges based on how your key is used. If you use an existing key, the additional use is an incremental cost.
Diff
diff --git a/deadline-cloud/latest/userguide/cost-management.md b/deadline-cloud/latest/userguide/cost-management.md index ea0c11c..683989b 100644 --- a//deadline-cloud/latest/userguide/cost-management.md +++ b//deadline-cloud/latest/userguide/cost-management.md @@ -7 +7 @@ -Cost management best practices +Why estimates differ from actual costsCosts incurred alongside Deadline Cloud @@ -9 +9 @@ Cost management best practices -# Cost management +# Understand estimated and actual costs for Deadline Cloud @@ -11 +11 @@ Cost management best practices -AWS Deadline Cloud provides budgets and the usage explorer to help you control and visualize costs for your jobs. However, Deadline Cloud uses other AWS services, such as Amazon S3. Costs for those services are not reflected in Deadline Cloud budgets or the usage explorer and are charged separately based on usage. Depending on how you configure Deadline Cloud, you may use the following AWS services, as well as others: +AWS Deadline Cloud budgets and the usage explorer estimate costs for your jobs. The estimates don't guarantee the amount that you owe for Deadline Cloud or other AWS services. Your actual bill can differ because of calculation limitations and charges from connected AWS services. @@ -13,8 +13 @@ AWS Deadline Cloud provides budgets and the usage explorer to help you control a -Service | Pricing page ----|--- -Amazon CloudWatch Logs | [Amazon CloudWatch Logs pricing](https://aws.amazon.com/cloudwatch/pricing/) -Amazon Elastic Compute Cloud | [Amazon Elastic Compute Cloud pricing](https://aws.amazon.com/ec2/pricing/) -AWS Key Management Service | [AWS Key Management Service pricing](https://aws.amazon.com/kms/pricing/) -AWS PrivateLink | [AWS PrivateLink pricing](https://aws.amazon.com/privatelink/pricing/) -Amazon Simple Storage Service | [Amazon Simple Storage Service pricing](https://aws.amazon.com/s3/pricing/) -Amazon Virtual Private Cloud | [Amazon Virtual Private Cloud pricing](https://aws.amazon.com/vpc/pricing/) +## Why estimates differ from actual costs @@ -22 +15 @@ Amazon Virtual Private Cloud | [Amazon Virtual Private Cloud pricing](https://aw -## Cost management best practices +The estimates in the usage explorer and budgets might differ from your actual costs for the following reasons: @@ -24 +17,28 @@ Amazon Virtual Private Cloud | [Amazon Virtual Private Cloud pricing](https://aw -Using the following best practices can help you understand and control your costs when using Deadline Cloud and the tradeoffs you can make between cost and efficiency. + * _Customer-owned resources_ – The tools don't calculate the actual cost of resources that you provide from AWS, on-premises infrastructure, or another cloud provider. + + * _Idle workers_ – The estimate doesn't include time when a worker has an `IDLE` status. Idle time can occur when a fleet has a minimum worker count greater than zero or while workers transition between jobs. + + * _Worker start and stop time_ – The estimate doesn't include the time that workers spend starting or transitioning from `IDLE` to `STOPPING` and then to `STOPPED`. + + * _Promotional credits, discounts, and custom pricing agreements_ – The tools don't automatically account for private pricing agreements or other discounts. Use the [Adjust usage explorer and budget estimates with the cost scale factor](./using-usage-explorer.html#cost-scale-factor) to align displayed estimates with your organization's pricing. + + * _Storage and connected services_ – The estimate doesn't include asset storage or charges from connected AWS services. The following table identifies common charges. + + * _Price changes_ – The tools use the most recent publicly available prices, but a delay can occur after a price changes. + + * _Taxes_ – The estimate doesn't include taxes applied to your purchase of the service. + + * _Rounding_ – The tools round pricing and usage data during calculations. + + * _Currency conversion_ – Estimates use U.S. dollars. Exchange-rate changes affect values that you convert to another currency. + + * _Pre-purchased licenses_ – The tools can't account for licenses that you provide. For more information, see [Software licensing for service-managed fleets](./smf-licensing.html). + + + + +## Costs incurred alongside Deadline Cloud + +Using Deadline Cloud creates charges from other AWS services, such as storing job attachments in Amazon S3 and collecting task logs in CloudWatch Logs. These charges aren't reflected in Deadline Cloud budgets or the usage explorer. They appear on your AWS bill as the underlying service, based on your usage of that service. + +To track detailed costs across Deadline Cloud and the other AWS services that you use with it, activate [AWS cost allocation tags](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html). @@ -28 +48 @@ Using the following best practices can help you understand and control your cost -The final cost of using Deadline Cloud depends on the interaction between a number of AWS services, the amount of work that you process, and the AWS Region where you run your jobs. The following best practices are guidelines and may not significantly reduce costs. +The table lists common connected-service costs, but it isn't exhaustive. The final cost of using Deadline Cloud depends on your configuration, the amount of work that you process, and the AWS Region where you run your jobs. The practices in the following sections are guidelines and might not significantly reduce costs. @@ -30 +50 @@ The final cost of using Deadline Cloud depends on the interaction between a numb -### Best practices for CloudWatch Logs +The following table maps each cost to when you incur it and where it appears on your bill. @@ -32 +52,8 @@ The final cost of using Deadline Cloud depends on the interaction between a numb -Deadline Cloud sends worker and task logs to CloudWatch Logs. You are charged to collect, store, and analyze these logs. You can reduce costs by logging only the minimum amount of data required to monitor your tasks. +Cost | When you incur it | Appears on your bill as +---|---|--- +Storage costs | When you submit jobs that upload job attachments, and for as long as assets, job attachments, output, and exported logs stay stored. | [Amazon Simple Storage Service](https://aws.amazon.com/s3/pricing/) +Compute costs | While workers in an EC2-backed customer-managed fleet run on instances that you own. | [Amazon Elastic Compute Cloud](https://aws.amazon.com/ec2/pricing/) +Logging costs | When workers send task and worker logs, and for as long as those logs stay stored. | [Amazon CloudWatch Logs](https://aws.amazon.com/cloudwatch/pricing/) +PrivateLink costs | Per hour, for each PrivateLink interface endpoint or usage-based licensing endpoint, for as long as the endpoint exists—even when it's idle. | [AWS PrivateLink](https://aws.amazon.com/privatelink/pricing/) and [Amazon Virtual Private Cloud](https://aws.amazon.com/vpc/pricing/) +Service-managed fleet VPC connection costs | While resources in your VPC are connected to a service-managed fleet, and for the traffic that flows through the connection. | [VPC Lattice](https://aws.amazon.com/vpc-lattice/pricing/) +Encryption key costs | When you encrypt your farm with a customer managed key, based on how the key is used. The default AWS owned key is free. | [AWS Key Management Service](https://aws.amazon.com/kms/pricing/) @@ -34 +61 @@ Deadline Cloud sends worker and task logs to CloudWatch Logs. You are charged to -When you create a queue or fleet, Deadline Cloud creates a CloudWatch Logs log group with the following names: +### Storage costs @@ -36 +63 @@ When you create a queue or fleet, Deadline Cloud creates a CloudWatch Logs log g - * `/aws/deadline/`<FARM_ID>`/`<FLEET_ID>`` +Deadline Cloud uses Amazon S3 to store assets for processing, job attachments, output, and logs that you export from CloudWatch Logs. You incur storage charges when jobs upload attachments and output, when you export logs, and for as long as the files stay stored. These charges appear on your bill as [Amazon Simple Storage Service](https://aws.amazon.com/s3/pricing/). @@ -38 +65 @@ When you create a queue or fleet, Deadline Cloud creates a CloudWatch Logs log g - * `/aws/deadline/`<FARM_ID>`/`<QUEUE_ID>`` +Job attachments use content-addressable storage. If an unchanged file is already available, Deadline Cloud doesn't upload it again. Content-addressable storage limits repeated uploads and storage growth during iterative workflows. For more information, see [Use job attachments to share files](https://docs.aws.amazon.com/deadline-cloud/latest/developerguide/build-jobs-attachments.html) in the _Deadline Cloud Developer Guide_. @@ -39,0 +67 @@ When you create a queue or fleet, Deadline Cloud creates a CloudWatch Logs log g +To reduce storage costs, reduce the amount of data that you store: @@ -40,0 +69,3 @@ When you create a queue or fleet, Deadline Cloud creates a CloudWatch Logs log g + * Only store assets that are currently in use or that will be used shortly. + + * Use an [S3 Lifecycle configuration](https://docs.aws.amazon.com/AmazonS3/latest/userguide/lifecycle-configuration-examples.html) to automatically delete unused files from an S3 bucket. @@ -43 +73,0 @@ When you create a queue or fleet, Deadline Cloud creates a CloudWatch Logs log g -By default, these logs never expire. You can adjust the retention policy of log groups to remove old logs and help reduce storage costs. You can also export logs to Amazon S3. Amazon S3 storage costs are lower than those for CloudWatch. For more information, see [Exporting log data to Amazon S3](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/S3Export.html). @@ -45 +74,0 @@ By default, these logs never expire. You can adjust the retention policy of log -### Best practices for Amazon EC2 @@ -47 +76 @@ By default, these logs never expire. You can adjust the retention policy of log -You can use Amazon EC2 instances for both service-managed and customer-managed fleets. There are three considerations: +### Compute costs @@ -49 +78,7 @@ You can use Amazon EC2 instances for both service-managed and customer-managed f - * For service-managed fleets, you can choose to have one or more instances available at all times by setting the minimum worker count for the fleet. When you set the minimum worker count above 0, the fleet always has this many workers running. This setting can reduce the amount of time that it takes for Deadline Cloud to start processing jobs, however you are charged for the instance's idle time. +If your customer-managed fleet uses Amazon EC2 instances, those instances appear on your bill as [Amazon Elastic Compute Cloud](https://aws.amazon.com/ec2/pricing/) for as long as they run. If your workers run on premises, in a co-location facility, or with another cloud provider, you are responsible for the costs of operating that infrastructure. Those costs aren't tracked by the Deadline Cloud cost management tools. + +Compute for service-managed fleets is billed at [AWS Deadline Cloud pricing](https://aws.amazon.com/deadline-cloud/pricing/) rates and is tracked by the Deadline Cloud cost management tools. + +To reduce compute costs for service-managed fleets and EC2-backed customer-managed fleets: + + * For service-managed fleets, you can choose to have one or more instances available at all times by setting the minimum worker count for the fleet. When you set the minimum worker count above 0, the fleet always has this many workers running. With this setting, you can reduce the time it takes for Deadline Cloud to start processing jobs. However, AWS charges you for the instance's idle time while it waits for work. @@ -53 +88,4 @@ You can use Amazon EC2 instances for both service-managed and customer-managed f - * For both service-managed and customer-managed fleets, you can specify the Amazon EC2 instance types in your fleets. Using smaller instances costs less per minute, but may take longer to complete a job. Conversely, a larger instance costs more per minute, but can reduce the time to complete a job. Understanding the demands that your jobs place on an instance can help reduce your costs. + * Choose Amazon EC2 instance types that match your workload. Smaller instances cost less per minute, but might take longer to complete a job. Conversely, a larger instance costs more per minute, but can reduce the time to complete a job. Understanding the demands that your jobs place on an instance can help reduce your costs. + + * When possible, use Amazon EC2 Spot capacity. Spot capacity costs less than On-Demand capacity, but it can be interrupted. AWS charges for On-Demand instances by the second, and they are not interrupted. + @@ -55 +92,0 @@ You can use Amazon EC2 instances for both service-managed and customer-managed f - * When possible, choose Amazon EC2 Spot instances for your fleet. Spot instances are available for a reduced price, but may be interrupted by on-demand requests. On-demand instances are charged by the second and are not interrupted. @@ -57,0 +95 @@ You can use Amazon EC2 instances for both service-managed and customer-managed f +For an overview of the controls that cap peak compute, see [Control spending and capacity](./manage-costs.html#cost-concurrency-controls). @@ -58,0 +97 @@ You can use Amazon EC2 instances for both service-managed and customer-managed f +### Logging costs @@ -60 +99 @@ You can use Amazon EC2 instances for both service-managed and customer-managed f -### Best practices for AWS KMS +Deadline Cloud sends worker and task logs to CloudWatch Logs. You incur charges to collect logs while workers run tasks, and to store and analyze those logs afterward. These charges appear on your bill as [Amazon CloudWatch Logs](https://aws.amazon.com/cloudwatch/pricing/). @@ -62 +101 @@ You can use Amazon EC2 instances for both service-managed and customer-managed f -By default, Deadline Cloud encrypts you data with an AWS owned key. You are not charged for this key. +When you create a queue or fleet, Deadline Cloud creates a CloudWatch Logs log group with the following names: @@ -64 +103 @@ By default, Deadline Cloud encrypts you data with an AWS owned key. You are not -You may choose to use a customer managed key to encrypt your data. When you use your own key, you are charged based on how your key is used. If you use an existing key, the additional use is an incremental cost. + * `/aws/deadline/`<FARM_ID>`/`<FLEET_ID>`` @@ -66 +105 @@ You may choose to use a customer managed key to encrypt your data. When you use -### Best practices for AWS PrivateLink + * `/aws/deadline/`<FARM_ID>`/`<QUEUE_ID>`` @@ -68 +106,0 @@ You may choose to use a customer managed key to encrypt your data. When you use -You can use AWS PrivateLink to create a connection between your VPC and Deadline Cloud using an interface endpoint. When you create a connection, you can call all of the Deadline Cloud API actions. You are charged per hour for each endpoint that you create. If you use PrivateLink, you must create at least three endpoints, and depending on your configuration, you may need as many as five. @@ -70 +107,0 @@ You can use AWS PrivateLink to create a connection between your VPC and Deadline -### Best practices for Amazon S3 @@ -72 +108,0 @@ You can use AWS PrivateLink to create a connection between your VPC and Deadline -Deadline Cloud uses Amazon S3 to store assets for processing, job attachments, output, and logs. To reduce the costs associated with Amazon S3, reduce the amount of data that you store. Some suggestions: @@ -74 +110 @@ Deadline Cloud uses Amazon S3 to store assets for processing, job attachments, o - * Only store assets that are currently in use or that will be used shortly. +To reduce logging costs, log only the minimum amount of data required to monitor your tasks. By default, these logs never expire. You can adjust the retention policy of log groups to remove old logs and help reduce storage costs. You can also export logs to Amazon S3. Amazon S3 storage costs are lower than those for CloudWatch. For more information, see [Exporting log data to Amazon S3](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/S3Export.html). @@ -76 +112,18 @@ Deadline Cloud uses Amazon S3 to store assets for processing, job attachments, o - * Use an [S3 Lifecycle configuration](https://docs.aws.amazon.com/AmazonS3/latest/userguide/lifecycle-configuration-examples.html) to automatically delete unused files from an S3 bucket. +### PrivateLink costs + +Two optional Deadline Cloud configurations create VPC endpoints in your account. You incur an hourly charge for each endpoint, for as long as it exists—even when it's idle. These charges appear on your bill as [AWS PrivateLink](https://aws.amazon.com/privatelink/pricing/) and [Amazon Virtual Private Cloud](https://aws.amazon.com/vpc/pricing/). + + * You can use AWS PrivateLink to create a connection between your VPC and Deadline Cloud using an interface endpoint. When you create a connection, you can call all of the Deadline Cloud API actions. AWS charges you per hour for each endpoint that you create. If you use PrivateLink, you must create at least three endpoints. Depending on your configuration, you might need up to five. + + * When you use usage-based licensing for your customer-managed fleet, you create a Deadline Cloud license endpoint, which is a Amazon VPC endpoint created in your account. + + + + +To reduce these costs, remove endpoints when you are not using them. For example, remove license endpoints when you are not using usage-based licenses. + +These endpoints are separate from the VPC resource endpoints that connect a service-managed fleet to your VPC. For those costs, see Service-managed fleet VPC connection costs. + +### Service-managed fleet VPC connection costs + +You can connect resources in your VPC, such as file systems and license servers, to a service-managed fleet with VPC resource endpoints. The connection uses VPC Lattice and a resource gateway that you create in your account. You incur charges while the resource gateway exists and for the traffic that flows through the connection. These charges appear on your bill as [VPC Lattice](https://aws.amazon.com/vpc-lattice/pricing/). Connections between Availability Zones carry no additional charge. @@ -77,0 +131 @@ Deadline Cloud uses Amazon S3 to store assets for processing, job attachments, o +To reduce these costs, remove the resource gateway and resource configuration when you are no longer connecting VPC resources to your fleet. @@ -78,0 +133 @@ Deadline Cloud uses Amazon S3 to store assets for processing, job attachments, o +For more information, see [Connect VPC resources to your SMF with VPC resource endpoints](https://docs.aws.amazon.com/deadline-cloud/latest/developerguide/smf-vpc.html) in the _Deadline Cloud Developer Guide_. @@ -79,0 +135 @@ Deadline Cloud uses Amazon S3 to store assets for processing, job attachments, o +### Encryption key costs @@ -81 +137 @@ Deadline Cloud uses Amazon S3 to store assets for processing, job attachments, o -### Best practices for Amazon VPC +By default, Deadline Cloud encrypts your data with an AWS owned key. You are not charged for this key. @@ -83 +139 @@ Deadline Cloud uses Amazon S3 to store assets for processing, job attachments, o -When you use usage-based licensing for your customer-managed fleet, you create a Deadline Cloud license endpoint, which is a Amazon VPC endpoint created in your account. This endpoint is charged at an hourly rate. To reduce costs, remove the endpoints when you are not using usage-based licenses. +You might choose to use a customer managed key to encrypt your data. When you use your own key, you incur charges based on how your key is used. If you use an existing key, the additional use is an incremental cost. These charges appear on your bill as [AWS Key Management Service](https://aws.amazon.com/kms/pricing/). @@ -91 +147 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Track usage and costs +SMF cost model @@ -93 +149 @@ Track usage and costs -Control costs and concurrency +Security