Reason: service was running ok on old config that wasn’t changed, so I suggest that correct creds were set directly using kubectl.

Solution: Set correct names for all AWS credentials, ensuring service is working and connecting to AWS without errors

Preventing steps: changing deployment using kubectl is fast, but will be overwritten on usual deploy flow. Please ensure all changes were saved in your repo after testing.