fix: add provider to guardduty features (#195)

* fix:add provider to guardduty features

* fix:change order following styleguide

guardduty.tf

@@ -25,18 +25,24 @@ resource "aws_guardduty_detector" "audit" {
 }
 
 resource "aws_guardduty_organization_configuration_feature" "ebs_malware_protection" {
+  provider = aws.audit
+
   detector_id = aws_guardduty_detector.audit.id
   name        = "EBS_MALWARE_PROTECTION"
   auto_enable = var.aws_guardduty.ebs_malware_protection_status == true ? "ALL" : "NONE"
 }
 
 resource "aws_guardduty_organization_configuration_feature" "eks_audit_logs" {
+  provider = aws.audit
+
   detector_id = aws_guardduty_detector.audit.id
   name        = "EKS_AUDIT_LOGS"
   auto_enable = var.aws_guardduty.eks_audit_logs_status == true ? "ALL" : "NONE"
 }
 
 resource "aws_guardduty_organization_configuration_feature" "eks_runtime_monitoring" {
+  provider = aws.audit
+
   detector_id = aws_guardduty_detector.audit.id
   name        = "EKS_RUNTIME_MONITORING"
   auto_enable = var.aws_guardduty.eks_runtime_monitoring_status == true ? "ALL" : "NONE"
@@ -49,18 +55,24 @@ resource "aws_guardduty_organization_configuration_feature" "eks_runtime_monitor
 }
 
 resource "aws_guardduty_organization_configuration_feature" "lambda_network_logs" {
+  provider = aws.audit
+
   detector_id = aws_guardduty_detector.audit.id
   name        = "LAMBDA_NETWORK_LOGS"
   auto_enable = var.aws_guardduty.lambda_network_logs_status == true ? "ALL" : "NONE"
 }
 
 resource "aws_guardduty_organization_configuration_feature" "rds_login_events" {
+  provider = aws.audit
+
   detector_id = aws_guardduty_detector.audit.id
   name        = "RDS_LOGIN_EVENTS"
   auto_enable = var.aws_guardduty.rds_login_events_status == true ? "ALL" : "NONE"
 }
 
 resource "aws_guardduty_organization_configuration_feature" "s3_data_events" {
+  provider = aws.audit
+
   detector_id = aws_guardduty_detector.audit.id
   name        = "S3_DATA_EVENTS"
   auto_enable = var.aws_guardduty.s3_data_events_status == true ? "ALL" : "NONE"