Fails to delete Timestream InfluxDB and S3 filesystem resources when global region is configured

[jangidms]

Describe the bug

When global is included in the regions config alongside regional entries (e.g. us-east-1),
regional AWS services such as S3FilesFileSystem and TimestreamInfluxDBDbInstance are incorrectly
skipped in the regional pass with the error service 'X' is not global, but the session is.

After removing global from the regions config, the resources are listed and deleted correctly.

To Reproduce

1. Set regions in config to include both global and us-east-1:

regions:
  - global
  - us-east-1

2. Run aws-nuke with regional resources present (e.g. S3FilesFileSystem or TimestreamInfluxDBDbInstance in us-east-1):

./aws-nuke run \
  --config config.yaml \
  --no-dry-run=false \
  --no-alias-check \
  --log-level debug

3. Observe that regional resources are skipped in us-east-1.

Expected behavior

Regional services should be listed and deleted in us-east-1 regardless of whether global is also
included in the regions config.

Actual behavior

With global + us-east-1 — resources are skipped:
Below debug logs are from my local testing -

time="2026-07-17T14:40:11-05:00" level=debug msg="attempting to run lister" owner=us-east-1 resource_type=TimestreamInfluxDBDbInstance
time="2026-07-17T14:40:11-05:00" level=debug msg="listing Timestream InfluxDB instances"
time="2026-07-17T14:40:11-05:00" level=debug msg="skipping request: operation error Timestream InfluxDB: ListDbInstances, service 'Timestream InfluxDB' is not global, but the session is" owner=us-east-1 resource_type=TimestreamInfluxDBDbInstance

time="2026-07-17T14:40:17-05:00" level=debug msg="listing S3 file systems"
time="2026-07-17T14:40:17-05:00" level=error msg="failed to list S3 file systems" error="operation error S3Files: ListFileSystems, service 'S3Files' is not global, but the session is"
time="2026-07-17T14:40:17-05:00" level=debug msg="skipping request: operation error S3Files: ListFileSystems, service 'S3Files' is not global, but the session is" owner=us-east-1 resource_type=S3FilesFileSystem

With only us-east-1 (workaround) — resources are found and deleted correctly:

time="2026-07-17T14:22:19-05:00" level=debug msg="listing S3 file systems"
time="2026-07-17T14:22:19-05:00" level=debug msg="found S3 file system" id=fs-xxx name=my-filesystem
time="2026-07-17T14:22:19-05:00" level=debug msg="finished listing S3 file systems" count=1

time="2026-07-17T14:40:11-05:00" level=debug msg="listing Timestream InfluxDB instances"
time="2026-07-17T14:40:11-05:00" level=debug msg="found Timestream InfluxDB instance" id=id-1 name=my-instance status=AVAILABLE