EDH - Manual IAM Setup Option (AWS)

Detailed Instructions for a Manual IAM Setup Approach to AWS Event-Driven Harvesting

This page includes step-by-step instruction to complete the InsightCloudSec setup for Event-Driven Harvesting (EDH) using an approach that will not automatically provision IAM resources; however, it will set up your CloudWatch resources.

  • You will be required to manually create the Eventbus role/policy. For customers that do not want to use InsightCloudSec's exact paths or names for the role/policy, we will work with you on alternatives.

For questions on this specific setup, assistance with this process for AWS GovCloud, or other EDH-related questions, reach out to us through the Customer Support Portal.

For details on other EDH setup options, check out the main Event-Driven Harvesting (AWS) page.

📘

DivvyCloud vs. InsightCloudSec

Some examples, database values, and other items may refer to DivvyCloud vs. InsightCloudSec. The behavior and performance is the same, just ensure that you are consistent in naming your values.

Setup for EDH in AWS

Configure Consumer Account

Consumer accounts are tasked with ingesting events from other accounts and also producing their own events (i.e., consumers are both producers and consumers).

📘

Opt-In Regions

If you are interested in disabling opt-in regions from harvesting, you can include that configuration when you establish the settings within your consumer(s). If you need assistance with this, contact us through the Customer Support Portal.

Refer to additional documentation on Opt-In Regions here.

1. Login to your AWS Console and open the IAM dashboard.

2. Open the "Policies" section and create a new policy using the "JSON" tab to assign to the existing user/role that InsightCloudSec/DivvyCloud uses to access the consumer account.

  • This policy allows the user to read and write the appropriate event data.
  • In this case, our user is 'DivvyCloud-PowerUser' and our policy name is 'DivvyCloud-EDH-Consumer'.

In addition, you can review the AWS IAM Policies for details.

Here is a sample of what the policy looks like:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "events:DeleteRule",
                "events:DescribeRule",
                "events:PutRule",
                "events:PutTargets",
                "events:RemoveTargets"
            ],
            "Resource": "arn:aws:events:*:CONSUMER-ACCT-ID:rule/divvycloud*"
        },
        {
            "Effect": "Allow",
            "Action": "events:PutPermission",
            "Resource": "arn:aws:events:*:CONSUMER-ACCT-ID:event-bus/default"
        },
        {

            "Effect": "Allow",
            "Action": [
                "sqs:CreateQueue",
                "sqs:ListQueues",
                "sqs:ReceiveMessage",
                "sqs:DeleteMessage"
            ],
            "Resource": [
                "arn:aws:sqs:*:CONSUMER-ACCT-ID:divvycloud-event-aggregator-*.fifo"
            ]
        },
        {
            "Action": [
                "organizations:DescribeOrganization"
            ],
            "Effect": "Allow",
            "Resource": "*"
        }
    ]
}

And here is the Create Policy interface in the AWS Console.

2204

Create Policy in AWS

3. Click on the "Review Policy" option to add the Name, Description, and to review the Summary.

  • In this example. we've named our policy 'DivvyCloud-EDH-Consumer' to identify it as the 'consumer' policy.
1274

Verify Consumer Policy

4. Locate your InsightCloudSec/DivvyCloud Power User. Open the permissions tab to attach the newly created consumer policy to your InsightCloudSec/DivvyCloud Power User (e.g., 'DivvyCloud-PowerUser' below).

1721

Attach the EDH Consumer Policy

❗️

Configuring CloudTrail

If you already have at least one CloudTrail enabled with at least Write events being logged, you do not need to create an additional trail for this and can skip to Step 7.*

5. With our consumer policies in place, you will need to configure CloudTrail. In the AWS console, open "Services" --> "CloudTrail."

  • In this example, the trail is named 'DivvyCloud-EDH'.
2796

CloudTrail Dashboard

6. Click on "Trails" --> "Create Trail" and complete the details based on your organization's requirements (e.g., all regions vs. specific, etc.).

