> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-delivery/troubleshooting-and-resources/armory/general/aws-lambda-plugin-stage-does-not-populate-the-existing-functions.md).

# AWS Lambda Plugin stage does not populate the existing Functions

### Issue <a href="#issue" id="issue"></a>

Functions that had been created in Spinnaker, and cached by Clouddriver, do not get populated by the AWS Lambda Plugin in the Spinnaker UI. The UI would show the following instead:

### Cause <a href="#cause" id="cause"></a>

This is a known issue, and impacts configuring AWS Lambda on a new AWS account. The issue stems from accounts getting merged by index and not by name. The Github issue is noted at: <https://github.com/spinnaker/spinnaker/issues/6271>The Armory documentation about the issue can be found here:<https://docs.armory.io/docs/release-notes/rn-armory-spinnaker/armoryspinnaker_v2-26-1/#lambda-ui-issue>