puppetlabs-aws icon indicating copy to clipboard operation
puppetlabs-aws copied to clipboard

Puppet module for managing AWS resources to build out infrastructure

Results 95 puppetlabs-aws issues
Sort by recently updated
recently updated
newest added

There are instances where Public records are different than the Private records. Unfortunately the current implementation doesn't know how to handle the situation where there is a public zone and...

Prefetching IAM resources (`iam_group, iam_policy, iam_policy_attachment`) takes long as it loads all details for every resource at prefetch time. This is not necessary and makes prefetch time too long. PR...

Avoid fetching of IAM resource data that require subsequent API call at instances list build time. This speeds up Puppet run for me from 217 to 7 seconds.

We are running into issue when creation of launch configurations using ec2_launchconfiguration fails if there is an existing launch configuration that was created from AWS console (probably also using CLI...

Have noticed the following room for improvement on elastic_ip support - elastic IPs that are associated with a NAT gateway report back as detached (check seems to only be against...

Using the module to try and bring some existing infrastructure under Puppet management and came across two stumbling blocks. 1 - puppet resource cloudfront_distribution only picked up 5 of the...

Every VPC that is created will automatically have a security group created with the GroupName "Default". This GroupName cannot be changed. This module only supports referencing the SecurityGroup you want...

Currently launching a CF stack via the cloudformation_stack type with a transform results in the error: `CreateStack cannot be used with templates containing Transforms.` There is great appeal for us...

enhancement

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 ``` Error: Security groups 'Puppet...

question

I'm working with a team that has multiple aws accounts. It would be cool to not need the AWS_PROFILE environment variable. Instead, something like: ``` ec2_instance { 'foo': profile =>...

feature