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

Deploying with faasd AWS CDK #207

Open
strongishllama opened this issue Oct 9, 2021 · 9 comments
Open

Deploying with faasd AWS CDK #207

strongishllama opened this issue Oct 9, 2021 · 9 comments

Comments

@strongishllama
Copy link

Hi there!

I've translated the DigitalOcean Terraform deployment into a CDK construct so I cloud play around with it on an AWS EC2 instance.

If you think it would be useful to the community I'd be more than happy to put in a pull request to either add the CDK construct to the docs directory of this project or just link to the NPM package once I've cleaned it up a little.

My initial thought would be the linking the package might be better because I was thinking of adding ECS/Fargate support as well and it might get a bit large to add to the docs directory.

Thanks.

@alexellis
Copy link
Member

Hi @strongishllama I'd be interested in seeing a blog post or sample that we can run and try out.

Let me also ping @nathanpeck who wrote some CDK for inlets and ECS Anywhere, he may also have an interest.

Alex

@strongishllama
Copy link
Author

@alexellis sounds good. I'll clean it up a bit and send through a link to a sample project.

@strongishllama
Copy link
Author

Hey @alexellis,

Here's a link to the demo CDK stack and the NPM package it imports.

If you're looking to try it out your best bet would be to clone the demo stack and follow the deployment steps in the readme.

A couple of things to note, mainly around two assumptions I've made.

  • There needs to be a Route53 hosted zone in the same AWS account and region you're deploying to, so the stack can create an A record for faasd.
  • You'll also need to create a VPC manually (or just use the default one) and add the VPC ID as a property in the stack. This is to get around possible VPC cidr issues.
  • You may also want to tweak your EC2 instance size and class depending on your needs, I've done very little testing under load. They're both available as optional properties.

Of course, any feedback is very welcome.

I'd also be more than happy to write up a blog post if you'd think it would be helpful. The demo stack was just a lot quicker to throw together and I wanted to make sure I was on the right track before committing too much time.

Cheers,
Taliesin

@alexellis
Copy link
Member

Thanks for the example. Yes a blog post is always helpful.

We can send you some stickers to say thanks. It'll be a bit like UDP though as I'm not sure if they'll arrive all the way to New Zealand. We can try though.

@strongishllama
Copy link
Author

strongishllama commented Oct 28, 2021

No worries, I'll hopefully start that soon and send you a link to the draft. That would be a very lost UDP packet as I'm in Australia!

@alexellis
Copy link
Member

Sure let me know when you have something.

@alexellis
Copy link
Member

You can join us on Slack if you like, because there's some development happening on faasd and we could use your help with testing (and contributing if that's of interest)

@alexellis
Copy link
Member

/set title: Deploying with faasd AWS CDK

@derek derek bot changed the title aws cdk deployments Deploying with faasd AWS CDK Nov 2, 2021
@strongishllama
Copy link
Author

Thanks, I'll check it out.

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

No branches or pull requests

2 participants