|
| 1 | +# AWS Pricing |
| 2 | + |
| 3 | +MTO supports AWS pricing model via the `integrationConfig.components.showbackOpts.cloudIntegrationSecretRef` field. Following 3 types of pricing are supported: |
| 4 | + |
| 5 | +- [`AWS Standard Pricing`](#aws-standard-pricing) |
| 6 | +- [`AWS Spot Instance Datafeed`](#aws-spot-instance-pricing) |
| 7 | + |
| 8 | +## AWS Standard Pricing |
| 9 | + |
| 10 | +OpenCost will automatically read the node information `node.spec.providerID` to determine the cloud service provider (CSP) in use. If it detects the CSP is AWS, it will attempt to pull the AWS on-demand pricing from the configured public API URL with no further configuration required. |
| 11 | + |
| 12 | +OpenCost will request pricing data from the `us-east-1` region for your `node_region` using the template: |
| 13 | + |
| 14 | +```url |
| 15 | +https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonEC2/current/${node_region}/index.json |
| 16 | +``` |
| 17 | + |
| 18 | +## AWS Spot Instance Pricing |
| 19 | + |
| 20 | +To enable the AWS Spot Instance pricing, subscribe to AWS Spot Instance Data Feed with the following command |
| 21 | + |
| 22 | +```sh |
| 23 | +aws ec2 create-spot-datafeed-subscription \ |
| 24 | + --bucket <BUCKET_NAME> \ |
| 25 | + [--prefix <BUCKET_PREFIX>] |
| 26 | +``` |
| 27 | + |
| 28 | +- `<BUCKET_NAME>` — Name of the bucket Amazon S3 bucket to store the data feed files |
| 29 | +- `<BUCKET_PREFIX>` — Optional prefix directory in which data feed files will be stored |
| 30 | + |
| 31 | +### Amazon S3 bucket requirements |
| 32 | + |
| 33 | +When you subscribe to the data feed, you must specify an Amazon S3 bucket to store the data feed files. |
| 34 | + |
| 35 | +Before you choose an Amazon S3 bucket for the data feed, consider the following: |
| 36 | + |
| 37 | +- You must have `FULL_CONTROL` permission to the bucket. If you're the bucket owner, you have this permission by default. Otherwise, the bucket owner must grant your AWS account this permission. |
| 38 | + |
| 39 | +- When you subscribe to a data feed, these permissions are used to update the bucket ACL to give the AWS data feed account `FULL_CONTROL` permission. The AWS data feed account writes data feed files to the bucket. If your account doesn't have the required permissions, the data feed files cannot be written to the bucket. For more information, see Logs sent to Amazon S3 in the Amazon CloudWatch Logs User Guide. |
| 40 | + |
| 41 | +- If you update the ACL and remove the permissions for the AWS data feed account, the data feed files cannot be written to the bucket. You must resubscribe to the data feed to receive the data feed files. |
| 42 | + |
| 43 | +- Each data feed file has its own ACL (separate from the ACL for the bucket). The bucket owner has `FULL_CONTROL` permission to the data files. The AWS data feed account has read and write permissions. |
| 44 | + |
| 45 | +- If you delete your data feed subscription, Amazon EC2 doesn't remove the read and write permissions for the AWS data feed account on either the bucket or the data files. You must remove these permissions yourself. |
| 46 | + |
| 47 | +- If you encrypt your Amazon S3 bucket using server-side encryption with an AWS KMS key stored in AWS Key Management Service (SSE-KMS), you must use a customer managed key. For more information, see Amazon S3 bucket server-side encryption in the Amazon CloudWatch Logs User Guide. |
| 48 | + |
| 49 | +### Configure an IAM Policy |
| 50 | + |
| 51 | +- Create a user or role for OpenCost with access to the spot feed bucket. Attach the policy below to the role/user and replace `<BUCKET_NAME>` with your spot bucket name |
| 52 | + |
| 53 | +```json |
| 54 | +{ |
| 55 | + "Version": "2012-10-17", |
| 56 | + "Statement": [ |
| 57 | + { |
| 58 | + "Action": [ |
| 59 | + "s3:ListAllMyBuckets", |
| 60 | + "s3:ListBucket", |
| 61 | + "s3:HeadBucket", |
| 62 | + "s3:HeadObject", |
| 63 | + "s3:List*", |
| 64 | + "s3:Get*" |
| 65 | + ], |
| 66 | + "Resource": [ |
| 67 | + "arn:aws:s3:::<BUCKET_NAME>" |
| 68 | + ], |
| 69 | + "Effect": "Allow", |
| 70 | + "Sid": "SpotDataAccess" |
| 71 | + } |
| 72 | + ] |
| 73 | +} |
| 74 | +``` |
| 75 | + |
| 76 | +### Option 1: Service Keys |
| 77 | + |
| 78 | +Generate Access Keys with following steps |
| 79 | + |
| 80 | +1. Navigate to the AWS IAM Console. |
| 81 | +1. Select Access Management > Users from the left navigation. |
| 82 | +1. Find the OpenCost User and select Security credentials > Create access key. |
| 83 | +1. Follow along to receive the Access Key ID and Secret Access Key (AWS will not provide you the Secret Access Key in the future, so make sure you save this value). |
| 84 | + |
| 85 | +Create a `service-key.json` and replace the values with the user access keys |
| 86 | + |
| 87 | +```json |
| 88 | +{ |
| 89 | + "aws_access_key_id": "<ACCESS_KEY_ID>", |
| 90 | + "aws_secret_access_key": "<SECRET_ACCESS_KEY>" |
| 91 | +} |
| 92 | +``` |
| 93 | + |
| 94 | +Create a Kubernetes secret with the following command |
| 95 | + |
| 96 | +```sh |
| 97 | +kubectl create secret generic <SECRET_NAME> --from-file=service-key.json --namespace multi-tenant-operator |
| 98 | +``` |
| 99 | + |
| 100 | +!!! note |
| 101 | + When managing the service account key as a Kubernetes secret, the secret must reference the service account key JSON file, and that file must be named `service-key.json`. |
| 102 | + |
| 103 | +The data feed will provide specific pricing information about any Spot instances in your account on an hourly basis. After setting this up, the bucket information can be provided through options in the IntegrationConfig via `integrationConfig.components.showbackOpts.custom` object. |
| 104 | + |
| 105 | +- `awsSpotDataBucket` - The name of the S3 bucket Spot Instance Data Feed is publishing to. |
| 106 | +- `awsSpotDataRegion` - The region configured for Spot Instance Data Feed |
| 107 | +- `awsSpotDataPrefix` - The prefix (if any) configured for Spot Instance Data Feed |
| 108 | +- `projectID` - The AWS Account ID |
| 109 | +- `<SECRET_NAME>` - Name of the service key secret created in previous step |
| 110 | + |
| 111 | +Example: |
| 112 | + |
| 113 | +```yaml |
| 114 | +components: |
| 115 | + showback: true # should be enabled |
| 116 | + showbackOpts: |
| 117 | + custom: |
| 118 | + provider: aws |
| 119 | + description: "AWS Provider Configuration. Provides default values used if instance type or spot information is not found." |
| 120 | + CPU: "0.031611" |
| 121 | + spotCPU: "0.006655" |
| 122 | + RAM: "0.004237" |
| 123 | + GPU: "0.95" |
| 124 | + spotRAM: "0.000892" |
| 125 | + storage: "0.000138888889" |
| 126 | + zoneNetworkEgress: "0.01" |
| 127 | + regionNetworkEgress: "0.01" |
| 128 | + internetNetworkEgress: "0.143" |
| 129 | + spotLabel: "kops.k8s.io/instancegroup" |
| 130 | + spotLabelValue: "spotinstance-nodes" |
| 131 | + awsSpotDataRegion: "us-east-2" |
| 132 | + awsSpotDataBucket: "my-spot-bucket" |
| 133 | + awsSpotDataPrefix: "spot_pricing_prefix" |
| 134 | + projectID: "012345678901" |
| 135 | + |
| 136 | + cloudPricingSecretRef: |
| 137 | + name: <SECRET_NAME> |
| 138 | + namespace: multi-tenant-operator |
| 139 | +``` |
| 140 | +
|
| 141 | +### Option 2: IRSA (IAM Roles for Service Accounts) |
| 142 | +
|
| 143 | +After creating the role and policy, attach the role ARN as an annotation to the opencost gateway account via following command |
| 144 | +
|
| 145 | +```sh |
| 146 | +kubectl annotate serviceaccounts -n multi-tenant-operator tenant-operator-opencost-gateway eks.amazonaws.com/role-arn=<ROLE_ARN> |
| 147 | +``` |
| 148 | + |
| 149 | +Apply the IntegrationConfig with current spot bucket data feed information |
| 150 | + |
| 151 | +Example: |
| 152 | + |
| 153 | +```yaml |
| 154 | +components: |
| 155 | + showback: true # should be enabled |
| 156 | + showbackOpts: |
| 157 | + custom: |
| 158 | + provider: aws |
| 159 | + description: "AWS Provider Configuration. Provides default values used if instance type or spot information is not found." |
| 160 | + CPU: "0.031611" |
| 161 | + spotCPU: "0.006655" |
| 162 | + RAM: "0.004237" |
| 163 | + GPU: "0.95" |
| 164 | + spotRAM: "0.000892" |
| 165 | + storage: "0.000138888889" |
| 166 | + zoneNetworkEgress: "0.01" |
| 167 | + regionNetworkEgress: "0.01" |
| 168 | + internetNetworkEgress: "0.143" |
| 169 | + spotLabel: "kops.k8s.io/instancegroup" |
| 170 | + spotLabelValue: "spotinstance-nodes" |
| 171 | + awsSpotDataRegion: "us-east-2" |
| 172 | + awsSpotDataBucket: "my-spot-bucket" |
| 173 | + awsSpotDataPrefix: "spot_pricing_prefix" |
| 174 | + projectID: "012345678901" |
| 175 | +``` |
| 176 | +
|
| 177 | +## References |
| 178 | +
|
| 179 | +For more information, refer to the following resources |
| 180 | +
|
| 181 | +- [`OpenCost documentation`](https://www.opencost.io/docs/configuration/aws) |
| 182 | +- [`Kubecost documentation`](https://docs.kubecost.com/install-and-configure/install/cloud-integration/aws-cloud-integrations) |
| 183 | +- [`Assign IAM roles to Kubernetes service accounts`](https://docs.aws.amazon.com/eks/latest/userguide/associate-service-account-role.html) |
| 184 | +- [`Track your Spot Instance costs using the Spot Instance data feed`](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-data-feeds.html) |
| 185 | +- [`Manage access keys from IAM users`](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html) |
0 commit comments