Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

AWS management seems to hang

I've installed the puppetlabs-aws module and set up a basic ec2_instance manifest:

ec2_instance { 'puppet-prov-test':
  ensure        => present,
  region        => 'us-east-1',
  image_id      => 'ami-8fcee4e5',
  instance_type => 't1.micro',
}

I have the user access and secret key in ~/.aws/credentials in the format

[default]
aws_access_key_id: $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
aws_secret_access_key: $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

When I run puppet apply --noop --verbose nothing seems to happen. My cursor just blinks at me after jumping to the next line after I hit enter.

Did I miss something?

AWS management seems to hang

I've installed the puppetlabs-aws module and set up a basic ec2_instance manifest:

ec2_instance { 'puppet-prov-test':
  ensure        => present,
  region        => 'us-east-1',
  image_id      => 'ami-8fcee4e5',
  instance_type => 't1.micro',
}

I have the user access and secret key in ~/.aws/credentials in the format

[default]
aws_access_key_id: $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
aws_secret_access_key: $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

When I run puppet apply --noop --verbose nothing seems to happen. My cursor just blinks at me after jumping to the next line after I hit enter.

Did I miss something?

EDIT Per rnelson0, I have added the specific manifest and have even realized that I had not assigned appropriate permissions to the user that I have been attempting to execute this as. Now that I've fixed those two issues I am seeing a completion of the run but it still isn't doing anything:

# puppet apply /etc/puppetlabs/code/environments/production/modules/aws_prod/manifests/init.pp 
Notice: Compiled catalog for puppetmaster.cspops.int in environment production in 0.04 seconds
Notice: Applied catalog in 0.24 seconds

Once it completes I look at the AWS console. I do not see the server. I have also executed puppet resource ec2_instance which lists all existing servers but not the one I'm attempting to create.

AWS management seems to hang

I've installed the puppetlabs-aws module and set up a basic ec2_instance manifest:

ec2_instance { 'puppet-prov-test':
  ensure        => present,
  region        => 'us-east-1',
  image_id      => 'ami-8fcee4e5',
  instance_type => 't1.micro',
}

I have the user access and secret key in ~/.aws/credentials in the format

[default]
aws_access_key_id: $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
aws_secret_access_key: $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

When I run puppet apply --noop --verbose nothing seems to happen. My cursor just blinks at me after jumping to the next line after I hit enter.

Did I miss something?

EDIT

Per rnelson0, I have added the specific manifest and have even realized that I had not assigned appropriate permissions to the user that I have been attempting to execute this as. Now that I've fixed those two issues I am seeing a completion of the run but it still isn't doing anything:

# puppet apply /etc/puppetlabs/code/environments/production/modules/aws_prod/manifests/init.pp 
Notice: Compiled catalog for puppetmaster.cspops.int in environment production in 0.04 seconds
Notice: Applied catalog in 0.24 seconds

Once it completes I look at the AWS console. I do not see the server. I have also executed puppet resource ec2_instance which lists all existing servers but not the one I'm attempting to create.