Skip to content

Conversation

@darend
Copy link
Contributor

@darend darend commented Mar 16, 2018

what

  • Enable encryption at rest.
  • Do not pin to the AWSServiceRoleForApplicationAutoScaling_DynamoDBTable role.

why

max_capacity = "${var.autoscale_max_read_capacity}"
min_capacity = "${var.autoscale_min_read_capacity}"
resource_id = "table/${module.default.id}"
role_arn = "${data.aws_iam_role.autoscale_service.arn}"
Copy link
Member

@aknysh aknysh Mar 16, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@osterman
it was like this before.
you changed it to use AWSServiceRoleForApplicationAutoScaling_DynamoDBTable because of

I had to use that to get idempotent apply

or some other issues?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ya, exactly. Everytime I ran terraform apply there was a change set.

@darend what happens if you run it twice?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was fixed in a newer AWS provider: hashicorp/terraform-provider-aws#3303

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image

@osterman osterman merged commit 059c0c5 into cloudposse:master Mar 16, 2018
@darend darend deleted the role branch March 16, 2018 17:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants