Update key-rotation.md for up-to-date accuracy (#1163)

Author: thomasvn

install-and-configure/advanced-configuration/key-rotation.md

@@ -1,23 +1,14 @@
 # Service Key Rotation
 
-Cloud provider service keys can be used in various aspects of the Kubecost installation. This includes configuring [integrating your cloud provider billing data with Kubecost](/install-and-configure/install/cloud-integration/README.md), [setting up multi-cluster environments](/install-and-configure/install/multi-cluster/multi-cluster.md), and [backing up data](/install-and-configure/install/multi-cluster/federated-etl/federated-etl-backups-alerting.md). While automated IAM authentication via a Kubernetes service account like AWS IRSA is recommended, there are some scenarios where key-based authentication is preferred. When this method is used, rotating the keys at a pre-defined interval is a security best practice. Combinations of these features can be used, and therefore you may need to follow one or more of the below steps.
+Cloud provider service keys can be used in various aspects of the Kubecost installation. This includes [integrating your cloud provider billing data with Kubecost](/install-and-configure/install/cloud-integration/README.md), [setting up multi-cluster environments](/install-and-configure/install/multi-cluster/multi-cluster.md), and [backing up data](/install-and-configure/install/multi-cluster/federated-etl/federated-etl-backups-alerting.md). While automated IAM authentication via a Kubernetes service account like AWS IRSA is recommended, there are some scenarios where key-based authentication is preferred. When this method is used, rotating the keys at a pre-defined interval is a security best practice. Combinations of these features can be used, and therefore you may need to follow one or more of the below steps.
 
-## Adding cloud provider keys
+## Cloud billing integration keys
 
-There are multiple methods for adding cloud provider keys to Kubecost when configuring a cloud integration. This article will cover all three procedures. Be sure to use the same method that was used during the initial installation of Kubecost when rotating keys.
-See the [Cloud Integrations](/install-and-configure/install/cloud-integration/README.md) doc for additional details.
+1. Update the Kubernetes secret containing the `cloud-integration.json` with the newly rotated key. See [Cloud Integrations](/install-and-configure/install/cloud-integration/README.md) for more configuration details.
+2. Restart the `cloud-cost` pod if it exists, otherwise restart the `cost-analyzer` pod.
+3. Verify the new key is working correctly. Any authentication errors should be present early in the container logs. Additionally, you can check the status of the cloud integration in the Kubecost UI via _Settings_ > _View Full Diagnostics_.
 
-1. The preferred and most common is via the multi-cloud _cloud-integration.json_ Kubernetes secret.
-2. The second method is to define the appropriate secret in Kubecost's [_values.yaml_](https://github.com/kubecost/cost-analyzer-helm-chart/blob/develop/cost-analyzer/values.yaml).
-3. The final method to configure keys is via the Kubecost Settings page. 
-
-The primary sequence for setting up your key is:
-
-1. Modify the appropriate Kubernetes secret, Helm value, or update via the Settings page.
-2. Restart the Kubecost `cost-analyzer` pod.
-3. Verify the new key is working correctly. Any authentication errors should be present early in the `cost-model` container logs from the `cost-analyzer` pod. Additionally, you can check the status of the cloud integration in the Kubecost UI via _Settings_ > _View Full Diagnostics_.
-
-## Adding multi-cluster keys
+## Multi-cluster keys
 
 There are two methods for enabling multi-clustering in Kubecost:
 
@@ -32,8 +23,8 @@ With Federated ETL objects, storage keys can be provided in two ways. The prefer
 
 1. Update the appropriate Kubernetes secret with the new key on each cluster.
 2. Restart the Kubecost `cost-analyzer` pod.
-3. Restart the Kubecost `federator` pod.
-4. Verify the new key is working correctly by checking the `cost-model` container logs from the `cost-analyzer` pod for any object storage authentication errors. Additionally, verify there are no object storage errors in the `federator` pod logs.
+3. If it exists, restart the `aggregator` pod.
+4. Verify the new key is working correctly by checking the container logs for any object storage authentication errors.
 
 ### Thanos