puppetlabs-toy-chest / puppetlabs-aws

Puppet module for managing AWS resources to build out infrastructure
Apache License 2.0
188 stars 219 forks source link

Error: Could not run: Puppet detected a problem with the information returned from AWS #227

Open anishnath opened 8 years ago

anishnath commented 8 years ago

[root@puppet XYZ]# puppet resource cloudwatch_alarm -y Error: Could not run: Puppet detected a problem with the information returned from AWS when looking up cloudwatch_alarm in us-east-1. The specific error was:

Malformed policy ARN. Given: arn:aws:sns:us-east-1:754261010230:testuser

Rather than report on cloudwatch_alarm resources in an inconsistent state we have exited. This could be because some other process is modifying AWS at the same time.

All other resources are working properly expect the cloud_watch

bengler9 commented 8 years ago

I'm getting the same error message. It looks like the cloudwatch_alarm resource currently does not support the Notification Action.

anishnath commented 8 years ago

AWS module is great we need support for the following tooSSL Configuration on the loadbalancer Changing the Instance Type Enable Disable Source/Dst CheckCloud Watch    

 On Thursday, 5 November 2015 1:10 AM, Brian Engler <notifications@github.com> wrote:

I'm getting the same error message. It looks like the cloudwatch_alarm resource currently does not support the Notification Action. — Reply to this email directly or view it on GitHub.

agarstang commented 8 years ago

Reproduced this on Puppet 4.3.2. Using IAM Role to assign permissions to Puppetmaster, no combination of polices allowed me to list 'cloudwatch_alarm' resources.

~# puppet resource cloudwatch_alarm --debug --verbose
Debug: Runtime environment: puppet_version=4.3.2, ruby_version=2.1.8, run_mode=user, default_encoding=UTF-8
Debug: Evicting cache entry for environment 'production'
Debug: Caching environment 'production' (ttl = 0 sec)
Error: Could not run: Puppet detected a problem with the information returned from AWS
when looking up cloudwatch_alarm in eu-west-1. The specific error was:

Malformed policy ARN. Given: arn:aws:sns:eu-west-1:xxxxxxxxxxxx:dynamodb

Rather than report on cloudwatch_alarm resources in an inconsistent state we have exited.
This could be because some other process is modifying AWS at the same time.
ahenroid commented 7 years ago

@anishnath @benglersc @agarstang, are you still seeing this with a recent version of the AWS module? I couldn't reproduce this error. But I can take a closer look if this is still an issue.

taibi-ibtissam commented 7 years ago

I am getting the same Error, And using the latest version of the aws module. I have specified the alarm in my hiera in this way:

itaws::cloudwatch_alarm: cpuutilizationtest: metric: CPUUtilization namespace: 'AWS/EC2' statistic: Average period: 15 dimensions:

  • InstanceId: 'myinstanceid' evaluation_periods: 3 threshold: 80 comparison_operator: '>=' region: 'eu-west-1' And I get

Error: Could not run: Puppet detected a problem with the information returned from AWS when looking up cloudwatch_alarm in eu-west-1. The specific error was:

Malformed policy ARN. Given: arn:aws:sns:eu-west-1:3683598xxxx:xxxxxxx

Rather than report on cloudwatch_alarm resources in an inconsistent state we have exited. This could be because some other process is modifying AWS at the same time.