Skip to content
This repository has been archived by the owner on Jul 7, 2021. It is now read-only.

Blueprint for ec2 roles #103

Open
aarcro opened this issue May 5, 2017 · 2 comments
Open

Blueprint for ec2 roles #103

aarcro opened this issue May 5, 2017 · 2 comments

Comments

@aarcro
Copy link
Contributor

aarcro commented May 5, 2017

I was going to create an s3 stack, but I don't see how to create the role that setting ReadWriteRoles would add a policy to.

I can work on a PR for this. Does it make more sense to have a blueprint that creates a bunch of ec2 and/or lambda roles, or just a single one.

aarcro added a commit to aarcro/stacker_blueprints that referenced this issue May 5, 2017
@phobologic
Copy link
Contributor

I think this is mainly up to how people want to implement this. Here at Remind, for example, we have a blueprint "per application" that handles a lot of the common setup for those applications, including setting up a Role and some default permissions (we let most apps do anything with any dynamodb tables named after the environment + app name, etc).

A simple role creation blueprint should be really easy with TroposphereTypes btw, similar to how we build the s3 bucket blueprint.

@aarcro
Copy link
Contributor Author

aarcro commented May 9, 2017

Are there any examples of these "per application" blueprints? I looked at Empire here a bit, but it was all methods that didn't do anything. I suppose that's something of a skeleton.

Maybe doc that kind of workflow at least.

phobologic added a commit that referenced this issue Aug 24, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants