I'm creating flutter application with Firebase authentication. But I need to store some recording files (mp3) to cloud storage. I need to use aws s3 as a requirement. So I tried to integrate the that with flutter.
I have found official plugin called amplify_storage_s3 on pub.dev
But I had to read from documentation I need to amplify authentication to use that.
I don't want to use amplify auth because I'm already done it with firebase authentication.
So what I can do?
Related
I want to connect my Flutter project with owncloud on my server. How do I do this? What do I study so I can do it?
You can use the Own Cloud External API. It allows third party developers to access data provided by ownCloud apps.
My customer has hosted GraphQL API using was AppSync. We have working native code to access the same. Need guidance to implement in flutter using flutter_amplify.
I have a cordova app running on android with a spring boot backend.
In the app the client can upload a photo.
At the moment the file is uploaded to google cloud storage via the backend, who has a service credentials file.
When we want to display a photo in the app should the photo be read from google cloud platform via the spring boot app?
Or can we read directly from the google cloud bucket, (in this case how do we authenticate)?
I would say it's simplest to read the data from GCS in the Java code, and then serve the data from your application.
An alternative you could consider is to generate a signed URL in your backend; the client can then use that signed URL to fetch the data. The Google Cloud Storage client library should make generating the signed URL fairly straightforward. You'll want to regenerate each time the client loads a page of photos though, as signed URLs (deliberately) have a limited lifespan.
I am trying to add AWS Cognito to my iOS application using AWS Amplify. The docs suggest to use amplify add auth on the CLI, but this does not seem to work with an existing User Pool (i.e. you have to create a new one). Is it possible to integrate AWS Cognito into my iOS (Swift) project using an existing User Pool?
Amplify CLI doesn't support existing resources at the moment but you can manually edit your awsconfiguration.json to include the User Pool that is already present as outlined here.
Update: Since 2020 Amplify allows you to use existing User Pools (yeah!). Just run:
amplify import auth
Source: https://aws.amazon.com/de/about-aws/whats-new/2020/10/use-existing-cognito-user-pools-identity-pools-for-amplify-project/
I have a Raspberry Pi3 device which has Android Things dev preview 0.6.1 installed. On completing certain operations, the device needs to send data to Google Cloud Storage. To do so it must have an API key to authenticate itself.
In Android devices it could be done easily using by integrating Google Sign in Option but since my Android Thing device doesn't have any interface, Google Sign In could not be implemented in it.
I have gone through github project Android Things Weather Station Sample which is using Google Service Account to publish data to PubSub. To do so, it generates and imports a credential.json file into the project and somehow generates credentials from it.
So my question stands is, without user consent, can we use Google Service Accounts to authenticate with Google Cloud Storage? If yes, how can we generate access token from it ? If no, is there any other method to authenticate with GCS?
The simplest and most secure way to authenticate your IoT devices with Google Cloud is using Cloud IoT Core to publish data over MQTT or HTTP into Cloud Pub/Sub. Cloud IoT Core is a bridge designed to securely manage large fleets of devices and authenticate them with your cloud project.
Take a look at the SensorHub sample app on GitHub, which is similar to the weather station, but uses Cloud IoT Core to authenticate and publish instead.
As Shubham stated, using a service account is one way to authenticate devices. Otherwise you'd need to build a mobile companion app which you use to authenticate the user. Then you would have to transfer that token to the IoT device.
In case anyone faces the same issue, I found this document which has explained the way to authenticate devices with Google Cloud without the consent of a user.