Open pablogmorales opened 6 years ago
You should use the subnet name rather than the subnet id, from your manifests i can see that you are using the subnet id .hope this helps
Did that help?
HI Greg, Sorry, did not get your last notification, maybe went to spam folder, I'll check the configuration and will let you know
Thank you very much for your time and support. Regards
Hello, this is what Im getting now:
ec2_instance { 'instance-from-puppet': ensure => running, region => 'us-east-1', availability_zone => 'us-east-1a', image_id => 'ami-b77a72c8', # you need to select your own AMI instance_type => 't2.micro', key_name => 'keyname', subnet => 'subnet-0589332f', security_groups => ['sg-b9c46ec9'], tags => { tag_name => 'provisioned_by_puppet', }, } change from 'absent' to 'running' failed: When specifying a subnet you must specify a security group associated with a VPC
That security group id is valid, is the one currently associated to an instance, what am I doing wrong?
Thanks
as as side note my subnet name is the same as the subnet id
I got it working now, I have to use the names instead of the ID's name..
Thank you very much!
Hi Do not know if this is a bug or a configuration issue, but it seems it cannot find any security group within my configuration
Thanks Regards