# Deploy only works for us-east-1

**URL:** <https://forum.serverless.com/t/deploy-only-works-for-us-east-1/2293>\
**Category:** Serverless Framework\
**Created:** [July 14, 2017, 8:57pm UTC](https://forum.serverless.com/t/deploy-only-works-for-us-east-1/2293 "2017-07-14T20:57:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nickwood2009](https://avatars.discourse-cdn.com/v4/letter/n/a8b319/32.png) [@nickwood2009](https://forum.serverless.com/u/nickwood2009)\
**Post date:** [July 14, 2017, 8:57pm UTC](https://forum.serverless.com/t/deploy-only-works-for-us-east-1/2293/1 "2017-07-14T20:57:26Z")

</div>

Just started working with the serverless framework, so very new.  
I tried creating a serverless.yml file in the region: “ap-southeast-2” that:

1. creates cloudfront
2. creates SSL cert
3. creates DNS entries in 53
4. pushes all website files to S3 bucket.

it kept failing with the following:  
“An error occurred while provisioning your stack: CDN - The specified SSL certificate doesn’t exist, isn’t in us-east-1 region, isn’t valid, or doesn’t include a valid certificate chain…”

Because the region was mentioned as the issue I tested changing the region to “us-east-1” and the deployment was successful. I changed nothing else in my yaml file. Is there any reason why the exact same deployment that is fully self contained (no dependencies on existing services except for the domain) would work in one region but not another?

---

<div class="post-metadata">

**Author:** ![rowanu](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/rowanu/32/75_2.png) [@rowanu](https://forum.serverless.com/u/rowanu)\
**Post date:** [July 17, 2017, 5:24am UTC](https://forum.serverless.com/t/deploy-only-works-for-us-east-1/2293/2 "2017-07-17T05:24:16Z")

</div>

CloudFront is a “global” service (like IAM, etc), which in practice means it only exists/works in `us-east-1`. ACM certificates can only be used with CloudFront if they exist in `us-east-1`, so this is why you’re getting this error.

The easiest resolution is to just deploy your service to `us-east-1`. If you have to deploy your service to `ap-southeast-2` then you’ll need to deploy your resources separately (since CloudFormation templates are pre-region).