Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support source_dest_check flag within resource aws_launch_configuration #3236

Closed
brandongalbraith opened this issue Sep 15, 2015 · 4 comments

Comments

@brandongalbraith
Copy link
Contributor

Currently, in order to use the source_dest_check flag you're required to use the aws_network_interface resource: #2407

It would be helpful if the source_dest_check flag could be specified along side the associate_public_ip_address flag in the aws_launch_configuration resource.

Example:

resource "aws_launch_configuration" "private-nat" {
  lifecycle { create_before_destroy = true }

  image_id = "${var.image_id}"
  instance_type = "t2.micro"
  associate_public_ip_address = true
  source_dest_check = false
  key_name = "${var.key_name}"
  security_groups = ["${aws_security_group.private-nat.id}"]
}
@brandongalbraith brandongalbraith changed the title Support source_dest_check for resource aws_launch_configuration Support source_dest_check flag within resource aws_launch_configuration Sep 15, 2015
@stack72
Copy link
Contributor

stack72 commented Sep 15, 2015

@brandongalbraith the SDK or CLI don't seem to support this

I am not sure how this would be able to be added to Terraform without it

@brandongalbraith
Copy link
Contributor Author

Thanks @stack72! I'll handle this by baking a script into the AMI to provide for this functionality.

@jangrewe
Copy link

For anybody having the same issue, this might be a solution: https://github.com/rubenv/ec2-disable-source-dest

@ghost
Copy link

ghost commented Apr 14, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants