# Deploy Lambda Function Into new region **URL:** \ **Category:** Serverless Framework\ **Created:** [October 12, 2017, 3:10pm UTC](https://forum.serverless.com/t/deploy-lambda-function-into-new-region/2870 "2017-10-12T15:10:10Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![jseiser](https://avatars.discourse-cdn.com/v4/letter/j/b77776/32.png) [@jseiser](https://forum.serverless.com/u/jseiser)\ **Post date:** [October 12, 2017, 3:10pm UTC](https://forum.serverless.com/t/deploy-lambda-function-into-new-region/2870/1 "2017-10-12T15:10:10Z")
I have a service I deployed into us-east-1, I would also like to deploy it to ca-central-1. It fails to deploy stating ``` ~/p/amibackup ❯❯❯ sls deploy -v --region ca-central-1 --stage prod --aws-profile profilename master ✱ Serverless Error --------------------------------------- Deployment bucket is not in the same region as the lambda function Get Support -------------------------------------------- Docs: docs.serverless.com Bugs: github.com/serverless/serverless/issues Forums: forum.serverless.com Chat: gitter.im/serverless/serverless Your Environment Information ----------------------------- OS: linux Node Version: 6.11.3 Serverless Version: 1.23.0 ~/p/amibackup ❯❯❯ ``` serverless.yml contains ``` deploymentBucket: name: 8675309-${self:provider.region}-${ssm:accountID}-serverless ``` Where in S3, both 8675309-us-east-1-55555-serverless and 8675309-ca-central-1-55555-serverless exist in their respective regions. How can I deploy the same service, to multiple regions? ---
**Author:** ![OmniPotent42](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/omnipotent42/32/916_2.png) [@OmniPotent42](https://forum.serverless.com/u/OmniPotent42)\ **Post date:** [October 12, 2017, 10:15pm UTC](https://forum.serverless.com/t/deploy-lambda-function-into-new-region/2870/2 "2017-10-12T22:15:30Z")
Have you tried making the service name dynamic? I’m guessing that the deployment bucket for Serverless is still in the same region, but if you change the service name it should treat it as a completely new service and you won’t have that issue. ---
**Author:** ![buggy](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/buggy/32/177_2.png) [@buggy](https://forum.serverless.com/u/buggy)\ **Post date:** [October 12, 2017, 10:42pm UTC](https://forum.serverless.com/t/deploy-lambda-function-into-new-region/2870/3 "2017-10-12T22:42:15Z")
Try using ```auto deploymentBucket: name: 8675309-${opt:region, self:provider.region}-${ssm:accountID}-serverless ``` or just remove the deploymentBucket. ---
**Author:** ![jseiser](https://avatars.discourse-cdn.com/v4/letter/j/b77776/32.png) [@jseiser](https://forum.serverless.com/u/jseiser)\ **Post date:** [October 13, 2017, 12:27pm UTC](https://forum.serverless.com/t/deploy-lambda-function-into-new-region/2870/4 "2017-10-13T12:27:11Z")
I can not remove the deployment bucket for policy reasons, but your first suggestion worked. Can you explain the difference between ${self:provider.region} and ${opt:region, self:provider.region} ? I read it as self:provider.region is the value I specify with --region. not sure what the opt:region part is. ---
**Author:** ![buggy](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/buggy/32/177_2.png) [@buggy](https://forum.serverless.com/u/buggy)\ **Post date:** [October 14, 2017, 12:25am UTC](https://forum.serverless.com/t/deploy-lambda-function-into-new-region/2870/5 "2017-10-14T00:25:34Z")
Using `--region` doesn’t change the value of `${self:provider.region}`. It’s always the value of region set in the provider section of serverless.yml. By using `${opt:region, self:provider.region}` you’re telling it to use the value from the `--region` command line option if provided then the value for region from the provider section in your serverless.yml if it isn’t. ---
**Author:** ![bill](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/bill/32/1072_2.png) [@bill](https://forum.serverless.com/u/bill)\ **Post date:** [October 14, 2017, 9:38am UTC](https://forum.serverless.com/t/deploy-lambda-function-into-new-region/2870/6 "2017-10-14T09:38:04Z")
regarding your sample about region to be defined. I have another question. Can we defaultly set the order in sls on how to read the variables. ``` `--region` : ${opt:region} system environment variable: ${env:AWS_DEFAULT_REGION} or ${env:AWS_REGION} self: ${self:provider.region} custom: ${self:custom:region} and more. ``` ---
**Author:** ![buggy](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/buggy/32/177_2.png) [@buggy](https://forum.serverless.com/u/buggy)\ **Post date:** [October 14, 2017, 10:29am UTC](https://forum.serverless.com/t/deploy-lambda-function-into-new-region/2870/7 "2017-10-14T10:29:23Z")
The easiest solution is probably to set it as: ```auto provider: region: ${opt:region, env:AWS_DEFAULT_REGION, 'us-east-1'} ``` Then just use `${self:provider.region}` If you want others then add them into the list. ---
**Author:** ![bill](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/bill/32/1072_2.png) [@bill](https://forum.serverless.com/u/bill)\ **Post date:** [October 14, 2017, 8:16pm UTC](https://forum.serverless.com/t/deploy-lambda-function-into-new-region/2870/8 "2017-10-14T20:16:51Z")
Thanks. How can we let sls know this order without add them as a long list in serverless.yml? looks sls doesn’t support this feature currently. Refer AWS Cli ([http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html#config-settings-and-precedence](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html#config-settings-and-precedence)), could we have the similar feature in SLS? The AWS CLI looks for credentials and configuration settings in the following order: 1. Command line options – region, output format and profile can be specified as command options to override default settings. 2. Environment variables – AWS\_ACCESS\_KEY\_ID, AWS\_SECRET\_ACCESS\_KEY, and AWS\_SESSION\_TOKEN. 3. The AWS credentials file – located at ~/.aws/credentials on Linux, macOS, or Unix, or at C:\Users\USERNAME .aws\credentials on Windows. This file can contain multiple named profiles in addition to a default profile. 4. The CLI configuration file – typically located at ~/.aws/config on Linux, macOS, or Unix, or at C:\Users\USERNAME .aws\config on Windows. This file can contain a default profile, named profiles, and CLI specific configuration parameters for each. 5. Container credentials – provided by Amazon EC2 Container Service on container instances when you assign a role to your task. 6. Instance profile credentials – these credentials can be used on EC2 instances with an assigned instance role, and are delivered through the Amazon EC2 metadata service. I prefer order #1, #2, #3 ---
**Author:** ![buggy](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/buggy/32/177_2.png) [@buggy](https://forum.serverless.com/u/buggy)\ **Post date:** [October 16, 2017, 9:19am UTC](https://forum.serverless.com/t/deploy-lambda-function-into-new-region/2870/9 "2017-10-16T09:19:37Z")
If you want to request a feature you’ll need to submit an issue on the Github project page.