From dde7cfb37f5bc73887f3ccc28a7240f6666cfe3c Mon Sep 17 00:00:00 2001 From: Tharun K <53267275+tharun634@users.noreply.github.com> Date: Thu, 2 Oct 2025 10:53:36 +0530 Subject: [PATCH 1/2] Update cloud-pods-collaborative-debugging.mdx --- .../cloud-pods-collaborative-debugging.mdx | 25 +++++++++++-------- 1 file changed, 15 insertions(+), 10 deletions(-) diff --git a/src/content/docs/aws/tutorials/cloud-pods-collaborative-debugging.mdx b/src/content/docs/aws/tutorials/cloud-pods-collaborative-debugging.mdx index ea446979..fcfb4a0e 100644 --- a/src/content/docs/aws/tutorials/cloud-pods-collaborative-debugging.mdx +++ b/src/content/docs/aws/tutorials/cloud-pods-collaborative-debugging.mdx @@ -1,5 +1,5 @@ --- -title: "How To: Collaborative AWS local development with LocalStack’s Cloud Pods" +title: "How To: Collaborative AWS local development with LocalStack's Cloud Pods" description: Replicating development environments ensures that all developers, regardless of their local machine configurations or operating systems, work within an environment that closely mirrors production. This consistency helps identify and solve environment-specific issues early in the development cycle, reducing the "it works on my machine" problem where code behaves differently on different developers' machines. services: - iam @@ -123,9 +123,11 @@ resource "aws_iam_policy" "lambda_dynamodb_policy" { Bob has mistakenly used `dynamodb:Scan` and `dynamodb:Query`, but missed adding the `dynamodb:GetItem` action to the policy document above. +## Test + ### Reproducing the issue locally -Let’s test out the current state of the application. +Let's test out the current state of the application. The Terraform configuration file outputs the REST API ID of the API Gateway. We can capture that value and use it further to invoke the **`add-product`** Lambda: @@ -199,7 +201,7 @@ Services: sts,iam,apigateway,dynamodb,lambda,s3,cloudwatch,logs LocalStack provides a remote storage backend that can be used to store the state of your application and share it with your team members. -The Cloud Pods CLI is included in the LocalStack CLI installation, so there’s no need for additional plugins to begin using it. +The Cloud Pods CLI is included in the LocalStack CLI installation, so there's no need for additional plugins to begin using it. The `LOCALSTACK_AUTH_TOKEN` needs to be set as an environment variable. Additionally, there are other commands for managing Cloud Pods included in the CLI: @@ -249,7 +251,7 @@ involved, meaning that the Lambda logs are still in the CloudWatch log groups. ![CloudWatch Logs](/images/aws/cloudwatch-logs.png) -By spotting the error message, there’s an instant starting point for checking the source of the problem. +By spotting the error message, there's an instant starting point for checking the source of the problem. The error message displayed in the logs is very specific: `"Error: User: arn:aws:sts::000000000000:assumed-role/productRole/get-product is not authorized to perform: dynamodb:GetItem on resource: arn:aws:dynamodb:us-east-1:000000000000:table/Products because no identity-based policy allows the dynamodb:GetItem action (Service: DynamoDb, Status Code: 400, Request ID: d50e9dad-a01a-4860-8c21-e844a930ba7d)"` @@ -335,12 +337,15 @@ The Cloud Pods command-line interface enables users to manage these remotes with ## Conclusion -Cloud Pods play a crucial role in team collaboration, significantly speeding up development processes. -The multiple and -versatile options for remote storage can support different business requirements for companies that prefer using the -environments they control. -Cloud Pods are not just for teamwork; they also excel in other areas, such as creating -resources in Continuous Integration (CI) for ultra-fast testing pipelines. +Cloud Pods play a crucial role in team collaboration, significantly speeding up development processes. The multiple and versatile options for remote storage can support different business requirements for companies that prefer using the environments they control. Cloud Pods are not just for teamwork; they also excel in other areas, such as creating resources in Continuous Integration (CI) for ultra-fast testing pipelines. + +This tutorial demonstrated how Cloud Pods enable seamless collaboration between team members by: +- Capturing exact environment states for easy sharing +- Providing immediate access to service data and logs for debugging +- Maintaining consistency across different developer machines +- Supporting multiple storage backends for compliance needs + +The workflow from Bob capturing the problematic state, to Alice debugging and fixing it, to Carol using the stable version for testing showcases how Cloud Pods streamline development cycles and eliminate environment-specific issues. ## Additional resources From c127161b19deb5ae329dfd23cd21ac283b8d2cab Mon Sep 17 00:00:00 2001 From: Quetzalli Date: Fri, 3 Oct 2025 06:01:19 -0700 Subject: [PATCH 2/2] Apply suggestions from code review --- .../docs/aws/tutorials/cloud-pods-collaborative-debugging.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/aws/tutorials/cloud-pods-collaborative-debugging.mdx b/src/content/docs/aws/tutorials/cloud-pods-collaborative-debugging.mdx index fcfb4a0e..147659ad 100644 --- a/src/content/docs/aws/tutorials/cloud-pods-collaborative-debugging.mdx +++ b/src/content/docs/aws/tutorials/cloud-pods-collaborative-debugging.mdx @@ -123,7 +123,7 @@ resource "aws_iam_policy" "lambda_dynamodb_policy" { Bob has mistakenly used `dynamodb:Scan` and `dynamodb:Query`, but missed adding the `dynamodb:GetItem` action to the policy document above. -## Test +## Testing the application ### Reproducing the issue locally