added some resources

Author: cjobermaier

content/well-architected-framework/docs/docs/optimize-systems/lifecycle-management/data-management.mdx

@@ -75,9 +75,13 @@ resource "aws_s3_bucket_lifecycle_configuration" "example" {
 It is important to note that other cloud providers, such as [Google Cloud Platform](https://registry.terraform.io/providers/hashicorp/google/5.0.0/docs/resources/storage_bucket.html#example-usage---life-cycle-settings-for-storage-bucket-objects) and [Microsoft Azure](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/storage_management_policy), offer similar lifecycle management features for their storage services. You can use Terraform to manage lifecycle policies across multiple cloud providers, ensuring consistent data management practices regardless of where your data resides.
 
 HashiCorp resources:
+
 - Search the [Terraform Registry](https://registry.terraform.io/browse/providers) for the [cloud](https://registry.terraform.io/browse/providers?category=public-cloud) or [database](https://registry.terraform.io/browse/providers?category=database) provider you use.
 
+- Learn best practices for writing Terraform with the Terraform [style guide](/terraform/language/style).
+
 External resources:
+
 - Cloud storage: [AWS](https://aws.amazon.com/products/storage/), [GCP](https://cloud.google.com/products/storage), and [Azure](https://azure.microsoft.com/en-us/products/category/storage)
 - [Learn how to set the lifecycle configuration for a Google Cloud Bucket](https://cloud.google.com/storage/docs/samples/storage-create-lifecycle-setting-tf) with Terraform.
 - AWS [Enforce data retention policies](https://docs.aws.amazon.com/wellarchitected/latest/framework/cost_decomissioning_resources_data_retention.html)
@@ -87,5 +91,4 @@ External resources:
 In this section of Lifecycle management, you learned about implementing data management policies, including why you should use lifecycle policies and how to automate policy management with infrastructure as code. Implement data management policies is part of the [Optimize systems](/well-architected-framework/optimize-systems) pillar.
 
 To learn more about infrastructure and resource management, see the following resources:
-- [Track infrastructure](/well-architected-framework/optimize-systems/lifecycle-management/track-infrastructure)
 - [Automate infrastructure provisioning](/well-architected-framework/define-and-automate-processes/process-automation/process-automation-workflow)

content/well-architected-framework/docs/docs/optimize-systems/lifecycle-management/decommission-infrastructure.mdx

@@ -48,6 +48,7 @@ You need to install Graphviz on your system to use the `terraform graph` command
 </Note>
 
 HashiCorp resources:
+
 - [Terraform Graph Command](/terraform/docs/cli/commands/graph)
 
 ## Create backups
@@ -90,30 +91,37 @@ lifecycle {
 }
 ```
 
-Consul can help you gradually remove resources by directing traffic away from services you are decommissioning. You can use Consul's service discovery and health checking features to monitor the status of services and ensure that dependent services are not affected during the decommissioning process.
+[Consul](/consul) can help you gradually remove resources by directing traffic away from services you are decommissioning. You can use Consul's service discovery and health checking features to monitor the status of services and ensure that dependent services are not affected during the decommissioning process.
+
+If you are using orchestration tools like [Nomad](/nomad) or Kubernetes, you can use their built-in capabilities to drain workloads before decommissioning nodes gracefully. Nomad provides node drain functionality through the `nomad node drain` command, which prevents new scheduling new allocations on a node while safely migrating existing jobs to other available nodes. The Kubernetes `kubectl drain` command safely removes pods from nodes while respecting Pod Disruption Budgets, which ensure that a minimum number of application replicas remain available throughout the process. 
 
-If you are using orchestration tools like Nomad or Kubernetes, you can use their built-in capabilities to drain workloads before decommissioning nodes gracefully. Nomad provides node drain functionality through the `nomad node drain` command, which prevents new scheduling new allocations on a node while safely migrating existing jobs to other available nodes. The Kubernetes `kubectl drain` command safely removes pods from nodes while respecting Pod Disruption Budgets, which ensure that a minimum number of application replicas remain available throughout the process. 
+HashiCorp resources:
 
-Review the [Zero-downtime deployments](/well-architected-framework/define-and-automate-processes/deploy/zero-downtime-deployments) documentation for strategies on how to redirect traffic and disable functions gradually.
+- Review the [Zero-downtime deployments](/well-architected-framework/define-and-automate-processes/deploy/zero-downtime-deployments) documentation for strategies on how to redirect traffic and disable functions gradually.
+- Learn how to [manage resource lifecycles with Terraform](/terraform/tutorials/state/resource-lifecycle).
 
 ## Verify health of infrastructure and applications
 
 After the decommissioning process, verify that the remaining infrastructure and applications are functioning correctly. Monitor system performance and user feedback to ensure that there are no negative impacts.
 
 The following are steps that you should do after decommissioning:
+
 - Validate APIs are functioning.
 - Check application performance.
 - Monitor system logs for errors.
 
 HashiCorp resources:
+
 - [Learn to setup monitoring agents](/well-architected-framework/define-and-automate-processes/monitor/setup-monitoring-agents) and [dashboards and alerts](/well-architected-framework/define-and-automate-processes/monitor/dashboards-alerts).
 
 External resources:
+
 - AWS [Implement a decommissioning process](https://docs.aws.amazon.com/wellarchitected/latest/framework/cost_decomissioning_resources_implement_process.html)
 
 ## Next steps
 
 In this section of Lifecycle management, you learned about decommissioning resources, including why you should plan decommissioning and how to safely execute the process. Decommission resources is part of the [Optimize systems](/well-architected-framework/optimize-systems) pillar.
 
 To learn more about infrastructure and resource management, see the following resource:
+
 - [Data management](/well-architected-framework/optimize-systems/lifecycle-management/data-management)