# Fleet AWS Integration Error - API keys not configured for metricbeat **URL:** \ **Category:** Elasticsearch\ **Tags:** fleet\ **Created:** [December 17, 2020, 12:49pm UTC](https://discuss.elastic.co/t/fleet-aws-integration-error-api-keys-not-configured-for-metricbeat/258992 "2020-12-17T12:49:11Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![matt\_t1](https://avatars.discourse-cdn.com/v4/letter/m/dfb087/32.png) [@matt\_t1](https://discuss.elastic.co/u/matt_t1)\ **Post date:** [December 17, 2020, 12:49pm UTC](https://discuss.elastic.co/t/fleet-aws-integration-error-api-keys-not-configured-for-metricbeat/258992/1 "2020-12-17T12:49:11Z")
AWS integration version 0.3.12 allows Access and Secret keys to be specified, both for log and metric ingestion. This works for logs, but for metrics the values are not propagated to elastic-agent.yml. Configuring a shared credential file and credential name does work as expected. ---
**Author:** ![Kaiyan\_Sheng](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaiyan_sheng/32/38247_2.png) [@Kaiyan\_Sheng](https://discuss.elastic.co/u/Kaiyan_Sheng)\ **Post date:** [December 17, 2020, 2:39pm UTC](https://discuss.elastic.co/t/fleet-aws-integration-error-api-keys-not-configured-for-metricbeat/258992/2 "2020-12-17T14:39:14Z")
Hello! I recently found the same issue. We will work on getting it fixed soon! Here is the github issue to track this bug: [https://github.com/elastic/integrations/issues/465](https://github.com/elastic/integrations/issues/465) Thank you! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 14, 2021, 2:39pm UTC](https://discuss.elastic.co/t/fleet-aws-integration-error-api-keys-not-configured-for-metricbeat/258992/3 "2021-01-14T14:39:19Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.