AwsAccountProvider

[LHaferkamp]

Connecting your AWS Account with Kepler.gl by using AWS Amplify.
AWS Amplify creates a user pool and storage connected to each user in your AWS account.
Detailed setup instructions are added to the Readme.
At the end you only need to copy the aws-exports.js generated by AWS Amplify into the demo-app/src folder.

There is no redirect to a login page as for the current Dropbox and Carto provider. Login and user permissions are managed by the AWS Amplify JS library. Per default also sign-up is enabled for the newly created user pool.

Bonus: You can display your AWS account name above the "powered by AWS" logo via export AWSAccountName=YOUR_ACCOUNT

[heshan0131]

Thanks for the aws provider. However, demo app is hosted on https://kepler.gl/demo, it is a single page github app, the aws provider won't be accessible. Can you remove it from the list of providers so it doesn't show up in kepler demo app? People will get confused if they can't use it

I would create a new example/awe-provider and move the Readme instructures and dependencies over there

[LHaferkamp]

@heshan0131 : It's a pleasure to contribute to a tool which supports us in our daily work!

I don't know how you build and deploy the page (is it Github pages with Jekyll?), but we could provide you with our AWS configuration file (its in examples/demo-app/src/aws-exports.js) which would allow every user to create her own "Kepler.gl account" inside an AWS account managed by us (we are a team working on DeepAtlas.io) . So every user could create her private maps and could share public maps and you would have a working example for AWS.

Considering your proposal of having a separate example: All the UI for cloud-providers is maintained in the demo-app, how would you share this with a new example which would have the same UI? Can the new example/aws-provider be an extension of the example/demo-app ?