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

Add ECR policies and make logs policy more flexible #8

Merged
merged 1 commit into from
Jun 19, 2018

Conversation

phobologic
Copy link
Member

This is in preparation of a basic Fargate ECS blueprint.

The aws lambda tests use the cloudwatch log write policy generator, and those tests have not changed, so this should be a no-op as far as existing functionality goes.

This is in preparation of a basic Fargate ECS blueprint.
phobologic added a commit that referenced this pull request Jun 18, 2018
Only creates a worker service in Fargate, no work done to add load
balancers, etc.

Relies on #8
@phobologic phobologic merged commit cfc2700 into master Jun 19, 2018
@phobologic phobologic deleted the update_for_ecs_policies branch June 19, 2018 04:05
phobologic added a commit that referenced this pull request Jun 24, 2018
* Add ECR policies and make logs policy more flexible

This is in preparation of a basic Fargate ECS blueprint.

* Simple Fargate Service + ECS Cluster blueprints

Only creates a worker service in Fargate, no work done to add load
balancers, etc.

Relies on #8

* Cleanup fargate blueprint to working state

This also cleans up some confusion in the policies for ecs & cloudwatch.
Turns out you can't really use wildcards in cloudwatch stream names.

* Key/values in env vars should be strings
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.

2 participants