Payment Service Investigation

[sunkavar]

@awsapm my payment service is having lot of errors, can you help me investigate the issue?

[github-actions]

🎯 Application observability for AWS Investigation Complete

Investigation completed successfully! Here are the results:

---

Critical Infrastructure Issues Identified:

• Missing SQS Queue: 79 errors from QueueDoesNotExistException - the audit-jobs queue doesn't exist
• Missing DynamoDB Table: 28 errors from ResourceNotFoundException - PetClinicPayment table not found
• High Latency: Discovery server registration taking 487ms (should be <100ms)

Root Cause Analysis:

• Infrastructure Gap: The payment service expects AWS resources (SQS queue + DynamoDB table) that aren't automatically created during EKS deployment
• Service Account Permissions: While the service account has DynamoDB/SQS permissions, the actual resources are missing
• Auto-Creation Logic: The service tries to create the DynamoDB table but fails for SQS queue creation

Immediate Actions Required:

• Create SQS Queue: aws sqs create-queue --queue-name audit-jobs --region us-east-1
• Verify DynamoDB: The service should auto-create PetClinicPayment table, but may need manual creation if permissions are insufficient
• Check Service Account: Ensure visits-service-account has proper IAM policies attached

Quick Fix Commands:
bash

Create missing SQS queue

aws sqs create-queue --queue-name audit-jobs --region us-east-1

Restart payment service to retry table creation

kubectl rollout restart deployment/payment-service-dotnet -n pet-clinic

The payment service will be functional once these AWS resources are created.

---

✅ Status: Complete
👤 Requested by: @sunkavar
🔗 Workflow: View details

Powered by AI Agent