This the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

    Deploy Sysdig Secure for cloud on AWS

    Review the offering description on Sysdig Secure for cloud, if needed.

    Choose whether you will deploy with a CloudFormation Template (CFT) or Terraform file.

    Onboarding a Single Account using a CFT

    Each of the features can be enabled from a single CloudFormation Template (CFT) from the AWS Console.

    Deploying the CFT will add the default cloud policies and rules to any existing Sysdig Secure installations.

    Prerequisites

    • A Sysdig Secure SaaS account

    • An AWS account and AWS services you would like to connect to Sysdig, with appropriate permissions to deploy a CFT.

    Steps

    1. Log in to your AWS Console and confirm that you are in the account and AWS region that you want to secure using Sysdig Secure for cloud.

    2. Log in to Sysdig Secure as Admin and select Get Started > Connect your Cloud account. Choose the AWS(CloudFormation) tab.

    3. Click Launch Stack.

      The AWS Console opens, at the CloudFormation > Stacks > Quick Create page. The Sysdig CloudFormation template is pre-loaded.

      Confirm that you are logged in the AWS account and region where you want to deploy the Sysdig Template.

    4. Provide a Stack name or accept the default.

    5. Fill in the Parameters:

      Sysdig Settings

      • Sysdig Secure Endpoint:

        Default (US-East): https://secure.sysdig.com. If your Sysdig Secure platform is installed in another region, use that endpoint.

        US West: https://us2.app.sysdig.com

        European Union: https://eu1.app.sysdig.com

      • Sysdig Secure API Token: See Retrieve the Sysdig API Token to find yours.

      Modules to Deploy: Choose any or all.

      • CSPM/Compliance: Deploys the CIS AWS Benchmarks in Sysdig’s Compliance module.

      • Threat detection using CloudTrail: Deploys everything needed to detect threats based on CloudTrail events.

      • ECR Image Registry Scanning: Integrates container registry scanning for AWS ECR.

      • Fargate Image Scanning: Integrates image scanning on any any container image deployed on a serverless Fargate task (in ECS).

      Existing Infrastructure: Leave all three entries blank to have a cluster, VPC, and subnet created automatically. Otherwise, you can provide existing:

      • ECS Cluster Name

      • VPC ID

      • Private subnet ID(s)

    6. Confirm the Capabilities required to deploy:

      • Check “I acknowledge that AWS CloudFormation might create IAM resources with custom names."

      • Check “I acknowledge that AWS CloudFormation might require the following capability: CAPABILITY_AUTO_EXPAND”

    7. Click Create Stack.

      In the AWS Console, the main stack and associated substacks will show “CREATE_IN_PROGRESS”. Refresh the status to see “CREATE_COMPLETE” for all. There is a delay of 5-10 minutes for events to be sent from CloudTrail, but no event is lost.

      A success message also appears in the Sysdig Secure Get Started page.

    Onboarding Using Terraform

    Terraform-based install instructions differ depending on what type of AWS account you are using.

    At this time, the options include:

    • Install for a single AWS account
    • Install for an organizational/management account

    For Single/Member Account

    The default code provided in the Get Started page of Sysdig Secure is pre-populated with your Secure API token and will automatically install threat detection with CloudTrail, AWS benchmarks, and container registry and image scanning.

    Prerequisites

    Permissions

    Steps

    1. Log in to Sysdig Secure as Admin and select Get Started > Connect your Cloud account. Choose the AWS (Terraform) tab.

    2. Copy the code snippet under Single Account and paste it in the terminal of your local machine. It should be pre-configured with your Sysdig API token.

    3. Then run:

      $ terraform init
      

      When complete, run:

      $ terraform apply
      

      which will present the changes to be made, ask you to confirm them, then make the changes.

    4. Confirm the Services are Working

      Check Troubleshooting in case of permissions or account conflict errors.

    For Organizational/Management Account

    For organizational accounts, the default code provided in the Get Started page of Sysdig Secure is pre-populated with your Secure API token and will automatically install threat detection with CloudTrail (only).

    Prerequisites

    • Have Terraform installed on the local machine.

    • A Sysdig Secure SaaS account

    • A Sysdig Secure for Cloud organizational member account ID.

      We recommend creating a unique member account for Sysdig Secure for cloud.

    Permissions

    • Sysdig Secure administrator permissions

    • AWS permissions:

      • An existing AWS account as the organization master account with the Organizational CloudTrail service enabled.

      • AWS profile credentials configuration of the master account of the organization

        You must also have sufficient permissions for the IAM user or role in the management account to successfully create an organization trail.

        Sysdig provides an IAM policy containing the required permissions.

    Steps

    1. Log in to Sysdig Secure as Admin and select Get Started > Connect your Cloud account. Choose the AWS (Terraform) tab.

    2. Copy the code snippet under Organizational Account and paste it in the terminal of your local machine. It should be pre-configured with your Sysdig API token.

    3. Then run:

      $ terraform init
      

      When complete, run:

      $ terraform apply
      

      which will present the changes to be made, ask you to confirm them, then make the changes.

    4. Confirm the Services are Working

      Check Troubleshooting in case of permissions or account conflict errors.

    Soon, this option will be expanded to include all the features currently in the single account option, as well as the ability to easily add multiple member accounts.

    Customizing the Install

    Both the Single Account and Organizational Account code examples are configured with sensible defaults for the underlying inputs. But if desired, you can edit the region, module enablement, and other Inputs. See details for:

    Resources Created by Each Module

    • Cloud-bench

      • aws_iam_role

      • aws_iam_role_policy_attachment

      • sysdig_secure_benchmark_task

      • sysdig_secure_cloud_account

    • Cloud-connector

      • aws_cloudwatch_log_stream

      • aws_ecs_service

      • aws_ecs_task_definition

      • aws_iam_role

      • aws_iam_role_policy

      • aws_s3_bucket

      • aws_s3_bucket_object

      • aws_s3_bucket_public_access_block

      • aws_security_group

      • aws_sns_topic_subscription

      • aws_sqs_queue

      • aws_sqs_queue_policy

    • Cloud-scanning

      • aws_cloudwatch_log_group

      • aws_cloudwatch_log_stream

      • aws_ecs_service

      • aws_ecs_task_definition

      • aws_iam_role

      • aws_iam_role_policy

      • aws_security_group

      • aws_sns_topic_subscription

      • aws_sqs_queue

      • aws_sqs_queue_policy

    If cloud-connector or cloud-scanning is installed, these additional modules will be installed:

    • resource-group

      • aws_resourcegroups_group
    • cloudtrail

      • aws_cloudtrail

      • aws_kms_alias

      • aws_kms_key

      • aws_s3_bucket

      • aws_s3_bucket_policy

      • aws_s3_bucket_public_access_block

      • aws_sns_topic

      • aws_sns_topic_policy

    • ssm

      • aws_ssm_parameter
    • ecs-fargate-cluster

      • aws_ecs_cluster

    If cloud-scanning is installed, these additional modules will be installed:

    • codebuild

      • aws_cloudwatch_log_group

      • aws_codebuild_project

      • aws_iam_role

      • aws_iam_role_policy

    Troubleshooting

    1. Resolve 409 Conflict Error

    This error may occur if the specified cloud account has already been onboarded to Sysdig.

    Solution:

    The cloud account can be imported into Terraform by running: 

    terraform import module.cloud_bench.sysdig_secure_cloud_account.cloud_account CLOUD_ACCOUNT_ID

    2. Resolve Permissions Error/Access Denied

    This error may occur if your current AWS authentication session does not have the required permissions to create certain resources.

    Solution:

    Ensure you are authenticated to AWS using a user or role with the required permissions.

    Confirm the Services are Working

    Log in to Sysdig Secure and check that each module you deployed is functioning. It may take 10 minutes or so for events to be collected and displayed.

    Check Overall Connection Status

    • Data Sources: Select Data Sources from the User menu to see all connected cloud accounts.

    • Subscription: Select Settings > Subscription to see an overview of your account activity, including cloud accounts.

    • Insights: Check that Insights have been added to your navigation bar. View activity on the Cloud Account, Cloud User, or Composite insight views.

    Check Threat Detection

    • Policies: Check Policies > Runtime Policies and confirm that the AWS Best Practices policy is enabled. This consists of the most-frequently-recommended rules for AWS and CloudTrail. You can customize it by creating a new policy of the AWS CloudTrail type.

    • Events: In the Events feed, search ‘cloud’ to show events from AWS CloudTrail.

    • Force an event: In case you want to manually create an event, choose one of the rules contained in the AWS Best Practices policy and execute it in your AWS account.
      ex.: Create a S3 Bucket with Public Access Blocked. Make it public to prompt the event.
      Remember that in case you add new rules to the policy you need to give it time to propagate the changes.

    Check CSPM/AWS Benchmarks

    • Compliance: Select Compliance and see that AWS Foundations Benchmark is installed.

    • Review the benchmark results and confirm the account, region and date added.

    Check Scanning for ECR and Fargate

    • Scan Results: CheckImage Scanning > Scan Resultsand choose the Origins drop-down.

      Confirm that AWS Registry and/or AWS Fargate are listed.

    • Filter by the desired origin and review scan results.

    • Force an event: Upload an image to a repository on your Elastic Container Registry (ECR). Follow View push commands button guide provided by AWS.

    See Also