Can't connect to EC2 agents on an IPv6 address

[mtrivedi50]

Describe the bug

• Prism cannot connect to EC2 instances using an IPv6 address. When running prism agent [apply | build | run], Prism gets stuck on the following step:

...
local-ec2-agent2[build] | ssh: connect to host ec2-52-90-51-71.compute-1.amazonaws.com port 22: Operation timed out
local-ec2-agent2[build] | SSH connection failed. Retrying in 5 seconds...
local-ec2-agent2[build] | ssh: connect to host ec2-52-90-51-71.compute-1.amazonaws.com port 22: Operation timed out
local-ec2-agent2[build] | SSH connection failed. Retrying in 5 seconds...
...

• Here is the agent configuration

# local-ec2-agent.yml

agent:
  type: ec2
  instance_type: t2.micro
  requirements: requirements.txt
  env:
    SNOWFLAKE_ACCOUNT: '{{ env("SNOWFLAKE_ACCOUNT") }}'
    SNOWFLAKE_DATABASE: '{{ env("SNOWFLAKE_DATABASE") }}'
    SNOWFLAKE_PASSWORD: '{{ env("SNOWFLAKE_PASSWORD") }}'
    SNOWFLAKE_ROLE: '{{ env("SNOWFLAKE_ROLE") }}'
    SNOWFLAKE_SCHEMA: '{{ env("SNOWFLAKE_SCHEMA") }}'
    SNOWFLAKE_USER: '{{ env("SNOWFLAKE_USER") }}'
    SNOWFLAKE_WAREHOUSE: '{{ env("SNOWFLAKE_WAREHOUSE") }}'
    GOOGLE_APPLICATION_CREDENTIALS: '{{ env("GOOGLE_APPLICATION_CREDENTIALS") }}'

CLI Arguments
prism agent apply -f local_ec2_agent.yml

Traceback
See the logs pasted above.

Expected behavior
A clear and concise description of what you expected to happen.

Desktop (please complete the following information):

• Mac OSx 12.5
• Python version: 3.10.12

Additional context

• Note that Prism creates all the necessary resources — the PEM key pair, the security group, and the instance itself. However, Prism cannot SSH into the instance when the host machine is using a IPv6 address.
• I confirmed that the security group has the appropriate inbound SSH permissions.