Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This page outlines the steps to enable AWS Integration with Zilla. We will be using the Delegate access across AWS accounts using IAM roles tutorial as a guide to allow you to delegate access of your AWS account to Zilla’s AWS account using AWS IAM Roles.

Table of Contents
minLevel1
maxLevel7
printablefalse

Bring in IAM Users and Groups into Zilla

To bring in IAM Users and Groups of an AWS Account, you need to create an IAM Role and attach an IAM Policy to it.

Create an IAM Policy for IAM Users and Groups

Steps to create an IAM Policy

...

Login to the AWS Account via the AWS Management Console

...

Enter your 12-digit account number. Click Next and then enter your username and password to login.

...

Once you are logged in, you will land on the home page with a search bar at the top.

...

 

...

In the search bar, search for IAM and click on the search result called IAM.

...

 

...

You will be redirected to the IAM dashboard.

...

 

...

Before creating a role, we will first create a policy that will be assigned to the role. Click Policies on the left hand side menu.

...

 

...

.

...

The

...

Code Block
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": "iam:GetGroup",
            "Resource": "arn:aws:iam::<YOUR_AWS_ACCOUNt_ID>:group/*"
        },
        {
            "Sid": "VisualEditor1",
            "Effect": "Allow",
            "Action": "iam:GetAccountAuthorizationDetails",
            "Resource": "*"
        }
    ]
}

 

...

 

...

Optionally add tags and click Next: Review.

...

Review Policy: On the review page, enter the Name (Zilla-IAM-Reader-Policy) and optionally a description for the policy. Review the permissions assigned to the policy and then click Create policy The policy will look like this:

...

 

...

You will see a success message that the policy has been created.

...

 

...

To confirm that the policy is present, you can search for it in the policy search bar. You will see your newly added policy in the list.

...

 

...

Click on the policy Zilla-IAM-Reader-Policy to double check the assigned permissions. The policy will look like this:

...

Click on the {} JSON tab to double check the policy json. (Account ID redacted from screenshot)

...

 

Now that you have created the policy, the next step is to create a cross account Role.

Create an IAM Role for IAM Users and Groups

Steps to create an IAM Role

  1. Click on Roles from the left hand side menu to begin then click Create role button to create a new IAM Role.

    Image Removed

     

  2. Under Select type of trusted entity select Another AWS account and enter the 12 digit Account ID of Zilla (087210011007). Click Next: Permissions.

    Image Removed

     

  3. On the permissions page, search for the policy created ,Zilla-IAM-Reader-Policy , and select the checkbox. Click Next: Tags.

    Image Removed

     

  4. Optionally add tags and click Next: Review.

    Image Removed

     

  5. On the review page, add the name of the role Zilla-IAM-Reader-Role and optionally add a description. Review the trusted entity account id matches Zilla’s account Id (087210011007) and that the Policies section contains Zilla-IAM-Reader-Policy. Click Create role.

    Image Removed

     

  6. Once the role is created, you can search for it on the roles tab and click on the role to check its details.

    Image Removed

     

  7. On the role details page, double check the policy under Permissions and Trusted entities has Zilla Account ID (087210011007) under Trust relationships.

    Image Removed

     

Info

Notes:

  1. Copy the Role ARN. For example: arn:aws:iam::<YOUR_AWS_ACCOUNT_ID>:role/Zilla-IAM-Reader-Role and keep it handy for later.

  2. Typically IAM Users and Groups are created against each AWS Account, so you will need to create the above role and policy for each of your AWS Accounts.

  3. Currently, the IAM Role and Policy creation to bring in IAM Users and Groups is mandatory in Zilla.

Include Page
AWS - Create an IAM Role for IAM Users, Groups, Roles and Resources
AWS - Create an IAM Role for IAM Users, Groups, Roles and Resources

Bring SSO Users, Groups and Permission Sets into Zilla

...

To Bring the SSO users, Groups and Permission

...

