Infrastructure as code

[prince-chrismc]

Automate the deployment process to AWS EC2 (or other) service

Perhaps a service like pulumi or codefresh could be beneficial

[prince-chrismc]

Required #21

[prince-chrismc]

https://www.pulumi.com/docs/tutorials/aws/ecs-fargate/#step-2-build-the-dockerized-app

vs

https://codefresh.io/docs/docs/how-to-guides/migrating-from-travis-ci/#deploy-on-example-of-aws-elastic-beanstalk

Decision TBA

[prince-chrismc]

https://learn.hashicorp.com/tutorials/terraform/aws-build?in=terraform/aws-get-started
https://medium.com/@bradford_hamilton/deploying-containers-on-amazons-ecs-using-fargate-and-terraform-part-2-2e6f6a3a957f

[prince-chrismc]

I really like pulumi in turns of it's flexibility and real code as infrastructure.

All three options are closely packed, the biggest difference is the capabilities of the DSL (codefresh and terraform) and width of the feature set (codefresh)

CodeFresh

is more than just deployments, it supports the entire CI/CD pipeline which is great for new projects but my intention is to sink or swim with GitHub Actions. The second strike was it's restricted to YAML which is limit in the extensibility (no example of security group permissions for AWS).

Terraform

Super competitive, it was first to really take off for a reason, the example and documentation made it very easy to understand it structure... but it was all costume DSL pseudo-JSON like. It does support "variables" but they were an afterthought and it's entirely static config. The strike ❌ was that everything needed to be exact for one instance, In order to have a second instance category would take a second nearly duplicated *.tf (I am sure there's a better way I just did not find it)

Pulumi

Code should be code not mark-up. The programmatic approach truly free the DevOps. There seem to be the hefty community which drives each of the six languages supported. Most interestingly TypeScript and Go. There are a ton of examples and the documentation is a delight.

[prince-chrismc]

Getting starting with Pulumi/Go totalled ~3.5hrs which blows my mind this use to take teams days to do. Times have changed.

There's POC prove that it's possible to meet the needs of this project

• deploy pre-built image for a non-default docker registry!

https://github.com/prince-chrismc/Hello-Go
https://github.com/prince-chrismc/Hello-Pulumi

[prince-chrismc]

Revisiting this now that the image size has been greatly reduced... https://www.pulumi.com/docs/tutorials/aws/ec2-webserver/

Most likely opting for the TypeScript since the code will be much lighter and the support is better!

❓ how can I reuse an existing EC2 instance

https://www.pulumi.com/docs/reference/pkg/aws/ec2/instance/#look-up

https://www.pulumi.com/docs/reference/pkg/aws/ec2/instance/#import

https://www.pulumi.com/docs/guides/adopting/import/#pulumi-import-resource-operation

[prince-chrismc]

https://github.com/pulumi/examples/blob/76cdb38ad9c1e6b632910eaadb38263f80f9015b/aws-ts-voting-app/index.ts

The challenge is the the backend is using self-signed certificate which the ELB complains about