v1.1.1

feature/disable-alarm-action @kris-Nabis (#145)

what

• Disables the use of Alarm Actions

why

• Unable to create the resource if execution user doesn't have iam:CreateServiceLinkedRole
• Somewhat random reboot triggers. Alarm Action reboot is triggered pretty consistently, even while EC2 Resource is not in an alarm state.

references

• closes #131

🤖 Automatic Updates

Update README.md and docs @cloudpossebot (#175)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

v1.1.0

Correct how the volume_id is selected - Fix #165 @it-praktyk (#171)

what

Fix #165 - allows create an EC2 instance with additional volumes.

why

The issue was introduced here.

The one Terraform function returns an error, that blocks creating EC2 instances with additional (non-root) volumes.

references

• The one Terraform function docs

closes #165

🤖 Automatic Updates

Update README.md and docs @cloudpossebot (#167)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

v0.50.0

• AWS provider V4 Compatibility

v1.0.0

• Support AWS provider V5
• Adding external ENIs

v0.49.0

Adding external ENIs @jamengual (#159)

what

Add the ability to add external ENIs to the instance

why

For ec2 instances deployments clusters where the IPs are required to be unique and not change it is necessary to create ENIs outside of this module so that the instance termination does not change the ENI and IP attached.

references

Sync github @max-lobur (#156)

Rebuild github dir from the template

v0.48.0

• No changes

v0.47.1

🚀 Enhancements

Only get data.aws_ami.info if it's actually required @y3ti (#151)

what

• Use data.aws_ami.info only if it's actually required

why

• Fix Your query returned no results" error once the AMI ID is not listed within AWS marketplace

references

• closes #150
• closes #143

v0.47.0

Do not set iops and throughput for non-supporting volume types @cinacio (#142)

what

• Only set iops and throughput arguments for volume types supporting those options.

why

• According to the documentation for the aws_ebs_volume resource, the iops argument is only valid for volumes types io1, io2 & gp3.
• According to the same documentation, the throughput argument is only valid for volume type gp3.
• Setting the throughput of a gp2 volume to "0" triggers the following error

Error: expected throughput to be in the range (125 - 1000), got 0

with module.instance.aws_ebs_volume.default[0],
on .terraform/modules/instance/main.tf line 178, in resource "aws_ebs_volume" "default":
178: throughput = local.ebs_throughput

references

• closes #137

v0.46.0

Adding support for secondary private ips @vale21 (#153)

what

• Adding support for secondary private ips to EC2 instances created with this module

why

• I cannot set secondary private IPs to my EC2 instance using your module

references

• Fixes #152

v0.45.2

🚀 Enhancements

Support AWS partition for SSM resources @dlundgren (#148)

what

• SSM patch is currently hardcoded to aws so this doesn't work when trying to use the role with AWS GovCloud.

why

• This allows the role to work in with AWS GovCloud

references

• The cloudwatch-alarm supports the AWS GovCloud partition