Elastic Beanstalk Worker (PHP 8.1 / AL2 3.5.7) failing to deploy - aws-sqsd can't create Thread: Resource temporarily unavailable (ThreadError)

I wonder if anyone else has had this issue before? Our deployment always succeeds to our identical WebApp instance (configured nearly exactly the same minus being a worker in a CloudFormation template).

These are the errors in the log files:

2023-08-07T06:32:16Z init: initializing aws-sqsd 3.0.4 (2022-03-18)
2023-08-07T06:32:16Z schedule-parser: Successfully loaded 7 scheduled tasks from file /var/app/current/cron.yaml .
2023-08-07T06:33:17Z leader-election:  initialized leader election
2023-08-07T06:33:18Z scheduler: initialized 7 job's pending time
2023-08-07T06:37:56Z init: initializing aws-sqsd 3.0.4 (2022-03-18)
2023-08-07T06:37:57Z init: can't create Thread: Resource temporarily unavailable (ThreadError)
	at /opt/elasticbeanstalk/lib/ruby/lib/ruby/2.6.0/timeout.rb:83:in `start'
	from /opt/elasticbeanstalk/lib/ruby/lib/ruby/2.6.0/timeout.rb:83:in `block in timeout'
	from /opt/elasticbeanstalk/lib/ruby/lib/ruby/2.6.0/timeout.rb:103:in `timeout'
	from /opt/elasticbeanstalk/lib/ruby/lib/ruby/2.6.0/net/http.rb:945:in `connect'
	from /opt/elasticbeanstalk/lib/ruby/lib/ruby/2.6.0/net/http.rb:930:in `do_start'
	from /opt/elasticbeanstalk/lib/ruby/lib/ruby/2.6.0/net/http.rb:919:in `start'
	from /opt/elasticbeanstalk/lib/ruby/lib/ruby/2.6.0/net/http.rb:605:in `start'
	from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/aws-sqsd-3.0.4/lib/aws-sqsd/sqsd_utils.rb:31:in `generate_token'
	from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/aws-sqsd-3.0.4/lib/aws-sqsd/sqsd_utils.rb:17:in `get_instance_metadata'
	from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/aws-sqsd-3.0.4/lib/aws-sqsd/config.rb:119:in `instance_doc'
	from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/aws-sqsd-3.0.4/lib/aws-sqsd/config.rb:95:in `region'
	from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/aws-sqsd-3.0.4/lib/aws-sqsd/daemon.rb:37:in `initialize'
	from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/aws-sqsd-3.0.4/bin/aws-sqsd:34:in `new'
	from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/aws-sqsd-3.0.4/bin/aws-sqsd:34:in `start'
	from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/aws-sqsd-3.0.4/bin/aws-sqsd:83:in `launch'
	from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/aws-sqsd-3.0.4/bin/aws-sqsd:111:in `<top (required)>'
	from /opt/elasticbeanstalk/lib/ruby/bin/aws-sqsd:23:in `load'
	from /opt/elasticbeanstalk/lib/ruby/bin/aws-sqsd:23:in `<main>'

There is also an error in composer when trying to install packages

In Process.php line 355:
                                   
  Unable to launch a new process.  

Shortly after this, the dashboard updates with this message: "Environment health has transitioned from Degraded to No Data. None of the instances are sending data."

Any idea what we can do to resolve this issue, or is it a bug with SQSD?