AWS
Review AWS Roles and Permissions
There are two identities involved in the onboarding process:
- Installer: Either a User or Role that will be used to perform the onboarding. Sysdig does not have access to this identity.
- Sysdig: A set of IAM Roles created during onboarding with specific, less permissive permissions attached. Sysdig will be given access to these Roles.
Prerequisites
- Sysdig Secure SaaS with Admin permissions.
- Terraform v1.3.1+ installed or access to CloudFormation.
- Access to a User or Role with the permissions required to install.
Permissions Required to Install
The Installer must have at least the following roles assigned:
- For Single Account installations:
- IAMFullAccess: This policy is required to create IAM Roles and associated permissions.
- For Organization installations:
- IAMFullAccess: This policy is required to create IAM Roles and associated permissions.
- AWSOrganizationsReadOnlyAccess: This policy is required to list Accounts and OUIDs in your Organization.
- AWSCloudFormationFullAccess: This policy is required to create a CloudFormation StackSet that creates IAM roles in each Account in your Organization.
Permissions Granted to Sysdig
The installation creates two IAM Roles that Sysdig can access. These Roles have the following permissions attached:
- A Role named sysdig-secure-onboarding-XXXX used to manage the base integration with Sysdig
- AWSAccountManagementReadOnlyAccess
- (Organizational install) AWSOrganizationsReadOnlyAccess
- A role named sysdig-secure-posture-XXXX used to collect an Inventory of cloud resources, and perform CSPM
- SecurityAudit
- A Custom IAM Policy containing the following permissions:
account:GetContactInformation
elasticfilesystem:DescribeAccessPoints
lambda:GetFunction
lambda:GetRuntimeManagementConfig
macie2:ListClassificationJobs
waf-regional:ListRuleGroups
waf-regional:ListRules
Prepare Your Environment
1. Configure Installation Permissions
Ensure the User or Role you log in to AWS with has the necessary permissions to install. You can:
- Use an existing User or Role who meets the permissions requirements.
- Create a new User or Role and set up permissions.
- Add permissions to an existing User or Role.
- Log into AWS and navigate to IAM>Users or IAM>Roles as applicable
- Open the details of the User or Role that will be used to onboard, and select Permissions
- Under Permissions policies, verify and add necessary policies.
2. Authenticate and Configure Terraform
If you are installing using CloudFormation, skip to step 3.
Configure Terraform to use AWS Credentials for the User or Role from step 1. A simple way is to use the following environment variables:
AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY
AWS_REGION
For alternative ways to authenticate Terraform, see the AWS Terraform Provider documentation.
3. Collect your Account Details
Account ID
- Sign in to the AWS Console. For an Organizational install, ensure you sign in to the Management account of your Organization.
- Expand the dropdown in the top right corner of your screen and copy your Account ID.
(Organizational install) Organization Unit IDs
By default, your entire AWS Organization will be onboarded. If you would like to restrict the onboarding to a subset of your Organization, you can target specific OUIDs.
- Sign in to the AWS Console.
- Expand the dropdown in the top right corner of your screen and select Organization.
- Note down the list of OUIDs that you would like to onboard. Note: accounts are added recursively below selected OUs, even if there are child OUs within them.
Connect AWS using the Wizard
- Log into Sysdig Secure
- Select Integrations > Cloud Accounts > AWS, and select Add AWS Account in the top right corner.
- Choose whether to connect your AWS Organization or Single Account.
This enables CSPM and lets you onboard Vulnerability Management, CIEM and CDR after completing.
Terraform
Organization
- Enter your:
- Management Account ID: The Account ID of your Organization’s Management Account.
- Primary Region: The region in which to create regional resources such as StackSets
- (optional) OUIDs: To onboard a subset of Accounts, enter the OUIDs in a comma separated list. Leave this field blank to onboard your entire Organization
- Generate and apply the Terraform code:
- Create a
main.tf
file. - Copy the snippet provided into the file.
- Run the command:
terraform init && terraform apply
.
- Create a
After deployment, your Accounts will appear on the Cloud Accounts page.
Single Account
- Enter your:
- Account ID: The Account ID of account you wish to onboard.
- Generate and apply the Terraform code:
- Create a
main.tf
file. - Copy the snippet provided into the file.
- Run the command:
terraform init && terraform apply
.
- Create a
After deployment, your Account will appear on the Cloud Accounts page.
CloudFormation Templates
Log in to the AWS Account where you want to deploy. For Organizational installs, log into your Organization’s Management Account.
Enter your:
- Account ID: The Account ID of account you wish to onboard. For Organizational installs, the Account ID of your Organization’s Management Account.
- (For Organizational) OUIDs: To onboard a subset of Accounts, enter the OUIDs in a comma separated list. Leave this field blank to onboard your entire Organizationinformation such as the requested account ID, regions and units in the Wizard screen and
Click Launch Stack.
You are redirected to the AWS Console. Follow the prompts to create the CloudFormation Stack.
Be sure to check the Acknowledgements in the AWS Capabilities section in the AWS Console.
When complete, return to the Sysdig Wizard and click Complete. Accounts will not appear in the Cloud Accounts page until this button is clicked.
Validate
To validate the successful connection of your AWS environment
In Sysdig Secure, select Integrations > Cloud Accounts > AWS.
The Status column shows the overall connection status (
Connected/Partial Error/Error/Unknown
)Select the desired account to review the individual services in the detail drawer.
See also: Cloud Accounts - AWS, Add New Features - AWS
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.