Merge pull request #453 from bjrara/doc

Update doc layout

Author: pxaws

deployment-template/eks/eks-sidecar.yaml …emplate/eks/otel-cloudwatch-sidecar.yamldeployment-template/eks/eks-sidecar.yaml renamed to deployment-template/eks/otel-cloudwatch-sidecar.yaml deployment-template/eks/eks-sidecar.yaml renamed to deployment-template/eks/otel-cloudwatch-sidecar.yaml

@@ -16,12 +16,12 @@ export AWS_REGION=<aws-region>
 ```
 
 2. Deploy a standalone aws-otel-collector application. An example config template can be
-   found [here](../../deployment-template/eks/standalone-otel-eks-deployment.yaml).
+   found [here](../../deployment-template/eks/otel-container-insights-prometheus.yaml).
     * Replace `{{region}}` with the name of the region where the logs are published (e.g. `us-west-2`).
     * Replace `{{cluster_name}}` with the actual eks cluster name.
 
 ```bash
-cat standalone-otel-eks-deployment.yaml |
+cat otel-container-insights-prometheus.yaml |
 sed "s/{{region}}/$AWS_REGION/g" | 
 sed "s/{{cluster_name}}/$CLUSTER_NAME/g" |
 kubectl apply -f - 

…/eks/standalone-otel-eks-deployment.yaml …/otel-container-insights-prometheus.yamldeployment-template/eks/standalone-otel-eks-deployment.yaml renamed to deployment-template/eks/otel-container-insights-prometheus.yaml deployment-template/eks/standalone-otel-eks-deployment.yaml renamed to deployment-template/eks/otel-container-insights-prometheus.yaml

@@ -39,7 +39,7 @@ docker push $AWS_ACCOUNT_ID.dkr.ecr.$AWS_REGION.amazonaws.com/prometheus-sample-
 
 ```bash
 SAMPLE_TRAFFIC_NAMESPACE=javajmx-sample
-curl https://raw.githubusercontent.com/aws-observability/aws-otel-collector/main/examples/eks/eks-containerinsight-javajmx-sample.yaml | 
+curl https://raw.githubusercontent.com/aws-observability/aws-otel-test-framework/terraform/sample-apps/jmx/examples/prometheus-metrics-sample.yaml | 
 sed "s/{{aws_account_id}}/$AWS_ACCOUNT_ID/g" |
 sed "s/{{region}}/$AWS_REGION/g" |
 sed "s/{{namespace}}/$SAMPLE_TRAFFIC_NAMESPACE/g" | 

docs/developers/container-insight-install-aoc.md

@@ -52,11 +52,11 @@ This example will introduce how to use AWS-OTel-Collector to send application tr
 The easiest way to deploy AWSOTelCollector on Amazon ECS is to run it as a sidecar, defining it in the same task definition as your application.
 
 **ECS Fargate Template**  
-You can find ECS Fargate AWSOTelCollector [Installing template](../../examples/ecs/ecs-fargate-sidecar.json). Instructions for setting up a service in your ECS cluster using Fargate can be found [here](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/getting-started-fargate.html).
+You can find ECS Fargate AWSOTelCollector [Installing template](../../examples/ecs/aws-cloudwatch/ecs-fargate-sidecar.json). Instructions for setting up a service in your ECS cluster using Fargate can be found [here](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/getting-started-fargate.html).
 
 **ECS EC2 Template**  
 Another example is installing AWSOTelCollector on ECS EC2 instance as sidecar to send telemetry data.
-You can find ECS EC2 AWSOTelCollector [Installing template](../../examples/ecs/ecs-ec2-sidecar.json). Instructions for setting up a service in your ECS cluster using EC2 can be found [here](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/getting-started-ecs-ec2.html).
+You can find ECS EC2 AWSOTelCollector [Installing template](../../examples/ecs/aws-cloudwatch/ecs-ec2-sidecar.json). Instructions for setting up a service in your ECS cluster using EC2 can be found [here](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/getting-started-ecs-ec2.html).
 
 **Configure The Task Definition**  
 The two ECS task definition templates are provided to run AWS-OTel-Collector as sidecar to send application metrics and traces on Amazon ECS. Notice that in the task definition templates we provided, you have to replace `{{region}}` with the region your want to send the data to. Fill `{{ecsTaskRoleArn}}` and `{{ecsExecutionRoleArn}}` with the IAM role (`ECS-AWSOTel`) you created above.

docs/developers/container-insights-eks-jmx.md

@@ -55,11 +55,11 @@ export CLUSTER_NAME=<eks-cluster-name>
 export AWS_REGION=<aws-region>
 ```
 
-3. Deploy the application. An example config template can be found [here](../../deployment-template/eks/eks-sidecar.yaml).
+3. Deploy the application. An example config template can be found [here](../../deployment-template/eks/otel-cloudwatch-sidecar.yaml).
 * Replace `{{region}}` with the name of the region where the logs are published (e.g. `us-west-2`).
 * Replace `{{cluster_name}}` with the actual eks cluster name.
 ```bash
-cat eks-sidecar.yaml |
+cat otel-cloudwatch-sidecar.yaml |
 sed "s/{{region}}/$AWS_REGION/g" | 
 sed "s/{{cluster_name}}/$CLUSTER_NAME/g" |
 kubectl apply -f - 

docs/developers/ecs-demo.md

@@ -23,7 +23,7 @@ services:
       # - AWS_PROFILE=myprofile
 
     volumes:
-      - ../examples/config-test.yaml:/etc/otel-agent-config.yaml
+      - ./config-test.yaml:/etc/otel-agent-config.yaml
       - ~/.aws:/root/.aws
     ports:
       - "1777:1777"   # pprof extension