# Use amazon AWS native API **URL:** \ **Category:** Ignition\ **Tags:** scripting\ **Created:** [October 24, 2025, 7:02am UTC](https://forum.inductiveautomation.com/t/use-amazon-aws-native-api/111692 "2025-10-24T07:02:05Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![arpit\_yadav](https://avatars.discourse-cdn.com/v4/letter/a/a5b964/32.png) [@arpit\_yadav](https://forum.inductiveautomation.com/u/arpit_yadav)\ **Post date:** [October 24, 2025, 7:02am UTC](https://forum.inductiveautomation.com/t/use-amazon-aws-native-api/111692/1 "2025-10-24T07:02:06Z")
Hi all, I’m trying to connect Ignition with **AWS IoT SiteWise** using **AWS native APIs** instead of MQTT or IoT Bridge. The goal is to fetch and push data to SiteWise directly from Ignition scripts via AWS API. Has anyone here implemented or tested this kind of direct **AWS IoT SiteWise API integration** in Ignition? Any examples or best practices would be great! ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [October 24, 2025, 3:44pm UTC](https://forum.inductiveautomation.com/t/use-amazon-aws-native-api/111692/2 "2025-10-24T15:44:23Z")
You could in theory load the AWS SDK via a custom module, but it's still going to be using MQTT/HTTP "under the hood" (as far as I can tell) so I'm not sure what advantage this would actually give you. ---
**Author:** ![arpit\_yadav](https://avatars.discourse-cdn.com/v4/letter/a/a5b964/32.png) [@arpit\_yadav](https://forum.inductiveautomation.com/u/arpit_yadav)\ **Post date:** [October 27, 2025, 4:30am UTC](https://forum.inductiveautomation.com/t/use-amazon-aws-native-api/111692/3 "2025-10-27T04:30:40Z")
While you’re correct that loading the AWS SDK via a custom module ultimately uses MQTT or HTTP under the hood, there’s a specific customer demand to use AWS’s native SiteWise APIs to retrieve asset property values directly and plot trends accordingly. The advantage is that these APIs (like GetAssetPropertyValue and GetAssetPropertyAggregates) allow for targeted, secure, and auditable data access from the IoT side, which is ideal for both current and historical trend visualization and serves industrial requirements beyond generic telemetry streams.​ Given this scenario, how can the direct SDK/API methodology be best implemented for real-time or historical trend plotting—especially for use cases where customers require fine-grained control and visibility into their IoT asset metrics from their SCADA or dashboard systems? What steps and best practices would you recommend to achieve reliable, scalable integration with minimal latency and maximum security? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [October 27, 2025, 11:00am UTC](https://forum.inductiveautomation.com/t/use-amazon-aws-native-api/111692/4 "2025-10-27T11:00:03Z")
You are asking questions that belong in the Module Development category, and are so broad that you are unlikely to get a response, short of paying for help. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [October 27, 2025, 3:26pm UTC](https://forum.inductiveautomation.com/t/use-amazon-aws-native-api/111692/6 "2025-10-27T15:26:14Z")
I'm not going to engage with you/your LLM any further than linking these posts where I go through a variety of things that are wrong. > [@Updating Limble Asset Information through Ignition](https://forum.inductiveautomation.com/t/updating-limble-asset-information-through-ignition/111559/3): > > Your LLM steered you wrong and gave you a lot more code than you need; they're quite good at that. This is less code and does the same as what you wrote, but with better error handling and usable from any scope, not just callable from Perspective. You can drop this into the project library. # ================================ # Limble API credentials # ================================ # These credentials are used to authenticate with the Limble CMMS API. # client\_id and client\_secret are provid… > [@Ignition Edge sends emails but no attachments](https://forum.inductiveautomation.com/t/ignition-edge-sends-emails-but-no-attachments/111666/9): > > Similar setup here - nothing against you personally, it's just that each time I work through a "person got a mountain of code from an LLM" post and try to guide them through all the things it did wrong makes me feel like Sisyphus. Top level notes: You should only rarely need to import anything in small Ignition scripts. Any imports you do use, you should be judicious about. You should never import system or anything from system. You should never use Jython's datetime library. You should (a…