Skip to content

Conversation

@khashf
Copy link
Contributor

@khashf khashf commented Mar 19, 2018

Given that the policy of s3 also allow other services (include ec2) read from its buckets and files

Given that policy of s3 also allow other services (include ec2) read from its buckets and  files
@khashf khashf requested a review from MikeTheCanuck March 19, 2018 06:02
@MikeTheCanuck
Copy link
Contributor

Hey @DingoEatingFuzz - would these additions help you with assigning the role I'd requested to the EC2 box for PostgreSQL?

@iant01
Copy link
Contributor

iant01 commented Mar 22, 2018

The ec2 role to permit S3 access should be narrowed to just the archive bucket if its purpose is to enable the ec2 instance to access the database dumps to use in initializing the database. If one or two other buckets need to be accessed, use a conditional to restrict to just the ones needed. Right now the role provides access to all current and future buckets in the account

@khashf khashf self-assigned this Mar 26, 2018
@DingoEatingFuzz
Copy link
Contributor

Hey @khashf, I dig the intent here to codify the process of creating roles and policies as well as codifying the details of said roles and policies. However, I don't think bash is the best tool for it.

We'd be better off taking the same infrastructure as code spirit and applying it to purpose-built tool/spec like Cloud Formation or Terraform.

Since we already have some Cloud Formation in use, it makes sense to continue going down that route.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants