My Terraform code has been working fine up until this afternoon. I have not knowingly made any changes when when I did a plan / apply / destroy I have started getting this error.

Any suggestions on how to resolve this?

Plan: 21 to add, 0 to change, 0 to destroy.
╷
│ Error: Plugin did not respond
│
│   with data.aws_subnets.subnets,
│   on data.tf line 18, in data "aws_subnets" "subnets":
│   18: data "aws_subnets" "subnets" {
│
│ The plugin encountered an error, and failed to respond to the plugin.(*GRPCProvider).ReadDataSource call. The plugin logs may contain more details.
╵
╷
│ Error: Plugin did not respond
│
│   with data.aws_subnets.batch_subnets,
│   on data.tf line 30, in data "aws_subnets" "batch_subnets":
│   30: data "aws_subnets" "batch_subnets" {
│
│ The plugin encountered an error, and failed to respond to the plugin.(*GRPCProvider).ReadDataSource call. The plugin logs may contain more details.
╵
╷
│ Error: Plugin did not respond
│
│   with module.batch_security_group.aws_security_group.this_name_prefix[0],
│   on .terraform/modules/batch_security_group/main.tf line 37, in resource "aws_security_group" "this_name_prefix":
│   37: resource "aws_security_group" "this_name_prefix" {
│
│ The plugin encountered an error, and failed to respond to the plugin.(*GRPCProvider).ReadResource call. The plugin logs may contain more details.
╵
╷
│ Error: Plugin did not respond
│
│   with module.rsdl_batch.aws_batch_job_definition.this["rsdl-core"],
│   on .terraform/modules/rsdl_batch/main.tf line 265, in resource "aws_batch_job_definition" "this":
│  265: resource "aws_batch_job_definition" "this" {
│
│ The plugin encountered an error, and failed to respond to the plugin.(*GRPCProvider).PlanResourceChange call. The plugin logs may contain more details.
╵

Stack trace from the terraform-provider-aws_v5.49.0_x5 plugin:

panic: interface conversion: interface {} is nil, not map[string]interface {}

Error: The terraform-provider-aws_v5.49.0_x5 plugin crashed!

This is always indicative of a bug within the plugin. It would be immensely
helpful if you could report the crash with the plugin's maintainers so that it
can be fixed. The output above should help diagnose the issue.