Amplify Kotlin Android feature for AWS IoT Core
datasciencemachine opened this issue · 4 comments
Before opening, please confirm:
- I have searched for duplicate or closed issues and discussions.
Language and Async Model
Kotlin
Amplify Categories
Not applicable
Gradle script dependencies
// Put output below this line
Environment information
# Put output below this line
Please include any relevant guides or documentation you're referencing
No response
Describe the feature request
In the Amplify v2 docuementation for Kotlin or Android, I am not able to see any implementation for AWS IoT Core in it. Basically, I need the support to create an android app to control my IoT Core Things.
Initialization steps (if applicable)
No response
Code Snippet
// Put your code below this line.amplifyconfiguration.json
No response
GraphQL Schema
// Put your schema below this line
Additional information and screenshots
No response
Amplify v2 does not have IoT capabilities.
If you are looking to make mqtt connections, you will want to use aws-iot-device-sdk-java.
If you are looking for APIs to manage IoT, you can use the AWS Kotlin SDK
Thanks for your help Tyler. I can use sdk for my use case as well. However, on the sdk repo readme, it was mentioned to use amplify instead of sdk directly, like in the screenshot below:
This the repo where i am planning to use the sdk from, can you please guide me if this repo is different from the ones you shared earlier to get iot core mqtt connection.
https://github.com/aws-amplify/aws-sdk-android
@datasciencemachine As Tyler suggested, Amplify is not a complete 1:1 replacement for aws-sdk-android. So you can use the two other repos as he suggested.
For the MQTT connection, it actually looks like there's a v2 of that library: https://github.com/aws/aws-iot-device-sdk-java-v2
For the AWS SDK Kotlin, here is the docs page with code examples for doing IoT things with it: https://github.com/awsdocs/aws-doc-sdk-examples/tree/main/kotlin/services/iot#code-examples
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.