0

I have setup an EC2 instance with VNC GUI access to it. While browsing LinkedIn from the EC2 instance, I am unable to open custom LinkedIn URLs, i.e. URL of a specific user (lets say https://np.linkedin.com/in/abc123). I have also opened port 443, 8080 from security groups. I get ping reply from np.linkedin.com though. Can anyone guide me what could have gone wrong?

Siraj Ahmad
  • 53
  • 7
  • What is the error you get? Is it 503? It is possible that linked in is blocking aws ip space from accessing certain parts of their site due to abuse. – Doon Aug 04 '15 at 09:41
  • Tor exit nodes run into the same issue. – wogsland Jul 06 '16 at 20:55

1 Answers1

2

I can verify that unauthenticated access to LinkedIn from an Amazon EC2 instance does not display user information (and the URL mentions something about sentinel_org_blocked.

I suspect that LinkedIn is intentionally blocking access from the Amazon EC2 IP address range to prevent information scraping. It works successfully if the user is logged into LinkedIn.

John Rotenstein
  • 241,921
  • 22
  • 380
  • 470