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

aws_launch_configuration invalid or unknown key: user_data_base64 #4565

Closed
digiwhite1980 opened this issue May 17, 2018 · 3 comments
Closed
Labels
question A question about existing functionality; most questions are re-routed to discuss.hashicorp.com. service/ec2 Issues and PRs that pertain to the ec2 service.
Milestone

Comments

@digiwhite1980
Copy link

digiwhite1980 commented May 17, 2018

Hi,

Im trying to use the "user_data_base64" option within the aws_launch_configuration ec2_resources.
I get the following error:

Error: module.kubelet_launch_configuration.aws_launch_configuration.launch_configuration: : invalid or unknown key: user_data_base64

I used an own written terraform module which has the following configuration:

resource "aws_launch_configuration" "launch_configuration" {
name_prefix = "${var.name_prefix}"
image_id = "${var.image_id}"
instance_type = "${var.instance_type}"
spot_price = "${var.spot_price}"
iam_instance_profile = "${var.iam_instance_profile}"

user_data_base64 = "${var.user_data_base64}"
key_name = "${var.key_name}"
security_groups = [ "${var.security_groups}" ]
associate_public_ip_address = "${var.associate_public_ip_address}"
root_block_device {
volume_type = "${var.volume_type}"
volume_size = "${var.volume_size}"
delete_on_termination = "${var.delete_on_termination}"
}

ignore_changes        = [ "user_data_base64" ]
create_before_destroy = true

}
ebs_optimized = "${var.ebs_optimized}"
}

The following terraform version is used (docker.io/hashicorp/terraform:0.11.7):

terraform version
Terraform v0.11.7

  • provider.aws v1.13.0
  • provider.null v1.0.0
  • provider.template v1.0.0
  • provider.tls v1.1.0

Please advise.

Kind regards,

Raymond Otto

@bflad bflad added question A question about existing functionality; most questions are re-routed to discuss.hashicorp.com. service/ec2 Issues and PRs that pertain to the ec2 service. labels May 17, 2018
@bflad bflad added this to the v1.16.0 milestone May 17, 2018
@bflad
Copy link
Contributor

bflad commented May 17, 2018

Hi @digiwhite1980 👋 Sorry you ran into trouble here. This was previously released via #4257 in version 1.16.0 of the AWS provider and has been available in all releases since. You're currently running version 1.13.0. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

@bflad bflad closed this as completed May 17, 2018
@digiwhite1980
Copy link
Author

digiwhite1980 commented May 18, 2018

Hi Brian (@bflad),

Thnx for the update.

@ghost
Copy link

ghost commented Apr 5, 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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question A question about existing functionality; most questions are re-routed to discuss.hashicorp.com. service/ec2 Issues and PRs that pertain to the ec2 service.
Projects
None yet
Development

No branches or pull requests

2 participants