Steps to create an IAM Policy

  1. Click on Policies on the left hand side menu of the IAM Dashboard.

    Image Removed

     

  2. Click Create policy and click on the JSON tab.

    Image Removed
  3. IAM Policy Creation: Enter the following json snippet and click Next: Tags. The following policy allows Zilla to read the SSO Users, Groups and Permission Sets information from your AWS account

    Code Block
    {
        "Version": "2012-10-17",
        "Statement": [
            {
                "Sid": "VisualEditor0",
                "Effect": "Allow",
                "Action": [
                    "sso:ListAccountAssignments",
                    "sso:ListPermissionSetsProvisionedToAccount",
                    "sso:DescribePermissionSet"
                ],
                "Resource": [
                    "arn:aws:sso:::instance/*",
                    "arn:aws:sso:::permissionSet/*/*",
                    "arn:aws:sso:::account/*"
                ]
            },
            {
                "Sid": "VisualEditor1",
                "Effect": "Allow",
                "Action": [
                    "identitystore:DescribeUser",
                    "identitystore:DescribeGroup"
                ],
                "Resource": "*"
            }
        ]
    }

     

    Image Removed

     

  4. Optionally add tags and click Next: Review.

  5. Image Removed

    Review Policy: On the review page, enter the Name (Zilla-SSO-Reader-Policy) and optionally a description for the policy. Review the permissions assigned to the policy and then click Create policy. The policy will look like this:

    Image Removed

     

  6. You will see a success message like this:

    Image Removed

     

  7. To confirm that the policy is present, you can search for it in the policy search bar. You will see your newly added policy in the list.

    Image Removed

     

  8. Click the policy Zilla-SSO-Reader-Policy to double check the assigned permissions. The policy will look like this:

    Image Removed

    Click on the {} JSON tab to double check the policy json.

    Image Removed

     

Now that you have created the policy, the next step is to create a cross account Role.

Create an IAM Role for SSO Users, Groups and Permission Set

Steps to create an IAM Role

  1. Click Roles from the left hand side menu to begin.

    Image Removed

     

  2. Click Create role button to create a new IAM Role. Under Select type of trusted entity select Another AWS account and enter the 12 digit Account ID of Zilla (087210011007) and then click Next: Permissions.

    Image Removed

     

  3. On the permissions page, search for the policy created ,Zilla-SSO-Reader-Policy , and select the checkbox. Then click Next: Tags.

    Image Removed

     

  4. Optionally add tags and click Next: Review.

    Image Removed

     

  5. On the review page, add the name of the role Zilla-SSO-Reader-Role and optionally add a description. Review the trusted entity account id matches Zilla’s account Id (087210011007) and that the Policies section contains Zilla-SSO-Reader-Policy, then click Create role .

    Image Removed

     

  6. Once the role is created, you can search for it on the roles tab and click on the role to check its details.

    Image Removed

     

  7. On the role details page, double check the policy under Permissions and Trusted entities has Zilla Account ID (087210011007) under Trust relationships.

    Image Removed

     

Info

Notes:

  1. Copy the Role ARN. For example: arn:aws:iam::<YOUR_AWS_ACCOUNT_ID>:role/Zilla-SSO-Reader-Role and keep it handy for later.

  2. Typically organizations will have one MASTER AWS ACCOUNT under which they will setup multiple Users, Groups, Permission Sets and AWS Accounts. So it’s likely you will need to create the SSO Role and Policy creation only once against your MASTER AWS ACCOUNT.

  3. Currently, the IAM Role and Policy creation to bring in SSO Users, Groups and Permission Sets is optional in Zilla.

 

Things to keep handy

...

For IAM Users and Groups: Copy the Role ARN. For eg: arn:aws:iam::<YOUR_AWS_ACCOUNT_ID>:role/Zilla-IAM-Reader-Role created above.

...

For SSO Users and Groups:, you need to keep the following things handy:

  1. Copy the SSO Role ARN of your Master AWS Account. For eg: arn:aws:iam::<YOUR_AWS_SSO_MASTER_ACCOUNT_ID>:role/Zilla-SSO-Reader-Role created above

  2. ARN of the SSO Instance

  3. Identity Store Id of the Identity Provider of SSO Instance

  4. 12 digit Account ID of the AWS Instance for which you want to bring in SSO Users and Groups

  5. AWS Region under which AWS SSO is setup

  6. AWS SCIM Endpoint

  7. AWS SCIM Access Token

Here are the instructions to get the above details:

...

In the search bar at the top, search for AWS SSO and click on the search result called AWS Single Sign-On as shown below.

...

 

...

You will land on the AWS SSO dashboard.

...

 

...

Click the Settings option on the left menu.

...

 

...

