Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS Config Set Retention #24944

Closed
tbo-246 opened this issue May 13, 2020 · 2 comments
Closed

AWS Config Set Retention #24944

tbo-246 opened this issue May 13, 2020 · 2 comments

Comments

@tbo-246
Copy link

tbo-246 commented May 13, 2020

Current Terraform Version

v0.12.24

Use-cases

It is now possible to set the retention policy in days for the AWS Config Service. This is a good way of keeping costs down and there is not currently a way to configure this with Terraform.

Attempted Solutions

I have checked all arguments in the resource config resources and none have a retention period setting. I purposefully set this option in the AWS console hoping for Terraform to detect code drift and give me a clue where the setting might be however the setting was ignored.

Proposal

Introduce an argument in the aws_config_configuration_recorder resource called "retention_period". It might look something like:

resource "aws_config_configuration_recorder" "example" {
  name     = "example"
  role_arn = aws_iam_role.config.arn
  retention_period = 365
  recording_group {
    all_supported = true
    include_global_resource_types = true
  }
}

References

@ghost
Copy link

ghost commented May 13, 2020

This issue has been automatically migrated to hashicorp/terraform-provider-aws#13305 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to hashicorp/terraform-provider-aws#13305.

@ghost ghost closed this as completed May 13, 2020
@ghost
Copy link

ghost commented Jun 13, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Jun 13, 2020
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants