Lock file maintenance

[renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: Branch creation - "before 4am on monday" in timezone Europe/London, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[github-actions]

Expected Changes

ec2-instance › i-0e9b4893e76c7b0aa

--- current
+++ planned
@@ -1,87 +1,13 @@
-ami: ami-0f199c73e611e6068
-arn: arn:aws:ec2:eu-west-2:540044833068:instance/i-0e9b4893e76c7b0aa
-associate_public_ip_address: true
-availability_zone: eu-west-2a
-capacity_reservation_specification:
-    - capacity_reservation_preference: open
-      capacity_reservation_target: []
-cpu_core_count: 1
-cpu_options:
-    - amd_sev_snp: ""
-      core_count: 1
-      threads_per_core: 2
-cpu_threads_per_core: 2
-credit_specification:
-    - cpu_credits: unlimited
-disable_api_stop: false
-disable_api_termination: false
-ebs_block_device: []
-ebs_optimized: false
-enclave_options:
-    - enabled: false
-ephemeral_block_device: []
+ami: ami-026d5ef1c0e90fd80
+credit_specification: []
 get_password_data: false
-hibernation: false
-host_id: ""
-iam_instance_profile: ""
-id: i-0e9b4893e76c7b0aa
-instance_initiated_shutdown_behavior: stop
-instance_lifecycle: ""
-instance_market_options: []
-instance_state: running
 instance_type: t3.micro
-ipv6_address_count: 0
-ipv6_addresses: []
-key_name: ""
 launch_template: []
-maintenance_options:
-    - auto_recovery: default
-metadata_options:
-    - http_endpoint: enabled
-      http_protocol_ipv6: disabled
-      http_put_response_hop_limit: 1
-      http_tokens: optional
-      instance_metadata_tags: disabled
-monitoring: false
-network_interface: []
-outpost_arn: ""
-password_data: ""
-placement_group: ""
-placement_partition_number: 0
-primary_network_interface_id: eni-0a13c9101d2f83f47
-private_dns: ip-172-31-25-125.eu-west-2.compute.internal
-private_dns_name_options:
-    - enable_resource_name_dns_a_record: false
-      enable_resource_name_dns_aaaa_record: false
-      hostname_type: ip-name
-private_ip: 172.31.25.125
-public_dns: ec2-35-178-131-180.eu-west-2.compute.amazonaws.com
-public_ip: 35.178.131.180
-root_block_device:
-    - delete_on_termination: true
-      device_name: /dev/xvda
-      encrypted: false
-      iops: 0
-      kms_key_id: ""
-      tags: {}
-      tags_all: {}
-      throughput: 0
-      volume_id: vol-0c13c385799b4a655
-      volume_size: 8
-      volume_type: standard
-secondary_private_ips: []
-security_groups:
-    - default
 source_dest_check: true
-spot_instance_request_id: ""
-subnet_id: subnet-0435f45b197666342
 tags:
     Name: SG Removal Example Instance 1
 tags_all:
     Name: SG Removal Example Instance 1
-tenancy: default
 terraform_address: module.scenarios[0].aws_instance.example_1
 terraform_name: module.scenarios[0].aws_instance.example_1
 user_data_replace_on_change: false
-vpc_security_group_ids:
-    - sg-0948cdc916d1efffd

ec2-instance › i-0ccab1235ae0f4467

--- current
+++ planned
@@ -1,87 +1,13 @@
-ami: ami-0f199c73e611e6068
-arn: arn:aws:ec2:eu-west-2:540044833068:instance/i-0ccab1235ae0f4467
-associate_public_ip_address: true
-availability_zone: eu-west-2a
-capacity_reservation_specification:
-    - capacity_reservation_preference: open
-      capacity_reservation_target: []
-cpu_core_count: 1
-cpu_options:
-    - amd_sev_snp: ""
-      core_count: 1
-      threads_per_core: 2
-cpu_threads_per_core: 2
-credit_specification:
-    - cpu_credits: unlimited
-disable_api_stop: false
-disable_api_termination: false
-ebs_block_device: []
-ebs_optimized: false
-enclave_options:
-    - enabled: false
-ephemeral_block_device: []
+ami: ami-026d5ef1c0e90fd80
+credit_specification: []
 get_password_data: false
-hibernation: false
-host_id: ""
-iam_instance_profile: ""
-id: i-0ccab1235ae0f4467
-instance_initiated_shutdown_behavior: stop
-instance_lifecycle: ""
-instance_market_options: []
-instance_state: running
 instance_type: t3.micro
-ipv6_address_count: 0
-ipv6_addresses: []
-key_name: ""
 launch_template: []
-maintenance_options:
-    - auto_recovery: default
-metadata_options:
-    - http_endpoint: enabled
-      http_protocol_ipv6: disabled
-      http_put_response_hop_limit: 1
-      http_tokens: optional
-      instance_metadata_tags: disabled
-monitoring: false
-network_interface: []
-outpost_arn: ""
-password_data: ""
-placement_group: ""
-placement_partition_number: 0
-primary_network_interface_id: eni-074e5724e0c7ec97c
-private_dns: ip-172-31-19-139.eu-west-2.compute.internal
-private_dns_name_options:
-    - enable_resource_name_dns_a_record: false
-      enable_resource_name_dns_aaaa_record: false
-      hostname_type: ip-name
-private_ip: 172.31.19.139
-public_dns: ec2-35-177-105-12.eu-west-2.compute.amazonaws.com
-public_ip: 35.177.105.12
-root_block_device:
-    - delete_on_termination: true
-      device_name: /dev/xvda
-      encrypted: false
-      iops: 0
-      kms_key_id: ""
-      tags: {}
-      tags_all: {}
-      throughput: 0
-      volume_id: vol-0ee2a48040c0c9698
-      volume_size: 8
-      volume_type: standard
-secondary_private_ips: []
-security_groups:
-    - default
 source_dest_check: true
-spot_instance_request_id: ""
-subnet_id: subnet-0435f45b197666342
 tags:
     Name: SG Removal Example Instance 1
 tags_all:
     Name: SG Removal Example Instance 1
-tenancy: default
 terraform_address: module.scenarios[0].aws_instance.example_2
 terraform_name: module.scenarios[0].aws_instance.example_2
 user_data_replace_on_change: false
-vpc_security_group_ids:
-    - sg-0948cdc916d1efffd

Blast Radius

Items	Edges
16	26

Open in Overmind

Risks

Possible Downtime Due to Provider Update [Medium]

Updating the AWS provider from 5.49.0 to 5.52.0 could introduce changes that are not compatible with the current infrastructure configuration, specifically with ec2-instance and ec2-volume resources. Given that the ec2-instance resources, i-0e9b4893e76c7b0aa and i-0ccab1235ae0f4467, are currently running and associated with public IPs and volumes, any disruptive changes or deprecations could lead to provisioning errors or downtime. While the minor version update for the Random provider is less concerning, changes in the AWS provider necessitate careful review of release notes and testing. The current system's dependencies on specific AWS resource configurations, such as t3.micro instances and standard volume types, heighten the need for this caution.

Risk of Configuration Drift [Low]

As the lock file updates provider versions, there's a potential risk that the applied infrastructure might drift from the configuration managed in Terraform, especially if new provider versions introduce defaults or behaviors that differ from the current state. Both EC2 instances and associated resources, such as network interfaces and volumes, could be affected if the new provider versions handle certain AWS resource attributes differently. This drift can lead to inconsistencies between the actual cloud environment and Terraform state, complicating further infrastructure management and updates. This risk underscores the importance of testing changes in an isolated environment to detect and address drift before applying updates to production systems.

Potential Interruptions in Instance Connectivity [Medium]

The update to the AWS provider may affect how Terraform interacts with EC2 instances and their networking configurations. Given the current state of the EC2 instances (i-0e9b4893e76c7b0aa and i-0ccab1235ae0f4467) and their reliance on specific network interfaces and security groups, alterations in provider behavior could impact instance connectivity. This includes changes to public IP addressing, DNS name resolution, or security group assignments, potentially leading to service interruptions. It is critical to verify the updated AWS provider's compatibility with the existing Terraform configuration and AWS resource setup to mitigate this risk.