With AWS OpsWorks for Chef Automate, you are charged based on the number of nodes connected to your Chef server and the time those nodes are running, and you also pay for the underlying Amazon Elastic Compute Cloud (Amazon EC2) instance running your Chef server. There are no upfront costs or minimum fees.
You pay an hourly rate for each running EC2 instance or on-premises server that is registered with your Chef server as a node. For example, if you use your Chef server to manage 10 EC2 instances for 24 hours, you would be billed for 240 node hours. AWS OpsWorks for Chef Automate charges are not incurred after an EC2 instance or on-premises server that is registered as a Chef node is de-registered, shut down or terminated.
|Number of Node Hours||Pricing|
|First 150 nodes / month||Equal to 112,500 node hours
||$0.0155 per node hour
|Next 250 nodes / month||Equal to 187,500 node hours||$0.0150 per node hour
|Next 500 nodes / month
||Equal to 375,000 node hours||$0.0140 per node hour|
|Next 1,500 nodes / month||Equal to 1,125,000 node hours||$0.0125 per node hour|
|Over 2,400 nodes / month||Equal to 1,800,000 node hours
As part of the AWS Free Tier, you can get started with AWS OpsWorks for Chef Automate for free. For 12 months, you receive 10 free connected nodes per month, which equals 7,500 node hours (750 x 10) for free per month.
You pay for the Amazon EC2 instance used to run your managed Chef server. You only pay for what you use, as you use it. There are no minimum fees and no upfront commitments. AWS OpsWorks for Chef Automate supports three instance types (t2.medium, m4.large, m4.2xlarge) and the hourly rate depends on the instance type you choose. See EC2 pricing to learn more.
You may incur additional charges if your managed Chef server uses other AWS services. For example, you may incur charges from Amazon Elastic Block Store (EBS), Amazon S3 for Chef server backups, and Amazon CloudWatch for log streams.