<p>The <a href="https://octopus.com/pricing/overview" rel="nofollow noreferrer">community edition</a> of Octopus is free to self-host, so that might be an option if you have somewhere you can run it. You can have 5 targets and 5 projects.</p>
<p>You could run a free cloud trial to test it out and then think about self-hosting once you've worked out the details.</p>
<p>Once you have it, you could use it to deploy other stuff you have, too. I'm using Octopus Cloud community edition to deploy a little monitoring tool I wrote (UpDn) that checks my websites are up, their certificates aren't about to expire, and that my DNS hasn't been messed with. It easily saves me $10 of effort each month :)</p>

CC BY-SA 4.0
2023-03-22T17:26:00.063Z
I have seen Octo and don't want to pay or self-host :)
James Geddes
CC BY-SA 4.0
2023-03-23T10:38:18.313Z
I'm looking through my list of suggestions, but even the open source stuff would require that you host it as they can't fund this for you (i.e. [Spinnaker](https://spinnaker.io/)). If you don't need all the features of a deployment tool, you may be able to script up your own deployment process to run from your CI tool instead?
Fenton
CC BY-SA 4.0
2023-03-23T11:58:50.857Z
I'll probably just stick with letting Terraform create the lambda based on the latest container in DockerHub
James Geddes
CC BY-SA 4.0
2023-03-22T11:18:46.077Z
2023-03-22T11:18:46.077Z
Fenton
<p>I am working on this little project.</p>
<p><a href="https://github.com/jamesgeddes/itsbeginningtolookalotlikechristmas" rel="nofollow noreferrer">https://github.com/jamesgeddes/itsbeginningtolookalotlikechristmas</a></p>
<p>It's currently a work-in-progress - don't judge!</p>
<p>As you can see, I have configured CircleCI to build, scan and publish the container. That, ideally, should be the end of the road for the Continuous Integration, CI, tool, as Continuous Deployment, CD, should take over, so I would like <a href="https://docs.docker.com/docker-hub/webhooks/" rel="nofollow noreferrer">Docker Hub Webhooks</a> to trigger the deployment of that container into AWS Lambda.</p>
<p>Unfortunately, I am struggling to find any dedicated CD tools.</p>
<p>I have seen,</p>
<ul>
<li><a href="https://octopus.com/pricing/overview" rel="nofollow noreferrer">Octopus Deploy</a>, but their minimum is £10 per month - more than I would like to pay for such a small project.</li>
<li><a href="https://www.harness.io/pricing?module=cd#" rel="nofollow noreferrer">Harness CD</a>, but their £0 plan only allows you to deploy to Kubernetes</li>
</ul>
<p>Everything else appears to be,</p>
<ul>
<li>a CI tool</li>
<li>a CI tool that insists that it can do CD as well</li>
<li>self-hosted - which I can't be bothered to do for such a small project</li>
</ul>
<p>How should I go about deploying my container to AWS Lambda while maintaining the best-practice separation of concerns between CI and CD?</p>

<amazon-web-services><deployment><continuous-deployment><continuous-delivery><aws-lambda>
How do you deploy a container to AWS Lambda?
James Geddes
# How do you deploy a container to AWS Lambda?

(Asked by: username_0 on 2023-02-04)

I am working on this little project.

<https://github.com/jamesgeddes/itsbeginningtolookalotlikechristmas>

It's currently a work-in-progress - don't judge!

As you can see, I have configured CircleCI to build, scan and publish the container. That, ideally, should be the end of the road for the Continuous Integration, CI, tool, as Continuous Deployment, CD, should take over, so I would like [Docker Hub Webhooks](https://docs.docker.com/docker-hub/webhooks/) to trigger the deployment of that container into AWS Lambda.

Unfortunately, I am struggling to find any dedicated CD tools.

I have seen,

* [Octopus Deploy](https://octopus.com/pricing/overview), but their minimum is £10 per month - more than I would like to pay for such a small project.
* [Harness CD](https://www.harness.io/pricing?module=cd#), but their £0 plan only allows you to deploy to Kubernetes

Everything else appears to be,

* a CI tool
* a CI tool that insists that it can do CD as well
* self-hosted - which I can't be bothered to do for such a small project

How should I go about deploying my container to AWS Lambda while maintaining the best-practice separation of concerns between CI and CD?

**Tags:** amazon-web-services, deployment, continuous-deployment, continuous-delivery, aws-lambda


---

## 1 answers

### Answer by username_1 on 2023-03-22. Score: -1

The [community edition](https://octopus.com/pricing/overview) of Octopus is free to self-host, so that might be an option if you have somewhere you can run it. You can have 5 targets and 5 projects.

You could run a free cloud trial to test it out and then think about self-hosting once you've worked out the details.

Once you have it, you could use it to deploy other stuff you have, too. I'm using Octopus Cloud community edition to deploy a little monitoring tool I wrote (UpDn) that checks my websites are up, their certificates aren't about to expire, and that my DNS hasn't been messed with. It easily saves me $10 of effort each month :)

> **Comments:**
> **username_0**: I have seen Octo and don't want to pay or self-host :)  
> **username_1**: I'm looking through my list of suggestions, but even the open source stuff would require that you host it as they can't fund this for you (i.e. [Spinnaker](https://spinnaker.io/)). If you don't need all the features of a deployment tool, you may be able to script up your own deployment process to run from your CI tool instead?  
> **username_0**: I'll probably just stick with letting Terraform create the lambda based on the latest container in DockerHub  

---

