I don't think my organization allows creating AWS ...
# ask-metaflow
c
I don't think my organization allows creating AWS resources in any way other than through CloudFormation. Can someone please guide me through how I can deploy step functions using CFN instead of boto3?
v
hi Arkadiy! You can find a CloudFormation template for deploying the open-source Metaflow stack here: https://outerbounds.com/engineering/deployment/aws-managed/cloudformation/
when you use Metaflow, Metaflow takes care of creating workflows in Step Functions, so you don't need a separate CFN template for that
c
@straight-shampoo-11124 I am using that template. But what I mean is this - my organization will not allow Metaflow to create workflows in Step Functions, or even create job definitions in Batch, without using a CloudFormation template. Metaflow is using boto3.
v
right, Metaflow handles creation of those resources internally. I don't know what counts as an AWS resource exactly in your org, but if you deployed Metaflow on EKS and used Argo, then you could use
@kubernetes
and
argo-workflows create
without having to create any new AWS resources on the fly.
we're happy to help you get that going, if that would be an option for you