A user interface for AWS for writers

Open
#153 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws
Domain
cloud

Research direction

The issue names no repository files, tests, or entry points. Start by defining the AWS authorization flow for non-developers and the creation of private and public S3 buckets for Little Outliner. Done should include a documented, workable account-authorization and bucket-access flow, but the issue does not specify implementation or test criteria.

Written by the indexing model from the issue text.

Description

Here's an interesting piece of data.

I said Hey Doc, create an AWS account. I didn't tell him how to do it. I wanted to see what happened. He didn't succeed.

OK so this means to me that we need a piece of software. A rough idea of how it would work. The user signs on to their Amazon account, the one they use to buy socks, and then authorizes you to act on its behalf with AWS. Ideally that would feel, to the user, like giving access to an app to use their Twitter identity. From there, you create a pair of S3 buckets, one private and one public. Then you allow my software, Little Outliner, to access his bucket.

I don't know what all these steps are. But it should draw on a user's ability to create accounts on other popular services. I imagine it's what Amazon itself would create if they wanted to provide a service to non-developers. I imagine at this time they consider it a "developer opportunity."

I need this functionality as a go-between my users and my software. I don't want to store their stuff long-term, because I don't have a long-term. :-)

Dominant language
HTML
Stars
134
Forks
10
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scripting/Scripting-News

All issues in scripting/Scripting-News

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.