terraform-provider-aws: error associating RAM Resource Share

Community Note

  • 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 β€œme too” comments, 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 Version

Terraform v0.11.8

Affected Resource(s)

  • aws_ram_resource_share
  • aws_ram_principal_association
  • aws_ram_resource_association

Terraform Configuration Files

Just use code of the documentation pages and use principal o-/ou-.

resource "aws_ram_resource_share" "tgwshare" {
  name = "test-share1"
  allow_external_principals = false
}

resource "aws_ram_principal_association" "example" {
  principal          = "o-xxxxxxx"


  resource_share_arn = "${aws_ram_resource_share.tgwshare.id}"
}

resource "aws_ram_resource_association" "tgwassoc" {
  resource_arn       = "${aws_ec2_transit_gateway.tgw.arn}"
  resource_share_arn = "${aws_ram_resource_share.tgwshare.id}"
}

resource "aws_ec2_transit_gateway" "tgw" {
  description = "example"
}

Debug Output

  • aws_ram_principal_association.example: 1 error(s) occurred:

  • aws_ram_principal_association.example: Error associating principal with RAM resource share: InvalidParameterException: Principal ID o-XXXXXXXX is malformed. Verify the ID and try again. status code: 400, request id: 80e330c1-35e0-11e9-84b1-c1fca2fb946c

Panic Output

no panic

Expected Behavior

Support o-,ou- synatx.

Actual Behavior

Synatay error while using ou- | o- the notation of the principal fails.

Steps to Reproduce

  1. terraform apply

Important Factoids

References

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 9
  • Comments: 16 (10 by maintainers)

Commits related to this issue

Most upvoted comments