Copy the ARN of the SSO Instance and keep it handy. It will look something like this: arn:aws:sso:::instance/ssoins-<SOME_ALPHANUMERIC_ID>.

...

Also, copy the Identity store ID. It will look something like this: d-<SOME_NUMBERS> .

...

Next, click the AWS accounts option from the left menu.

...

 

...

Copy the 12 digit Account Id of the AWS Account whose Permission sets assignments you want to get.

...

Copy the region in which the AWS SSO Organization has been created. For eg: us-east-1.

...

 

...

Go back to Settings to get the Automatic Provisioning (SCIM) details

...

You can only get the SCIM details if Automatic Provisioning is enabled. You can choose to keep Automatic Provisioning disabled or choose to enable at this point. If Automatic Provisioning is disabled, Zilla won’t be able to track the Active Status of a user.

...

To enable Automatic Provisioning, click Enable automatic provisioning.

...

Copy the SCIM Endpoint and keep it handy.

Click Show token and copy the token. Note that this token is available to be copied only once.

...

sets into an AWS app instance in Zilla, this AWS app instance must have AWS Organization app instance as Parent Application.

...

Follow the steps here for AWS Organization Sync for this AWS app instance’s Parent Application.

Info

Notes:

  1. “Discover Child Apps” configuration should be set to “Yes” in the AWS Organizations App which is parent of this AWS app.

  2. “Sync AWS SSO accounts in Child AWS Apps” configuration should also be set to “Yes” in the AWS Organizations parent App.

  3. The AWS Organizations App adds SSO configurations to its child AWS apps. These SSO configurations are hidden in the child AWS apps.

  4. The configurations of the discovered AWS child Apps should not be edited manually. If the configurations are edited manually, it removes the hidden SSO configurations.

  5. To restore the hidden SSO configurations to this child AWS app, sync the Parent AWS Organizations App.

Refer AWS - Hidden SSO configurations for more details.

Info

 Notes:
To sync all S3 buckets data, Zilla requires the following permissions to be allowed in the Zilla IAM Reader role:

  • ListAllMyBuckets

  • GetBucketLocation

  • GetBucketPolicy

  • GetBucketAcl

  • GetBucketPublicAccessBlock

  • GetBucketOwnershipControls

  • GetBucketPolicyStatus

  • GetEncryptionConfiguration

  • ListAccessPoints

  • GetAccessPoint

  • GetAccessPointPolicy

  • GetAccessPointPolicyStatus

Set up AWS Application Integration on Zilla

  1. Login to Zilla at http://app.zillasecurity.com/.

    Image Modified

     

  2. Once you are signed in, you will land on the Applications page.

    Image Modified

     

  3. Click Add Application. You will see a library of all applications listed which are supported by Zilla.

    Image Modified

     

  4. Type “aws” into the search bar to filter the results.

    Image Modified

     

  5. Click on Add to Applications next to the Amazon Web Services entry. You will see a dialog box appear.

...

  1. All the fields are optional. Click Add to Applications.

    Image Added
  2. You will be redirected back to the Applications page and you will see the Amazon Web Services entry included in the list.

    Image Modified

     

...

  1. Click the application instance to configure its integration.

...

  1. Image Added

  2. Click

...

  1. Sync

...

  1. now in the top right corner. You will see a dialog box appear.

    Image Modified
  2. Click

...

  1. the

...

  1. slider under API Integration to enable

...

  1. .

...

  1. Image Added

  2. Enter the Role ARN. For example: arn:aws:iam::<YOUR_AWS_ACCOUNT_ID>:role/Zilla-IAM-Reader-Role created above. and click Next.

    Image Added

  3. Click Next again.

    Image Modified

     

  4. Your sync will begin. Once it completes, you will see the below message.

    Image Modified

     

  5. Click Done . You will then see a message like this if the sync completed successfully.

    Image Modified
  6. You can close the message dialog and navigate to the Accounts tab to the IAM Users from your AWS account.

    Image Modified

     

  7. Next, click the Permissions tab to browse the

...

  1. permissions assigned to each user.

    Image Modified

  2. Click the Resources tab to browse the AWS resources (S3 Buckets and S3 Access points).

    Image Added

  3. Click the Profile tab to browse the AWS account Security Settings.

...

Include Page
Integrations Footer
Integrations Footer