Setup inCloud Managed with AWS
Last updated
Last updated
inCloud Managed is one of our setup options, which install our platform's infrastructure in a cloud environment owned by your organization, allowing you to delegate its entire setup, update, and maintenance to groundcover.
Note: inCloud Managed is available exclusively to Enterprise users.
inCloud Managed requires to create an isolated account within your AWS organization, that will be managed by groundcover's control plane and will establish, configure, and maintain the infrastructure and workloads within the account. These include AWS VPC, S3, EKS, LB, etc.
The following sequence diagram provides an overview of the setup process:
inCloud Managed deployment (delegated to groundcover)
Sensor deployment (handled by your organization)
groundcover Managed inCloud can be deployed using one the following configurations:
In line with AWS’s recommended unit of containerization, the default option is to deploy in a dedicated AWS account. This acts as an identity, resources, quota and access management isolation boundary.
We recommend naming the account [groundcover-incloud] and placing the account in OU=Infrastructure/OU=Managed. For additional information please see Establishing your best practice AWS environment (external link to a page on the AWS website).
For customers who prefer using a single account approach, Managed inCloud can also be deployed into an existing account, running alongside existing production workloads in your existing AWS account. To limit access and prevent resource collusion, we implement a “scoping territory” approach using ABAC tags for access control and VPC subnets for network control.
By default, groundcover Managed inCloud deploys as a SaaS solution using ZTNA public, allowing you to deliver telemetry data securely over the public internet.
Prefer private networking is supported with Private Link.
Read more about this option in our Private Network Guide.
To grant our control-plane access to the account, we use AWS’s built-in access federation feature. The following guide will guide you through the steps required to setup this access.
Users on an Enterprise plan (prerequisite for inCloud Managed) have access to a private support channel on Slack for their organization. Use that channel to let us know that you're ready to get started with the inCloud Managed setup. Then, the groundcover team will share your External ID with you.
Log in as a privileged user to the AWS account chosen for deployment
Navigate to IAM -> Roles
Click “Create role”
Trusted entity type: Select “AWS Account”
An AWS account: Check "Another AWS account"; Account ID: 991078109329
Options: Check "Require external ID" and enter your External ID (see Step 1)
Make sure “Require MFA” is unchecked
Click "Next"
In the following screen, do not attach any managed permissions
Click "Next"
Note: AWS can’t verify MFA login in cross-account operational mode. groundcover control-plane is enforcing strict security principals, including MFA.
In this screen, fill in the following details:
Role name: Type groundcover-managed
Description: Optional field, your can write any free text description that can be helpful for you and others to understand this purpose of this role in the future (e.g. “app.groundcover.com control plane access”)
Tags: Type groundcover:access = read. You can also use specify additional workflow-oriented tags
Click "Create role"
Search for the newly created groundcover-managed role (or scroll down the list until you find it) and click on it.
Navigate to the "Trust relationships" screen.
Click "Edit trust policy"
Replace the statement with the following snippet:
Click "Update Policy"
Navigate to "Permissions" tab.
Click "Add permissions" -> "Create inline policy"
Click the “JSON” tab and paste the following policy into the text box:
Click "Next"
Click “Review Policy”
Enter the following Policy name: inline-policy-2.4.2
Click “Create policy”
We create the inline policy to adhere to security best practices (external link to Wikipedia) by limiting access on IAM, EC2 and related services to the bare minimum required for control plane operations including: health monitoring, security patches, auto scaling and version updates.
groundcover Control-Plane is a secure reconciliation controller designed to manage enterprise inCloud infrastructure environments. It is compliant with ISO-27001 and SOC-2 standards.
The control plane can securely access your groundcover-incloud account by using a cross-account IAM role.
Setting up groundcover inCloud does not require access to your production data or workloads, nor does it grant it such access.
To establish the Trust Relationship, please share the following information with groundcover.
Go to IAM > Roles > groundcover-managed > Trust relationships
Verify that the sts:ExternalId is as was provided by groundcover's integration manager
Take note of your ARN number, which you will need to share with us (see What's Next?)
Example:
Using the same Slack channel as in Step 1, share the following information with the groundcover team:
The region where you’d like inCloud to be deployed
Once up and running, we will share our instructions on how to redeploy the eBPF sensor, which will now point the data collected into a public endpoint we will provide for your inCloud. You will get the incloud-values.yaml file from us, which you can use to deploy our sensor on your production workload as follows:
See API Key Secret for additional information.
Data is transmitted to, processed on, and stored in the [groundcover-incloud] managed infrastructure. The mental model is that of a private SaaS solution.
