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
*Issue description:*
This is a part of four series of PR to remove public endpoints for E2E
testing to comply with security best practices.
- [Deploy Traffic
Generator](#140)
- [Remove Public Endpoints from
K8s](#141)
- [Remove Public Endpoints from
EKS](#139)
- [Remove Public Endpoints from
EC2](#144)
Since the public endpoints will be removed, we are unable to call the
sample app APIs directly from the workflow. Therefore, we will be using
a traffic generator that is installed alongside the sample app
applications to call the APIs
This PR will be responsible for creating the traffic generator as well
as saving them to private ECR and S3 bucket.
The private ECR will be used by EKS and K8s platform while the S3 bucket
will be used by EC2 Platforms.
The traffic generator will first wait while it receives the appropriate
environment variable. Once that is received, it will ping the API
endpoints every minute. There is some additional logic depending on
which canary it is running for.
Test run:
https://github.com/aws-observability/aws-application-signals-test-framework/actions/runs/10118562925
Test run after comment:
https://github.com/aws-observability/aws-application-signals-test-framework/actions/runs/10148623963
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.
0 commit comments