1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
1
Resolved after I added an IP address of AWS pulled from this JSON file to one of the inbound rules: https://ip-ranges.amazonaws.com/ip-ranges.json (filter on "EC2_INSTANCE_CONNECT" and your region)
for full tutorial: https://docs.aws.amazon.com/vpc/latest/userguide/aws-ip-ranges.html
Sadly this didn't seem to be in the overall tutorial on EC2.
beantwortet vor 2 Monaten
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- Wie verbinde ich verschiedene Zweigstellen mithilfe von AWS Site-to-Site VPN und AWS Direct Connect?AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 4 Monaten
- AWS OFFICIALAktualisiert vor 3 Jahren
I did this and it worked but I'm confused. If an "all tcp" rule has 0.0.0.0/0 vs. the ca-central-1 ip, would 'all' work and negate having to spend the effort to have the added ip address? Yes, 0.0.0.0/0 is bad for security, but it should work, no?
RickSegal not sure, I have just started with AWS about 1.5 months ago :)