Troubleshoot AWS Services

This topic explains how you troubleshoot issues related to AWS Services on Tanzu Application Platform (commonly known as TAP).

Secret key name for Amazon MQ claims do not match the name used in the Spring Cloud Bindings library

Symptom:

When you create a claim for Amazon MQ (RabbitMQ), the resulting binding secret contains a key named endpoint. This does not match the key name that the Spring Cloud Bindings library expects, which is addresses. As a result, when you bind Spring-based workloads to the Amazon MQ service, the connection is not established automatically.

Cause:

This issue was caused by a misconfiguration in the CompositeResourceDefinition and Composition for the Amazon MQ service. These resources have been updated to resolve the issue. However, Crossplane does not support changes to connectionSecretKeys in CompositeResourceDefinition resources.

Solution:

The following workaround is only required if you have upgraded Tanzu Application Platform from v1.8.0 or v1.8.1.

To workaround this issue:

1. Find the name of the Crossplane pod, for example:

   kubectl get pod -lapp=crossplane -n crossplane-system
   

2. Delete the pod, for example:

   kubectl delete pod CROSSPLANE-POD-NAME -n crossplane-system
   

   Where CROSSPLANE-POD-NAME is the name of the Crossplane pod you retrieved.

After you delete the pod, it is automatically recreated. This causes Crossplane to re-read the updated list of connectionSecretKeys from the CompositeResourceDefinition. New claims for Amazon MQ (RabbitMQ) will now contain the correct set of key names.