bug: lambda VPC attachment can break outbound connectivity for public threat feeds

[Panacota96]

Summary

The Flask Lambda is attached to default VPC subnets but the Terraform stack does not provision NAT or equivalent outbound access for public HTTP dependencies such as OpenPhish.

Evidence

• File: phishing-platform-infra/terraform/lambda.tf:51-54
• File: phishing-platform-infra/terraform/elasticache.tf attaches Lambda/Redis to VPC resources.
• App code fetches OpenPhish from �pp/dashboard/routes.py using
  equests.get("https://openphish.com/feed.txt").

Impact

• Threat-feed and any other public egress integrations may fail in AWS even if they work locally.
• The runtime networking model is ambiguous and likely environment-dependent.

Expected outcome

Make outbound connectivity explicit: either remove unnecessary VPC attachment or provision the required NAT/VPC endpoints and document the tradeoff.