Documentation
Documentation
Onboarding
GeneralCloud ProviderChoosing a SourceKubernetesCloudwatchEC2
Adding a Destination

After you've selected the desired source, Trink will need some details regarding your account to start collecting or reading logs from it. The required details and information for each source may differ, depending on the source, account needed and etc.

Please read the following guides on the required details for each source:

Kubernetes

Step 1: AWS Account ID and Region

At first, please provide details for your AWS account, including AWS id and region. At this point, you can also select the option to "ignore old logs" which will make the entire process of the onboarding quicker than it would be otherwise.

Step 2: AWS IAM Role Permission

Make sure that you are logged in to your AWS account.\ A pop-up window directing you to AWS should appear after clicking the "Start Deploying" button.

If you are already logged into AWS, the following pop-up should appear:

AWS pop-up

In case you are not logged in - the following will appear, in that case - please sign in with your account.

aws log in

Step 3: Cluster VPC

Select your VPC from the listed options.

kubernetes cluster vpc

Step 4: Peer VPC

At this point, there is not much needed to be done from your end. This is the part where we peer your VPC to trink, and it may take a few moments.

kubernetes peer vpc

Step 5: Execute Deployment Command

Copy and execute the listed commands wither on K8s deployment command OR in Helm, then click "Yes".

kubernetes execute deployment command

Step 6: Cluster Synchronization with Trink

Trink deploys all containers.\ \ Once all these steps are finished - you can see your source in action either on our Discovery Map or Health.

Cloudwatch

Step 1: AWS Account ID and Region

At first, please provide details for your AWS account, including AWS id and region. At this point, you can also select the option to "ignore old logs" which will make the entire process of the onboarding quicker than it would be otherwise.

Step 2: AWS IAM Role Permission

Make sure that you are logged in to your AWS account.

cloudwatch aws iam role permission

A pop-up window directing you to AWS should appear after clicking the "Start Deploying" button.

Step 3: Integrate Cloudwatch Logs

At this point, there is not much needed to be done from your end. This is the part where we connect your Cloudwatch to trink, and it may take a few moments.

Once all these steps are finished - you can see your source in action either on our Discovery Map or Health.

EC2

Step 1: AWS Account ID and Region

At first, please provide details for your AWS account, including AWS id and region. At this point, you can also select the option to "ignore old logs" which will make the entire process of the onboarding quicker than it would be otherwise.

Trink ec2 onboarding

Step 2: AWS IAM Role Permission

Make sure that you are logged in to your AWS account.\ A pop-up window directing you to AWS should appear after clicking the "Start Deploying" button.

Step 3: Cluster VPC

Select your VPC from the listed options.

Step 4: Peer VPC

At this point, there is not much needed to be done from your end. This is the part where we peer your VPC to trink, and it may take a few moments.

Step 5: Execute Deployment Command

Copy and execute the listed commands wither on K8s deployment command OR in Helm, then click "Yes".

Step 6: Cluster Synchronization with Trink

Trink deploys all containers.\ \ Once all these steps are finished - you can see your source in action either on our Discovery Map or Health.

Get In Touch

Contact us for more information