Bug: leading whitespace causes aws_iam_policy to incorrectly report valid JSON policies as invalid

[mwinters0]

Terraform Version

0.10.7, 0.9.11

Terraform Configuration Files

resource "aws_iam_policy" "nodes_sqs_policy" {
    name        = "nodes_sqs_policy"
    description = "nodes SQS"
    policy = <<EOF
    {
      "Version": "2012-10-17",
      "Statement": [
        {
          "Effect": "Allow",
          "Action": [
            "sqs:GetQueueAttributes"
          ],
          "Resource": [
            "arn:aws:sqs:us-east-1:123123123:myapp-dev-us-east-1*"
          ]
        }
      ]
    }
EOF
}

Expected Behavior

The policy was applied

Actual Behavior

1 error(s) occurred:

* aws_iam_policy.nodes_sqs_policy: "policy" contains an invalid JSON policy

Important Factoids

Removing the whitespace before the first character in the policy allows it to be applied:

data "template_file" "nodes_iam_sqs" {
    name        = "nodes_sqs_policy"
    description = "nodes SQS"
    policy = <<EOF
{
      "Version": "2012-10-17",
      "Statement": [
        {
          "Effect": "Allow",
          "Action": [
            "sqs:GetQueueAttributes"
          ],
          "Resource": [
            "arn:aws:sqs:us-east-1:123123123:myapp-dev-us-east-1*"
          ]
        }
      ]
    }
EOF
}

According to RFC 4627, "Insignificant whitespace is allowed before or after any of the six structural characters."

References

#11906 is where the JSON validation was applied.

[mwinters0]

Aaand this is in the wrong repo.

[lws-llc]

just ran into this issue, thanks

[woodcockjosh]

lame. Can we please fix? Thanks

[mwinters0]

The AWS provider has moved out of the main terraform repo, and this bug report has moved here: hashicorp/terraform-provider-aws#1873

[JoeyGarcia]

I had the same problem and got it fixed by removing all the spaces before the left curly brace that is immediately after the <<EOF, that curly brace should be on it's own line and position 0.

[ghost]

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.