Skip to content

Commit

Permalink
Add 'Conflict' notice to launch_template.vpc_security_group_ids (#12647)
Browse files Browse the repository at this point in the history
Add 'Conflict' notice to launch_template.vpc_security_group_ids

If you supply both `vpc_security_groups_ids` and `network_interfaces.security_groups` you will get back:

```
Error: Error creating AutoScaling Group: InvalidQueryParameter: Invalid launc`h template: When a network interface is provided, the security groups must be a part of it.
        status code: 400, request id: 8821039b-87f1-45ff-8567-74e8b9f21905
```
  • Loading branch information
iamtheworstdev authored Aug 31, 2021
1 parent 572b534 commit d351663
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion website/docs/r/launch_template.html.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,7 @@ The following arguments are supported:
* `ram_disk_id` - The ID of the RAM disk.
* `security_group_names` - A list of security group names to associate with. If you are creating Instances in a VPC, use
`vpc_security_group_ids` instead.
* `vpc_security_group_ids` - A list of security group IDs to associate with.
* `vpc_security_group_ids` - A list of security group IDs to associate with. Conflicts with `network_interfaces.security_groups`
* `tag_specifications` - The tags to apply to the resources during launch. See [Tag Specifications](#tag-specifications) below for more details.
* `tags` - (Optional) A map of tags to assign to the launch template. If configured with a provider [`default_tags` configuration block](/docs/providers/aws/index.html#default_tags-configuration-block) present, tags with matching keys will overwrite those defined at the provider-level.
* `user_data` - The Base64-encoded user data to provide when launching the instance.
Expand Down

0 comments on commit d351663

Please sign in to comment.