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

Add AWS Fargate Support #29

Merged
merged 2 commits into from
Jan 20, 2018
Merged

Add AWS Fargate Support #29

merged 2 commits into from
Jan 20, 2018

Conversation

jpignata
Copy link
Contributor

Additions to the template to support the Fargate launch type including adding a new service and task definition changes, introduction of an execution role, and a log group for visibility.

  • Update reference architecture diagram
  • Update ECS Optimized AMIs to amzn-ami-2017.09.g
  • Add script to generate a list of ECS Optimized AMIs on the fly
  • Collapse to a single S3 bucket for distribution
  • Convert vestigial embedded JSON documents to YAML and other minor cleanup
  • README and copy cleanup

Support the Fargate launch type via a parameter in the CloudFormation
template for launch type. If Amazon EC2 is specified, the template will
continue to create an Auto Scaling group of EC2 instance. If AWS Fargate
is specified, this will skipped and the service will specify FARGATE as
the launch type.

- Add service and update task definition for Fargate
- Add a log group to assist in debugging for Fargate tasks
- Convert vestigial embedded JSON into YAML
- Update reference architecture diagrams
- As we're no longer using Amazon S3 in CodePipeline, consolidate into a
  single bucket for templates
- Update the README and minor cleanup
- Adds a script in bin to generate this list by making DescribeImages
  call to each Region.
@jpignata jpignata merged commit 277200e into master Jan 20, 2018
@jpignata jpignata deleted the jp/fargate branch January 20, 2018 00:16
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant