Skip to content
This repository has been archived by the owner on Oct 4, 2024. It is now read-only.

MWAA: testing connectivity fails with "KeyError - 'PortRange'" #191

Open
ivica-k opened this issue Jan 31, 2022 · 1 comment
Open

MWAA: testing connectivity fails with "KeyError - 'PortRange'" #191

ivica-k opened this issue Jan 31, 2022 · 1 comment

Comments

@ivica-k
Copy link

ivica-k commented Jan 31, 2022

Hey :)

Thank you for providing the verify_env.py script for MWAA. However, running it fails with an error in the ### Testing connectivity to the following service endpoints from MWAA enis... step. The error is not apparent from the script itself but is clearly visible from SSM Automation execution. This is the traceback

Traceback (most recent call last):
  File "/tmp/ea8016b8-bc1f-4d1c-9910-cd137a8b0a0d-2022-01-31-15-23-46/customer_script.py", line 80, in eval_nat_nacls
    check_ingress_from_dst(ingress_acls, dst_ip)
  File "/tmp/ea8016b8-bc1f-4d1c-9910-cd137a8b0a0d-2022-01-31-15-23-46/customer_script.py", line 41, in check_ingress_from_dst
    if ((acl.get('Protocol') == '-1') or (set(range(src_port_from,src_port_to)).issubset(range(acl['PortRange']['From'], acl['PortRange']['To'] +1)))):
KeyError: 'PortRange'

It seems to me that the code that fails comes from Connectivity Troubleshooter that this repo does not control.

I'd be happy to provide more information.

@twknight
Copy link

Unfortunately, this is still an issue.

(Not very helpful, but consider this my upvote!)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants