# Mixing functions with docker and zip for AWS

**URL:** <https://forum.serverless.com/t/mixing-functions-with-docker-and-zip-for-aws/20106>\
**Category:** Serverless Framework\
**Tags:** aws, lambda\
**Created:** [April 22, 2024, 7:26am UTC](https://forum.serverless.com/t/mixing-functions-with-docker-and-zip-for-aws/20106 "2024-04-22T07:26:46Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![alanwilter](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/alanwilter/32/6415_2.png) [@alanwilter](https://forum.serverless.com/u/alanwilter)\
**Post date:** [April 22, 2024, 7:26am UTC](https://forum.serverless.com/t/mixing-functions-with-docker-and-zip-for-aws/20106/1 "2024-04-22T07:26:46Z")

</div>

I was writing a new `serverless.yml` for a new function when it occurred to me…

Basically, I have a service for AWS with like 15 functions, all using docker images. The AWS lambdas created work fine.

Now I want to create a new AWS lambda function that actually calls one or of these 15 lambdas accordingly and I was writing a new `serverless_new.yml`, on automatic mode, when I realise that:

1. I may not need a docker since it’s a simple python script to call other lambdas
2. If I can do it as zip package, can I mix `zip` and `docker` functions in one `serverless.yml`?

They would access different buckets with different `iam.role.statements` but otherwise I don’t see why I can’t do this except that it may take longer to deploy (but maybe not before my original 15 lambdas are very stable and I’m not changing its code that often anymore).

And they would have a different **deploy**  **stage** call as well. So it would set them aside right?