Add workspace for AWS account for already Onboarded AWS Organisation

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

Add workspace for AWS account for already Onboarded AWS Organisation

L2 Linker

I have configured Scan in Cloud Visibility for AWS and onboarded AWS organisation. Now I am required to grant end users access to one of the accounts -

  1. To configure new webapp for one of the discovered accounts under the onboarded organisation, do I need to onboard the account separately in Cloud Visibility? If yes, would Connect option will onboard the account?
  2. Also, when trying to manually onboard workspace for that account, getting error Account ID already exists.
  3. Since it gave error Account ID already exists, I tried to create web app for that particular account but there is no account id coming up in the dropdown.

Could someone please suggest if I am missing anything here?

 

Thanks!

Neha

1 accepted solution

Accepted Solutions

L7 Applicator

Hi @Neha Mehta​ 

 

1.

 

No, you generally do not need to onboard the individual account separately in Cloud Visibility. Since the account is part of the already onboarded AWS organisation SCA is aware of its existence through the discovery process

 

 

2.

 

Thats because account is already known to SCA/Cloud Visibility because it was discovered as a member of your onboarded AWS organisation and hence it’s not allowing to onboard a member account of an organization as a standalone account.

 

3.

 

Either you can wait for scheduled discovery or perform manual discovery.

 

Hope it helps !

 

 

View solution in original post

1 REPLY 1

L7 Applicator

Hi @Neha Mehta​ 

 

1.

 

No, you generally do not need to onboard the individual account separately in Cloud Visibility. Since the account is part of the already onboarded AWS organisation SCA is aware of its existence through the discovery process

 

 

2.

 

Thats because account is already known to SCA/Cloud Visibility because it was discovered as a member of your onboarded AWS organisation and hence it’s not allowing to onboard a member account of an organization as a standalone account.

 

3.

 

Either you can wait for scheduled discovery or perform manual discovery.

 

Hope it helps !

 

 

  • 1 accepted solution
  • 110 Views
  • 1 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!