1109

Create a New Cloud Trail

7. Navigate to "CloudWatch --> Events --> Event Buses." Click on the "Add permission" button and enable Organization access to default event bus.

1209

Event Bus Permissions

8. If organization permissions do not already exist, add them using your organization ID.

1380

Add Permission to Event Bus

Configure Producer Account

1. Login to your AWS Console and open the IAM dashboard.

2. Open the "Policies" section and create a new policy using the "JSON" tab. This new policy will be assigned to the existing Harvesting user/role that InsightCloudSec uses to access the producer account.

  • This policy allows the InsightCloudSec/DivvyCloud user to write the appropriate event data.
  • In this case, our user is 'DivvyCloud-PowerUser' and our policy name is 'DivvyCloud-EDH-Producer'.
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "events:DeleteRule",
                "events:DescribeRule",
                "events:PutRule",
                "events:PutTargets",
                "events:RemoveTargets"
            ],
            "Resource": "arn:aws:events:*:*:rule/divvycloud-events*"
        },
        {
            "Effect": "Allow",
            "Action": [
                "iam:CreatePolicyVersion",
                "iam:GetPolicy",
                "iam:GetPolicyVersion",
                "iam:GetRole",
                "iam:PassRole"
            ],
            "Resource": [
                "arn:aws:iam::*:policy/service-role/event-driven-harvest/divvycloud-eventbus-policy",
                "arn:aws:iam::*:role/service-role/event-driven-harvest/divvycloud-eventbus-role"
            ]
        },
        {
            "Action": [
                "organizations:DescribeOrganization"
            ],
            "Effect": "Allow",
            "Resource": "*"
        }
    ]
}

3. You will need to manually create a role and policy that grants the consumer access to the producer’s logs. This role/policy will need be to created on every producer account.

🚧

Eventbus Role/Policy Details

During the InsightCloudSec portion of your setup, InsightCloudSec will expect the specified names and paths that are provided in the sample files below; if you modify these, your EDH setup will produce errors and fail.

4. Save the following JSON for use with the the ‘assume-role-policy-document’. Save as ‘edh_role_manual_sts.txt’.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Principal": {"Service": "events.amazonaws.com"},
            "Action": "sts:AssumeRole"
        }
    ]
}

5. Create divvycloud-eventbus-role.

  • Note the sample content below includes the AWS CLI commands required to create this role. We do not recommend using the AWS Console to create this role because of configuration limitations (e.g., you will not be able to specify the path included below).
aws iam create-role --role-name divvycloud-eventbus-role --assume-role-policy-document file:///PATH/TO/FILE/edh_role_manual_sts.txt --path /service-role/event-driven-harvest/
{
    "Role": {
        "Path": "/service-role/event-driven-harvest/",
        "RoleName": "divvycloud-eventbus-role",
        "RoleId": "AROAIYD6PGH3VPCBX4D4Q",
        "Arn": "arn:aws:iam::ACCT-ID-HERE:role/service-role/event-driven-harvest/divvycloud-eventbus-role",
        "CreateDate": "2018-11-02T20:27:37Z",
        "AssumeRolePolicyDocument": {
            "Version": "2012-10-17",
            "Statement": [
                {
                    "Effect": "Allow",
                    "Principal": {
                        "Service": "events.amazonaws.com"
                    },
                    "Action": "sts:AssumeRole"
                }
            ]
        }
    }
}

6. Save the following JSON for use as the ‘policy-document’.

  • Be sure to update the ‘CONSUMER-ACCT-ID’ value with the account ID of the consumer account.
  • Save as ‘edh_role_manual_policy.txt’
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "events:PutEvents"
            ],
            "Resource": [
                "arn:aws:events:*:CONSUMER-ACCT-ID:event-bus/default"
            ],
            "Effect": "Allow"
        }
    ]
}

7. Create divvycloud-eventbus-policy.

