terraform-aws-key-pair

what

In this PR, we can use the AWS SSM Parameter store resource to facilitate the secure management of private key information. This resource allows us to gather the private key information generated by the current module and securely store it in the parameter store.

why

The objective behind this enhancement is to ensure the secure distribution of private key ownership within the AWS infrastructure. We can centrally manage and protect sensitive information, increasing operational efficiency and reducing the likelihood of unauthorized access to critical resources.

references

No issue relates to current improvement.
I have run these required commands,
make init
make readme

Kindly review this PR for module improvements. Thank you

what

Support AWS Provider V5
Linter fixes

why

Maintenance

references

https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.0.0

Rebuild github dir from the template

what and why

Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.

References

• DEV-143

🚀 Enhancements

what

• Updated to local_sensitive_file resource, changed provider versions.

why

• This removes a terraform warning

🤖 Automatic Updates

what

This is an auto-generated PR that updates the context.tf file to the latest version from cloudposse/terraform-null-label

why

To support all the features of the context interface.

🚀 Enhancements

what

• Ensure module adheres var.enabled
• fix tests and ensure examples_import_key_test is run in test suite

why

• Resources were created even when var.enabled was false

references

• Issue identified in https://github.com/cloudposse/terraform-aws-components/pull/340

🐛 Bug Fixes

what

• Ensure module adheres var.enabled
• fix tests and ensure examples_import_key_test is run in test suite

why

• Resources were created even when var.enabled was false

references

• Issue identified in https://github.com/cloudposse/terraform-aws-components/pull/340

what

• update context.tf to v0.24.1
• minimum required Terraform version bumped to 0.13.0
• readme updated, Bridgecrew compliance badges added

why

• It allows for setting the letter case of tag names and labels, back compatibility with context v0.22.0 and below
• we have dropped support for Terraform 0.12
• To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant

Closes #62
Closes #63

what

• Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard

why

• Support Terraform 0.14

what

• Update aws provider to >= 2.0 avoid module version conflicts when used with >= 3.0 modules (eg. aws-eks-node-group).

why

• This module is being used with terraform-aws-eks-node-group which needs aws provider version to be >= 3.0 which is causing version conflicts.

references

• See cloudposse/terraform-aws-eks-node-group#41 for details. This tackles one of the modules causing the issue.

what

• Add tags population to aws_key_pair that are already using the variable

why

• For billing to be able to filter resources by tag
• Requirements within a company to tag all resources that support tags

what

• Delay filename outputs until files exist

what

• Instead of running an external command, use terraform's built in way of setting permissions on local file resources

why

• using native way always better

what

• Add a private_key to output parameters

why

• Sometimes it's useful to have this available -- e.g. for CI situations in which one needs to create a scratch key, create an instance, then provision the instance using the newly-created keypair.

what

• Do not show private key content

why

• Avoid showing private key in terraform diffs

what

• Use the latest label module to support the environment attribute

why

• The environment attribute is useful for naming AWS resources