Do we need to Deploy SIA connector for the additional AWS accounts onboarded later?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Do we need to Deploy SIA connector for the additional AWS accounts onboarded later?

L4 Transporter

Posting it here as there is no specific group for SIA

 

If I have initially onboarded the AWS account for AWS ZSP. Do we need to deploy connectors for the additional AWS accounts or the additional connectors we deploy is only for the redundancy and latency?

4 REPLIES 4

L4 Transporter

Connectors are deployed into a "Pool". You can deploy multiple connectors within a pool for redundancy or load balancing.

 

Within a "pool" there are one or more logical (cyberark) networks. Every device in the logical network should be routable from the connectors within that network, and they are addressed by the FQDN of the device. So if you have devices in multiple VPCs that are all peered and so you can route between them, you can address all the devices with a single pool and use the target's FQDN to identify the correct pool.

 

Also within a pool you can link one or many AWS Accounts, or VPCs, or Subnets, that should all be routable from the connectors in that pool. These devices would be addressed by their AWS GUID rather than FQDN.

 

So if you have one AWS Account with two VPCs that are peered you could have one pool to address all the devices in both VPCs. If the two VPCs are not routable then you would need a separate pool and separate connectors to serve each VPC.

 

If you have two AWS Accounts each with one VPC and the VPCs are not routable then you would need a separate pool and separate connector for each Account. If you have two Accounts and their VPCs are fully peered and all devices in both Accounts are routable from each other then you could use a single Pool to service all the devices

Thanks for the reply @Jon Musker​ ,

 

So, it means that until all the AWS instances are reachable through DPA connector we are good right.

 

If there is network isolation between them. Then we have to deploy them separately right.

 

yes, that's right.

 

Over time you may find there are subtle differences between connecting to a VM based on the name, or the GUID, or theFQDN, but the configuration of Pools and Networks should enable you to get the right combination for your users.

L4 Transporter

Hi @Somidi Vamshi​ 

 

It seems that Jon Musker provided an answer to your question. Could you kindly let us know if this solution helped?

If so, please mark the answer as 'Select as Best' to assist other community members.

Thank you, Liad

  • 19 Views
  • 4 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!