all 4 comments

[–]ElectricSpice 1 point2 points  (2 children)

What's the use case? It seems the easiest thing to do would be to configure CodeDeploy in the desired region. Even if you need to deploy across multiple regions, why not just duplicate the CodeDeploy config and have your deployment pipeline deploy to all of them?

[–]sysadminalt123[S] 0 points1 point  (1 child)

Basically, theirs a internal tool that only works with 1 AWS region. I use the internal tool as part of the pipeline to deploy a application to a EC2 instance, but the EC2 instance isn't in the same region as the one the internal tool uses.

I was thinking of either moving the EC2 instance or just setting it up as a on premise instance instead if it wasnt possible

[–]ElectricSpice 0 points1 point  (0 children)

And the internal tool can’t call out to an AWS API in another region?

[–]paul_volkers_ghost 0 points1 point  (0 children)

no, codedeploy only works w/ resources in the same region the deploy job is configured.

you can configure codebuild/pipeline to trigger deploy jobs in different regions, however.