Create cluster manifests using following config:

compute:
 ...
  platform:
    aws:
      amiID: ami-0c5e051fb7dc39f8d (BYO-AMI uploaded in eusc-de-east-1)
controlPlane:
  ...
  platform:
    aws:
      amiID: ami-0c5e051fb7dc39f8d (BYO-AMI uploaded in eusc-de-east-1)
platform:
  ...
  aws:
    region: eusc-de-east-1

It looks like the installer didn't respect amiID field,  it was trying to copy AMI from us-east-1, but get stuck while creating machine manifests.

The eusc-de-east-1 region is not a public AWS region, if the AMI is unavailable, the installer is not supposed to copy the AMI from us-east-1.

```
time="2026-02-05T22:17:53-05:00" level=debug msg="  Generating Image..."
time="2026-02-05T22:17:53-05:00" level=debug msg="No AMI found in eusc-de-east-1. Using AMI from us-east-1."
time="2026-02-05T22:17:53-05:00" level=debug msg="No AMI found in eusc-de-east-1. Using AMI from us-east-1."
time="2026-02-05T22:17:53-05:00" level=debug msg="  Fetching Master Ignition Config..."
time="2026-02-05T22:17:53-05:00" level=debug msg="    Fetching Install Config..."
time="2026-02-05T22:17:53-05:00" level=debug msg="    Reusing previously-fetched Install Config"
time="2026-02-05T22:17:53-05:00" level=debug msg="    Fetching Machine Config Server Root CA..."
time="2026-02-05T22:17:53-05:00" level=debug msg="    Generating Machine Config Server Root CA..."
time="2026-02-05T22:17:53-05:00" level=debug msg="  Generating Master Ignition Config..."
time="2026-02-05T22:17:53-05:00" level=debug msg="Generating Master Machines..."
```

    

   4.22.0-0.nightly-2026-02-03-002928
    

always
    

    1.Create manifests in eusc-de-east-1 region
    

   Installer got stuck.
    

   Manifests are created successfully