aws iam create-policy --policy-name divvycloud-eventbus-policy --policy-document file:///PATH/TO/FILE/edh_role_manual_policy.txt
{
    "Policy": {
        "PolicyName": "divvycloud-eventbus-policy",
        "PolicyId": "ANPAJ52WSKTB7L4W3QXFS",
        "Arn": "arn:aws:iam::CONSUMER-ACCT-ID:policy/divvycloud-eventbus-policy",
        "Path": "/service-role/event-driven-harvest/",
        "DefaultVersionId": "v1",
        "AttachmentCount": 0,
        "IsAttachable": true,
        "CreateDate": "2018-11-02T20:42:27Z",
        "UpdateDate": "2018-11-02T20:42:27Z"
    }
}

8. Attach divvycloud-eventbus-policy to divvycloud-eventbus-role.

aws iam attach-role-policy --role-name divvycloud-eventbus-role --policy-arn arn:aws:iam::ACCT-ID:policy/divvycloud-eventbus-policy

aws iam list-attached-role-policies --role-name divvycloud-eventbus-role
{
    "AttachedPolicies": [
        {
            "PolicyName": "divvycloud-eventbus-policy",
            "PolicyArn": "arn:aws:iam::ACCT-ID:policy/service-role/event-driven-   harvest/divvycloud-eventbus-policy"
        }
    ]
}

9. InsightCloudSec will automatically use the divvycloud-eventbus-role; the role does not need to be associated with ‘DivvyCloud-PowerUser'.

❗️

Enabling CloudTrail

If you already have at least one CloudTrail enabled with at least Write events being logged, you do not need to create an additional trail for this and can skip to the "Setup EDH in InsightCloudSec" section of this page.

10. With your producer policies in place, you can now configure CloudTrail. Navigate to "Services" --> "CloudTrail."

  • In this example, the trail is named ‘DivvyCloud-EDH’.
2796

Configure CloudTrail

11. Click on "Trails" --> "Create Trail" and complete the details based on your organization's requirements (e.g., all regions vs. specific, etc.).

1109

Create CloudTrail

Setup EDH in InsightCloudSec

After completing the AWS configuration, you are now ready to complete the configuration of EDH inside of InsightCloudSec.

1. Navigate to "Cloud --> Clouds" and select "EDH Consumers". Click "EDH Configuration", then click "AWS SQS Consumer".

1600

Event-Driven Harvesting Consumer Configurations

2. Complete this form by selecting the Consumer Account from the drop-down list. You will also need to do the following:

  • Provide the ARN for the SQS.
  • Select the "EventBridge via EventBus" from the Producer Type drop-down menu.
  • Click "Configure". Note: The Consumer will remain in a pending state while setup is in progress.
1383

Add SQS Consumer

❗️

Enabled Note

Do not add producers until the consumer displays as enabled.

5. Click the "EDH Producers" tab, then click "Add Producer."

1381

Add Producer

6. Complete the "Create Auto-Provisioning Producer" form with the details from the AWS setup completed earlier.

1383

Create Auto-Provisioning Producer Form

Note: If you have questions about the policy associated with enabling any options on this form, contact us through the Customer Support Portal.

  • You can choose to "Automatically update enabled resource types to use all resource types." This will provide event support for all future resource types as they become supported by InsightCloudSec(this is recommended).
  • You can also set EDH to "Automatically Provision IAM resources" and "Automatically Provision Cloudwatch resources" (These are enabled be default and we recommend leaving this option enabled as part of the "Fully Automatic" setup.)

7. After adding your producer, it may remain in the pending state for several minutes while setup is in progress. (Note: This will not refresh automatically; you will need to manually reload the browser.)

8. Once the configuration is complete, the producer account’s status will be labeled enabled.

📘

Enabling Producer

If there are any issues enabling your producer, the status will read "error" and you’ll be able to click the read icon to see related errors.

9. If you added a heavily-used account as your producer, you should see events within a minute or so. If not, you can create and delete a test user to generate events.