fix: Readme and troubleshooting section (#530)

* fix: readme

* fix: path for GitHub Action

Author: maxday

.github/workflows/aws-lambda-java-profiler.yml

@@ -4,12 +4,12 @@ on:
   pull_request:
     branches: [ '*' ]
     paths:
-      - 'aws-lambda-java-profiler/**'
+      - 'experimental/aws-lambda-java-profiler/**'
       - '.github/workflows/aws-lambda-java-profiler.yml'
   push:
     branches: ['*']
     paths:
-      - 'aws-lambda-java-profiler/**'
+      - 'experimental/aws-lambda-java-profiler/**'
       - '.github/workflows/aws-lambda-java-profiler.yml'
 
 jobs:

experimental/aws-lambda-java-profiler/README.md

@@ -88,6 +88,7 @@ the result to is configurable using an environment variable.
 - Ensure the Lambda function execution role has the necessary permissions to write to the S3 bucket.
 - Verify that the environment variables are set correctly in your Lambda function configuration.
 - Check CloudWatch logs for any error messages from the extension.
+- The profiler extension uses dependencies such as `com.amazonaws:aws-lambda-java-core`, `com.amazonaws:aws-lambda-java-events` and `software.amazon.awssdk:s3`. If you're using the same dependencies in your Lambda function, make sure that the versions match those used by the extension as mismatched versions can lead to compatibility issues.
 
 ## Contributing
 

experimental/aws-lambda-java-profiler/extension/build.gradle

@@ -14,7 +14,7 @@ dependencies {
     implementation 'com.amazonaws:aws-lambda-java-core:1.2.3'
     implementation 'com.amazonaws:aws-lambda-java-events:3.11.5'
     implementation("tools.profiler:async-profiler:3.0")
-    implementation("software.amazon.awssdk:s3:2.28.9") {
+    implementation("software.amazon.awssdk:s3:2.31.2") {
         exclude group: 'software.amazon.awssdk', module: 'netty-nio-client'
     }
 }