-
Notifications
You must be signed in to change notification settings - Fork 0
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
Feat/frontend key access #132
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
60 changes: 60 additions & 0 deletions
60
infrastructure/environments/cloudformation/full/common/general_key_access.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,60 @@ | ||
AWSTemplateFormatVersion: 2010-09-09 | ||
Description: | | ||
This template adds cognito triggers to handle post-authentication tasks | ||
|
||
|
||
Parameters: | ||
DataStoreLocationArn: | ||
Description: The S3 Bucket users will have access to for uploading files | ||
Type: String | ||
CognitoUserPool: | ||
Description: ID of the User Pool to add the triggers to | ||
Type: String | ||
Environment: | ||
Type: String | ||
Description: | | ||
Determines the type of environment. "stag" and "prod" are the two valid strings. Stag will auto-deploy | ||
new versions, while prod will only deploy the cached versions and updates will need to be applied through | ||
infrastructure updates. | ||
Default: prod | ||
|
||
Resources: | ||
FrontendUser: | ||
Type: AWS::IAM::User | ||
Properties: | ||
UserName: "frontend-hosting-user" | ||
|
||
GeneralUserPolicy: | ||
Type: AWS::IAM::Policy | ||
Properties: | ||
PolicyName: GeneralUserPolicy | ||
Users: | ||
- !Ref FrontendUser | ||
PolicyDocument: | ||
Version: "2012-10-17" | ||
Statement: | ||
- Effect: Allow | ||
Action: | ||
- "s3:DeleteObject" | ||
- "s3:GetObject" | ||
- "s3:ListBucket" | ||
- "s3:PutObject" | ||
- "s3:PutObjectAcl" | ||
Resource: | ||
- !Sub "${DataStoreLocationArn}" | ||
- !Sub "${DataStoreLocationArn}/*" | ||
|
||
|
||
AccessKey: | ||
Type: AWS::IAM::AccessKey | ||
Properties: | ||
UserName: | ||
Ref: FrontendUser | ||
|
||
Outputs: | ||
AccessKeyId: | ||
Description: "AWS Access Key ID" | ||
Value: !Ref AccessKey | ||
SecretAccessKey: | ||
Description: "AWS Secret Access Key" | ||
Value: !GetAtt AccessKey.SecretAccessKey |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might need to chat this one through to fully understand what's going on here :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All this is doing is generating the access keys with the required permissions for Heroku so I can copy the result in to Heroku's env vars. :-)
Ideally I would have a setup that doesn't need this and users of the platform would just assume the role directly. That will be for later.