hi, what do you suggest as the best of managing the Logstash pipeline configuration, i.e being able to update it and apply it to a running ec2 instance
Also when I do terraform apply I get this error: Error: Error launching source instance: InvalidAMIID.NotFound: The image id '[ami-0e472ba40eb589f49]' does not exist │ status code: 400, request id: fcb2bcfd-25ef-444e-be99-fe93ee52d94a │ │ with module.ec2_instance.aws_instance.this[0], │ on .terraform/modules/ec2_instance/main.tf line 5, in resource "aws_instance" "this": │ 5: resource "aws_instance" "this" { I dont know why I get this error I changed the subnet to my subnet and I copied the ami id. I think there must be something wrong in the Github code.
The error msg complains about the AMI. Were you spinning up your EC2 in the same availability zone and same region? Double check and get a valid AMI that is available on your AWS console. That should fix the issue.
Installing new version of config file /etc/kibana/kibana.yml ... Restarting kibana service... OK Created Kibana keystore in /etc/kibana/kibana.keystore Scanning processes... Scanning linux images... Running kernel seems to be up-to-date. No services need to be restarted. No containers need to be restarted. No user sessions are running outdated binaries. No VM guests are running outdated hypervisor (qemu) binaries on this host.
why didnt you use the user-data to do the installation of elasticsearch and the logstash?
Do you have any such video for On premises ELK cluster using terraform?
You needed to figure out if terraform has a provider to support your "On Premises" env.
hi, what do you suggest as the best of managing the Logstash pipeline configuration, i.e being able to update it and apply it to a running ec2 instance
I am using Terraform + Ansible + Parker.
@@zztalk thank you. Do you a github repo for this?
@@tkhalane I shared the key config files in the description of this video. Check it out to see if you get what you're looking for..
I am finding trouble with getting the ubuntu server to spin up. It says there is something wrong source code that was copied from github.
Also, do you mind sharing the variable part of your code. I want to see if I am missing something.
cat variable.tf
variable "AWS_REGION" {
default = "us-east-2"
}
variable "PATH_TO_PUBLIC_KEY" {
description = "Public key path"
default = "mykey.pub"
}
variable "PATH_TO_PRIVATE_KEY" {
default = "mykey"
}
variable "AWS_ACCESS_KEY" {
type = string
default = "xxxx"
}
variable "AWS_SECRET_KEY" {
type = string
default = "xxxx"
}
variable "INSTANCE_USERNAME" {
default = "ubuntu"
}
@@zztalk Thank you so much!
Can you please share the git repo for the modules?
Installing new version of config fiel
Also when I do terraform apply I get this error:
Error: Error launching source instance: InvalidAMIID.NotFound: The image id '[ami-0e472ba40eb589f49]' does not exist
│ status code: 400, request id: fcb2bcfd-25ef-444e-be99-fe93ee52d94a
│
│ with module.ec2_instance.aws_instance.this[0],
│ on .terraform/modules/ec2_instance/main.tf line 5, in resource "aws_instance" "this":
│ 5: resource "aws_instance" "this" {
I dont know why I get this error I changed the subnet to my subnet and I copied the ami id. I think there must be something wrong in the Github code.
The error msg complains about the AMI. Were you spinning up your EC2 in the same availability zone and same region? Double check and get a valid AMI that is available on your AWS console. That should fix the issue.
Please provide git link
Installing new version of config file /etc/kibana/kibana.yml ...
Restarting kibana service... OK
Created Kibana keystore in /etc/kibana/kibana.keystore
Scanning processes...
Scanning linux images...
Running kernel seems to be up-to-date.
No services need to be restarted.
No containers need to be restarted.
No user sessions are running outdated binaries.
No VM guests are running outdated hypervisor
(qemu) binaries on this host.
not able to install kibana..getting this error.how to solve it