Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Documentation] Configuration section #41

Open
mickelsonm opened this issue Nov 30, 2015 · 4 comments
Open

[Documentation] Configuration section #41

mickelsonm opened this issue Nov 30, 2015 · 4 comments

Comments

@mickelsonm
Copy link

It would be nice if the Configuration section could be broken up into smaller readable sections. The way it stands now I am personally finding it hard to get the information I am looking for quickly.

Perhaps if it were something like :

Basics
Basics -> Configuration
Basics -> Configuration -> Environments
Basics -> Configuration -> Environments -> Development
Basics -> Configuration -> Environments -> Production

Maybe more granular would help the end user find/read about how to configure something more easily?

Also, when configuring for production...I am finding this process to be rather difficult. I have minimal AWS experience, so I am not sure exactly what needs to be done when setting up the IAM policies and the DynamoDB table that Confidant uses. Could you create a video showing how to setup Confidant in a production environment or at the very least provide a list of detailed steps to do so?

Thanks!

@ryan-lane
Copy link
Contributor

Hey @mickelsonm, thanks for the feedback! I'll try to make the config docs more approachable. The screencasts are a good idea as well.

@ryan-lane
Copy link
Contributor

As for the configuration of IAM policies and dynamo tables and such, the policies shown in the config should be almost exactly what you need. You'll need to generate two KMS keys, with the specified policies attached (you'll need to manually edit the key policy - there's a button for this in the console somewhere in the key's configuration). For the IAM policy for confidant itself, you'll need to create a role, then a couple inline policies for it. The docs show the IAM policy required. For the dynamodb table you'll create one table with two global secondary indexes. The keys for the table and indexes is here.

@mickelsonm
Copy link
Author

@ryan-lane Thanks for understanding and I look forward to whatever you come up with.

As for the added AWS information, thanks for summing it up. Between learning Confidant itself and struggling to make sense of why AWS makes things more complex than what it should be...it has been a fun learning experience/work task. Hopefully, i'll get this up-and-running soon.

Thanks again!

@ryan-lane
Copy link
Contributor

You're welcome. Feel free to hop into the confidant channel on freenode if you want to talk about any troubles you're having!

rowillia pushed a commit that referenced this issue Jan 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants