# AWS integration 7.1 fleet agent bug or UI glitch **URL:** \ **Category:** Kibana\ **Tags:** fleet\ **Created:** [July 30, 2026, 12:21pm UTC](https://discuss.elastic.co/t/aws-integration-7-1-fleet-agent-bug-or-ui-glitch/388899 "2026-07-30T12:21:25Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![stanley783](https://avatars.discourse-cdn.com/v4/letter/s/a5b964/32.png) [@stanley783](https://discuss.elastic.co/u/stanley783)\ **Post date:** [July 30, 2026, 12:21pm UTC](https://discuss.elastic.co/t/aws-integration-7-1-fleet-agent-bug-or-ui-glitch/388899/1 "2026-07-30T12:21:25Z")
Recently upgraded ELK cluster from 9.3.2 to 9.4.4. On older version had AWS integration of version 6.20, on new cluster upgraded it to 7.1 latest. Prior to upgrade, we had 1 Elastic agent with this integration 6.2 (agent also went from 9.3.2. to 9.4.4 before upgrading integration). After upgrade i got error in "policy" in integration, that agent is not compatible (yet agent was already 9.4.4 prior to upgrading integration) ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/4/645bd0f6d300dedf7aa5cef125a0fcdba2ab11a5.png) After removing integration from policy only, and adding it again that error dissapeared but in Fleet, agent had "i" status about that policy is stuck on lower version ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/e/feebfcc176fe3cb118ee08b9ef267a002b321e37.png) I tried to remove integration from policy again but got better error, that agent was unable to sync Agent policy. I did not try to setup other integration to verify if this is just UI glitch or it seriosly does not update. elastic-agent status via cli was reporting healthy. ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/b/6b466b91555389ddcd7346e3ebc49094f005a050.png) Not sure if this is UI glitch, Bug, or am i misconfiguring something now. I tried to add AWS integration on different agent, which never had aws integration, and it got bricked too. So i added integration back to policy with nothing configured in it, just so it at least show it updates agent policy sucesfully. ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [July 30, 2026, 12:32pm UTC](https://discuss.elastic.co/t/aws-integration-7-1-fleet-agent-bug-or-ui-glitch/388899/2 "2026-07-30T12:32:17Z")
Hello, There are multiple issues related to Version Specific Agent Policies introduces in 9.4.4, they are being tracked here: [[Fleet] Meta: version-specific agent policies — known bugs and follow-up work · Issue #281074 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/281074) For the agents running the AWS integration make sure that they are on version 9.4.4 and try the workaround of reassigning the agent to the same policy. For example, if the policy is named `aws-policy`, select the agents with issues in the Fleet UI, go into Actions \> Assign to new policy, and choose the same `aws-policy`. This is expected to fix the outdated policy and future change should sync as well, if this do not work, then this may be a new unreported bug related to version specific agent policies. ---
**Author:** ![stanley783](https://avatars.discourse-cdn.com/v4/letter/s/a5b964/32.png) [@stanley783](https://discuss.elastic.co/u/stanley783)\ **Post date:** [July 30, 2026, 12:40pm UTC](https://discuss.elastic.co/t/aws-integration-7-1-fleet-agent-bug-or-ui-glitch/388899/3 "2026-07-30T12:40:27Z")
Thanks for advice. Regarding issue "Outdated policy" after removing AWS integration from policy, reassigning policy worked. For the issue that agent is latest as well as integration, and agent has that "i" alert about "version specific policy used" it did not fix. Will check if this is mentioned in bugs. Thank you very much. ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [July 30, 2026, 12:43pm UTC](https://discuss.elastic.co/t/aws-integration-7-1-fleet-agent-bug-or-ui-glitch/388899/4 "2026-07-30T12:43:34Z")
> [@stanley783](#): > > For the issue that agent is latest as well as integration, and agent has that "i" alert about "version specific policy used" it did not fix. Yeah, I don't think this was reported yet or if it was solved by the recent changes, just checked on my cluster and I have the same thing, but this is less problematic as it seems just a UI information, not related to sync. I've just made a comment on the main issue tracking this to see if a separed issue is required. ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [July 30, 2026, 12:54pm UTC](https://discuss.elastic.co/t/aws-integration-7-1-fleet-agent-bug-or-ui-glitch/388899/5 "2026-07-30T12:54:28Z")
> [@stanley783](#): > > Regarding issue "Outdated policy" after removing AWS integration from policy, reassigning policy worked. The reassign should work with the AWS Integration in the policy as well, it is working in my case. ---
**Author:** ![stanley783](https://avatars.discourse-cdn.com/v4/letter/s/a5b964/32.png) [@stanley783](https://discuss.elastic.co/u/stanley783)\ **Post date:** [July 30, 2026, 12:55pm UTC](https://discuss.elastic.co/t/aws-integration-7-1-fleet-agent-bug-or-ui-glitch/388899/6 "2026-07-30T12:55:16Z")
That info-error came back after minute or two unfortunatelly ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [July 30, 2026, 1:00pm UTC](https://discuss.elastic.co/t/aws-integration-7-1-fleet-agent-bug-or-ui-glitch/388899/7 "2026-07-30T13:00:19Z")
> [@stanley783](#): > > That info-error came back after minute or two unfortunatelly What came back? The agent is out of sync and showing the _Outdated policy_ message? Or you have the information with the message: > This agent uses a version-specific policy because it doesn't meet the agent version requirements of some integrations. ---
**Author:** ![stanley783](https://avatars.discourse-cdn.com/v4/letter/s/a5b964/32.png) [@stanley783](https://discuss.elastic.co/u/stanley783)\ **Post date:** [July 30, 2026, 1:09pm UTC](https://discuss.elastic.co/t/aws-integration-7-1-fleet-agent-bug-or-ui-glitch/388899/8 "2026-07-30T13:09:44Z")
Sorry by info-error i meant the latter: This agent uses a version-specific policy because it doesn't meet the agent version requirements of some integrations. After reassigning the policy it did dissapear for some time and i tought it is fixed but it reappeared. Trying it again atm. Took around minute to reappear ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [July 30, 2026, 1:11pm UTC](https://discuss.elastic.co/t/aws-integration-7-1-fleet-agent-bug-or-ui-glitch/388899/9 "2026-07-30T13:11:04Z")
Yeah, this will not go away, no matter what you do, it is a confusing message that should not appear. You can ignore it. ---
**Author:** ![stanley783](https://avatars.discourse-cdn.com/v4/letter/s/a5b964/32.png) [@stanley783](https://discuss.elastic.co/u/stanley783)\ **Post date:** [July 30, 2026, 1:13pm UTC](https://discuss.elastic.co/t/aws-integration-7-1-fleet-agent-bug-or-ui-glitch/388899/10 "2026-07-30T13:13:39Z")
Aight, thanks. One more thing that Claude AI pointed out, which i used to help me troubleshoot, was that policy id had suffix #9.4 827fe189-......6fa67575cbc1#9.4 which it said it was added as version-hold suffix, possibly causing that info-alert. No idea if true, just trowing it here to inquire. ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [July 30, 2026, 3:01pm UTC](https://discuss.elastic.co/t/aws-integration-7-1-fleet-agent-bug-or-ui-glitch/388899/11 "2026-07-30T15:01:48Z")
Just created an issue based on what I'm seeing here on my cluster. Feel free to add feedback and share evidence from your side as well. > > > \*\*Kibana version:\*\* > 9.4.4 > > \*\*Elasticsearch version:\*\* > 9.4.4. > \*\*Server OS version…:\*\* > Elastic Cloud Hosted > > \*\*Browser version:\*\* > Not related > \*\*Browser OS version:\*\* > Not related > > \*\*Original install method (e.g. download page, yum, from source, etc.):\*\* > Elastic Cloud Hosted > > \*\*Describe the bug:\*\* > > In the Fleet UI \> Agents, there is an information link that will show a pop-up with the phrase: > > \> This agent uses a version-specific policy because it doesn't meet the agent version requirements of some integrations. > > But the agent is on the latest version available and meet the requirements for all integrations in the policy, the information is misleading as it indicates a problem, but there is no action to be taken. > > \*\*Steps to reproduce:\*\* > > 1. Create a deployment on 9.4.4 > 2. Create a policy with some integration that triggers version-specific policies, like the Auditd integration. > 3. Enroll an agent on version 9.4.4 > 4. Validate on Fleet UI \> Agents that it shows that the agent does not meet the requirements of some integrations. > > \*\*Expected behavior:\*\* > > No warning should be present if the agent meets all the requirements for the integrations. > > \*\*Screenshots (if relevant):\*\* > > \Image