Packer hangs during provisioning

amazon-ebs output will be in this color.

==> amazon-ebs: Prevalidating AMI Name...
    amazon-ebs: Found Image ID: ami-8af219f3
==> amazon-ebs: Creating temporary keypair: packer_597b25d9-22e4-f67f-25c8-3b0aab315e3e
==> amazon-ebs: Creating temporary security group for this instance: packer_597b25db-43fd-7889-892c-cda656f44167
==> amazon-ebs: Authorizing access to port 22 on the temporary security group...
==> amazon-ebs: Launching a source AWS instance...
    amazon-ebs: Instance ID: i-08820de52d02d3229
==> amazon-ebs: Waiting for instance (i-08820de52d02d3229) to become ready...
==> amazon-ebs: Adding tags to source instance
    amazon-ebs: Adding tag: "Name": "annaken-packer-instance"
==> amazon-ebs: Waiting for SSH to become available...
==> amazon-ebs: Connected to SSH!
==> amazon-ebs: Provisioning with shell script: /tmp/packer-shell082198671
    amazon-ebs: Hit:1 http://eu-west-1.ec2.archive.ubuntu.com/ubuntu xenial InRelease
    amazon-ebs: Get:2 http://eu-west-1.ec2.archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
    amazon-ebs: Get:3 http://eu-west-1.ec2.archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB]
    amazon-ebs: Hit:4 http://ppa.launchpad.net/ansible/ansible/ubuntu xenial InRelease
    amazon-ebs: Get:5 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
    amazon-ebs: Get:6 http://eu-west-1.ec2.archive.ubuntu.com/ubuntu xenial-updates/main Sources [265 kB]
    amazon-ebs: Get:7 http://eu-west-1.ec2.archive.ubuntu.com/ubuntu xenial-updates/universe Sources [166 kB]
    amazon-ebs: Get:8 http://eu-west-1.ec2.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [593 kB]
    amazon-ebs: Get:9 http://eu-west-1.ec2.archive.ubuntu.com/ubuntu xenial-updates/main Translation-en [239 kB]
    amazon-ebs: Get:10 http://eu-west-1.ec2.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [511 kB]
    amazon-ebs: Get:11 http://eu-west-1.ec2.archive.ubuntu.com/ubuntu xenial-updates/universe Translation-en [198 kB]
    amazon-ebs: Get:12 http://security.ubuntu.com/ubuntu xenial-security/main Sources [82.5 kB]
    amazon-ebs: Get:13 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages [316 kB]
    amazon-ebs: Get:14 http://security.ubuntu.com/ubuntu xenial-security/main Translation-en [133 kB]
    amazon-ebs: Get:15 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages [149 kB]
    amazon-ebs: Get:16 http://security.ubuntu.com/ubuntu xenial-security/universe Translation-en [77.0 kB]
    amazon-ebs: Fetched 3,036 kB in 1s (2,696 kB/s)
    amazon-ebs: Reading package lists...
    amazon-ebs: Reading package lists...
    amazon-ebs: Building dependency tree...
    amazon-ebs: Reading state information...
    amazon-ebs: aptitude is already the newest version (0.7.4-2ubuntu2).
    amazon-ebs: python-minimal is already the newest version (2.7.11-1).
    amazon-ebs: 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
==> amazon-ebs: Provisioning with Ansible...
==> amazon-ebs: Executing Ansible: ansible-playbook --extra-vars packer_build_name=amazon-ebs packer_builder_type=amazon-ebs -i /tmp/packer-provisioner-ansible008447774 /home/annaken/Repos/global-infrastructure-amis/dgs-hardened/dgs-hardened-ami.yml --private-key /tmp/ansible-key856823803
    amazon-ebs: [DEPRECATION WARNING]: Instead of sudo/sudo_user, use become/become_user and
    amazon-ebs: make sure become_method is 'sudo' (default).
    amazon-ebs: This feature will be removed in a
    amazon-ebs: future release. Deprecation warnings can be disabled by setting
    amazon-ebs: deprecation_warnings=False in ansible.cfg.
    amazon-ebs:
    amazon-ebs: PLAY [all] *********************************************************************
    amazon-ebs:
    amazon-ebs: TASK [Gathering Facts] *********************************************************

Any solution to this ?

1709301582,,ui,say,==> amazon-ebs: Stopping the source instance...
1709301582,,ui,message, amazon-ebs: Stopping instance
1709301583,,ui,say,==> amazon-ebs: Waiting for the instance to stop...
1709301614,,ui,say,==> amazon-ebs: Creating AMI windows_2019_golden_ami_march_2024 from instance i-0346dec52407102f1
1709301614,,ui,message, amazon-ebs: AMI: ami-0f17ae67eccfbbdcd
1709301614,,ui,say,==> amazon-ebs: Waiting for AMI to become ready...

we are execting packer build from Jenkins and it is getting stuck at "Waiting for AMI to become ready .."