Adding troubleshooting page

Author: leandrodamascena

examples/build_recipes/troubleshooting/fix-layer-compatibility.sh

@@ -5,7 +5,8 @@
 # 2. Verify layer compatibility
 aws lambda get-layer-version \
     --layer-name AWSLambdaPowertoolsPythonV3-python313-x86_64 \
-    --version-number 22
+    --version-number 22 \
+    --region-name {REGION}
 
 # 3. Avoid version conflicts
 # Don't include Powertools for AWS in deployment package if using layer

examples/build_recipes/troubleshooting/optimize-cold-starts.sh

@@ -2,12 +2,13 @@
 # 1. Optimize package size (see above)
 
 # 2. Use public Powertools for AWS layer
-# Layer ARN: arn:aws:lambda:region:017000801446:layer:AWSLambdaPowertoolsPythonV3-python313-x86_64:1
+# Layer ARN: arn:aws:lambda:{REGION}:017000801446:layer:AWSLambdaPowertoolsPythonV3-python313-x86_64:1
 
 # 3. Enable provisioned concurrency for critical functions
 aws lambda put-provisioned-concurrency-config \
     --function-name my-function \
-    --provisioned-concurrency-config ProvisionedConcurrencyCount=10
+    --provisioned-concurrency-config ProvisionedConcurrencyCount=10 \
+    --region-name {REGION}
 
 # 4. Minimize imports in handler
 # Import only what you need, avoid heavy imports at module level