Connecting EC2 to AWS ActiveGate

[shakib]

I have an AWS EC2 that I installed a OneAgent on before setting up an Environment ActiveGate in AWS. 

The EC2 instance and AG are both in the same network zone. And yet the EC2 instance is still connecting directly to the Dynatrace cluster, even after I restarted the OneAgent. 
When I check --get-server on the EC2 I see the AG on AWS as one of the listed entities but I'm perplexed as to why it doesn't connect to it first instead of directly to the cluster. 

I assume there is a networking issue that is blocking it. If it is a networking issue, I don't see anything about it in the oneagent-logmon-general or detailed logs on the EC2 instance.

[shakib · Accepted solution]

Ok so this was resolved after adding inbound rule on the ActiveGate's security group to allow 9999 traffic from that specific EC2 instance. 

[techean]

great, Its basically the product behavior, if oneagent is not able to connect to AG it will directly communicate with cluster.

[jgibson]

We also deal with firewalls setup to protect between accounts and have to open port 9999 to those ActiveGates  😞