You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, the idea is similar to the Cloud Export deployments with Ansible, we would extend the capabilities to support synthetics testing.
In the Kentik Portal, is a newly provisioned workflow for Cloud Performance, which layers together flows from AWS Cloud with the capability of provisioning synthetic tests from VPC over [VPN or Direct Connect] towards on prem resources.
Automation with ansible could facilitate implementation (deployment / installation) of Kentik ksynth agents:
in specific VPC resources in AWS (be prepared for rinse repeat operations for Azure, then other clouds)
in on prem facilities (campus, branch, data center)
Then deploy tests evaluating paths to/from cloud resources, to specific physical endpoints (campus, branch, data center)
Context (from Jira comments)
Comment 1
Yes, the idea is similar to the Cloud Export deployments with Ansible, we would extend the capabilities to support synthetics testing.
In the Kentik Portal, is a newly provisioned workflow for Cloud Performance, which layers together flows from AWS Cloud with the capability of provisioning synthetic tests from VPC over [VPN or Direct Connect] towards on prem resources.
Automation with ansible could facilitate implementation (deployment / installation) of Kentik ksynth agents:
Then deploy tests evaluating paths to/from cloud resources, to specific physical endpoints (campus, branch, data center)
Comment 2
I am thinking of launching an ec2 ARM instance in the specific VPC / Subnet, with appropriate security group and NACL, to provision access across to on prem resources (VPN, Direct Connect, etc)
https://docs.aws.amazon.com/cli/latest/userguide/cli-services-ec2-instances.html#launching-instances
With the launch of the EC2 instance, there is a user data section, where we can include deployment of ksynth, and provide the right CID, token, etc
With the newly installed EC2, with the ksynth, we can instantiate more ksynth tests (which is the ultimate goal).
The text was updated successfully, but these errors were encountered: