SOLVED

My inbound rule to the gateway was too restrictive only allowing ips from a specific subnet! If this does help anyone else:

• VPC management > Route Tables > Routes > Destination should be open (say 0.0.0.0/0) and target should be the gateway.

It's been a long time since I was working with aws and I haven't been able to figure this out on my own.

Basically, my EC2 instance was able to ping google yesterday when I was logged in with ssh. I had two rules inbound on the security group associated with the VPC:

IPv4    SSH TCP 22  my ipd

IPv4    All UDP 0 - 65535   my ip

When I changed the second rule to;

HTTPS   TCP 443 security group

I could use my ec2 instance as a proxy to access my opensearch instance on the same VPC but, I could no longer ping google.

So, I added back the rule I replaced, and I still can't ping google.

I've confirmed that I have an internet gateway connected to the VPC.

I'm reading documentation and brushing up on my networking, but if someone does have an inkling right off the bat, I'd be very grateful.