Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/hashicorp/terraform-provider-aws/issues/13097 below:

DynamoDB with Global table v2019.11.21 and PROVISIONED and autscaling generates Table Capacity and/or GSI capacityValidationException · Issue #13097 · hashicorp/terraform-provider-aws · GitHub

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform v0.12.24
provider.aws v2.59.0

• aws_dynamodb_table
• aws_appautoscaling_policy
• aws_appautoscaling_target

resource "aws_dynamodb_table" "table" {
  billing_mode     = "PROVISIONED"
  hash_key         = "PK"
  name             = "test-one"
  read_capacity    = 10
  write_capacity   = 5
  stream_enabled   = true
  stream_view_type = "NEW_AND_OLD_IMAGES"
  attribute {
    name = "PK"
    type = "S"
  }
  replica {
    region_name = "us-west-2"
  }
}

resource "aws_appautoscaling_target" "dynamodb-table_read_target" {
  max_capacity       = 100
  min_capacity       = 50
  resource_id        = "table/${aws_dynamodb_table.table.name}"
  scalable_dimension = "dynamodb:table:ReadCapacityUnits"
  service_namespace  = "dynamodb"
}

resource "aws_appautoscaling_policy" "dynamodb-table_read_policy" {
  name               = "dynamodb-read-capacity-utilization-${aws_appautoscaling_target.dynamodb-table_read_target.resource_id}"
  policy_type        = "TargetTrackingScaling"
  resource_id        = aws_appautoscaling_target.dynamodb-table_read_target.resource_id
  scalable_dimension = aws_appautoscaling_target.dynamodb-table_read_target.scalable_dimension
  service_namespace  = aws_appautoscaling_target.dynamodb-table_read_target.service_namespace

  target_tracking_scaling_policy_configuration {
    predefined_metric_specification {
      predefined_metric_type = "DynamoDBReadCapacityUtilization"
    }
    target_value = 70
  }
}

resource "aws_appautoscaling_target" "dynamodb-table_write_target" {
  max_capacity       = 100
  min_capacity       = 50
  resource_id        = "table/${aws_dynamodb_table.table.name}"
  scalable_dimension = "dynamodb:table:WriteCapacityUnits"
  service_namespace  = "dynamodb"
}

resource "aws_appautoscaling_policy" "dynamodb-table_write_policy" {
  name               = "dynamodb-write-capacity-utilization-${aws_appautoscaling_target.dynamodb-table_write_target.resource_id}"
  policy_type        = "TargetTrackingScaling"
  resource_id        = aws_appautoscaling_target.dynamodb-table_write_target.resource_id
  scalable_dimension = aws_appautoscaling_target.dynamodb-table_write_target.scalable_dimension
  service_namespace  = aws_appautoscaling_target.dynamodb-table_write_target.service_namespace

  target_tracking_scaling_policy_configuration {
    predefined_metric_specification {
      predefined_metric_type = "DynamoDBWriteCapacityUtilization"
    }
    target_value = 70
  }
}

gist

NA

Replica for Gobal tables v2019.11.21 should play nicely with autoscaling:

1. create the table
2. create the autoscaling target and policies
3. apply the replication

Errors out with a message:

error creating DynamoDB Table (test-one) replicas: error creating DynamoDB Table (test-one) replicas: ValidationException: Table write capacity should either be Pay-Per-Request or AutoScaled.

1. terraform apply

NA

• DynamoDB V2019.11.21 #12342 (comment)

glkz, parkeyparker, dbednall, ksaio, onema and 63 morehiren929

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4