Support eu-west-3 region

[mimccio]

Please add support for eu-west-3 (Paris) region.

[sammartinez]

Hello @mimccio, Amplify JS interacts with the Amplify CLI. Are you calling out for support within the CLI? Please let us know. cc @renebrandel for awareness.

[mimccio]

Hi @sammartinez,
Yes when we initiate a new amplify project in the CLI there is no choice for eu-west-3.
Thanks :)

[jeromeheissler]

I have setup a project with a profile in eu-west-3. All the project has been created in the correct region. But when i tried to deploy it with the Amplify Console the build failed with message : "Amplify service is not available in the region eu-west-3"

                                 # Starting phase: build
                                 # Executing command: amplifyPush --simple
2020-12-22T14:44:56.572Z [INFO]: 
2020-12-22T14:44:56.574Z [INFO]: �[0mFor more information on AWS Profiles, see:�[0m
                                 �[0mhttps://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html�[0m
                                 �[31mAmplify service is not available in the region eu-west-3�[39m
2020-12-22T14:44:56.575Z [INFO]: �[31mFailed to pull the backend.�[39m
2020-12-22T14:44:56.577Z [INFO]: �[31mAmplify service is not available in the region eu-west-3�[39m
2020-12-22T14:44:56.579Z [INFO]: �[0mError: Amplify service is not available in the region eu-west-3�[0m
                                 �[0m    at Object.run (/root/.nvm/versions/node/v12.19.0/lib/node_modules/@aws-amplify/cli/node_modules/amplify-provider-awscloudformation/src/attach-backend.js:63:11)�[0m
                                 �[0m    at processTicksAndRejections (internal/process/task_queues.js:97:5)�[0m
                                 �[0m    at Object.attachBackend (/root/.nvm/versions/node/v12.19.0/lib/node_modules/@aws-amplify/cli/node_modules/amplify-provider-awscloudformation/src/index.ts:37:3)�[0m
                                 �[0m    at Object.queryProvider (/root/.nvm/versions/node/v12.19.0/lib/node_modules/@aws-amplify/cli/src/attach-backend-steps/a10-queryProvider.ts:12:3)�[0m
                                 �[0m    at Object.attachBackend (/root/.nvm/versions/node/v12.19.0/lib/node_modules/@aws-amplify/cli/src/attach-backend.ts:20:5)�[0m
                                 �[0m    at Object.exports.run (/root/.nvm/versions/node/v12.19.0/lib/node_modules/@aws-amplify/cli/src/commands/pull.ts:57:5)�[0m
                                 �[0m    at Object.executeAmplifyCommand (/root/.nvm/versions/node/v12.19.0/lib/node_modules/@aws-amplify/cli/src/index.ts:256:5)�[0m
                                 �[0m    at executePluginModuleCommand (/root/.nvm/versions/node/v12.19.0/lib/node_modules/@aws-amplify/cli/src/execution-manager.ts:181:3)�[0m
                                 �[0m    at Object.executeCommand (/root/.nvm/versions/node/v12.19.0/lib/node_modules/@aws-amplify/cli/src/execution-manager.ts:28:5)�[0m
                                 �[0m    at Object.run (/root/.nvm/versions/node/v12.19.0/lib/node_modules/@aws-amplify/cli/src/index.ts:105:5)�[0m
2020-12-22T14:44:56.596Z [ERROR]: !!! Build failed
2020-12-22T14:44:56.597Z [ERROR]: !!! Non-Zero Exit Code detected
2020-12-22T14:44:56.597Z [INFO]: # Starting environment caching...
2020-12-22T14:44:56.597Z [INFO]: # Environment caching completed
Terminating logging...

[Yaskomega]

Thank you @mimccio , I was about to create a issue for this !

As you can see, we don't have eu-west-3 among the available choices.
Is it possible to deploy in eu-west-3 ?
Can you please add the eu-west-3 choice if so ?
@jeromeheissler what command are you using please ?

[lePaulo]

@Yaskomega: as a workaround, you can define an aws profile with the aws cli, and avoid the command amplify configure.
@jeromeheissler: as a workaround in Amplify Console, you can edit build settings and apply the following template (replace dev by your environment name):

version: 1
backend:
  phases:
    build:
      commands:
        - '# Execute Amplify CLI with the helper script'
        - amplify init --amplify "{\"envName\":\"dev\"}" --yes
        - amplify push --yes
frontend:
  phases:
    preBuild:
      commands:
        - npm ci
    build:
      commands:
        - npm run build
  artifacts:
    baseDirectory: build
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*

[rubab]

@lePaulo I tried with aws cli but app didn't deploy on Paris region. Could you please guide me?

[mitmol]

Hello,

In the amplify app dashboard, I have the "frontend environment tab, but not the backend tab. The amplify support is not total in region eu-west-3 ?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed because of inactivity. Please open a new issue if you are still encountering problems.

[martijnwiekens]

I have the same problem. Can't deploy to eu-west-3. Same message.
With Amplify cli 5.0.2

[lambda0xff]

When trying to amplify pull I get "Amplify service is not available in the region eu-west-3. Failed to pull the backend. Amplify service is not available in the region eu-west-3"

Shouldn't this issue be reopened ? And also, maybe the docs should make it clear that the CLI is not available for all regions ? Could have saved me some time ...

[drekorig]

Same problem with Amplify cli 5.1.2

[Emmanuel-D-coface]

We need to configure a cloudfront hosting to an Amplify project hosted in zone eu-west-3.

This Amplify project was created via the console interface since the Amplify CLI does not support eu-west-3 as a region (even the latest version ) which is a strange inconsistency , if it's allowed with the console it should be added to the CLI too especially if some actions ARE NOT POSSIBLE through the console...

But the hosting is not configurable via the console , only the CLI , could you allow the CLI to support eu-west-3 ?
Thanks for the support

[laisnegautier]

I created a SSR project (with NuxtJS) with amplify configured in eu-west-3 by not using "amplify configure", but just "amplify init" with a eu-west-3 configured profile. With this, it's possible to add api and auth in the region etc... But there are issues in the console (for the hosting part) which doesn't build my backend because amplify cli doesn't support eu-west-3.

Sticking to static generation and workaround for now then.

[alexduros]

Same here ! Not able to deploy a SSR project un eu-west-3 as amplify CLI is not available there.
Not completely clear for me on what is missing on AWS part to open it (as the service is already available in static mode) .
Please add eu-west-3 🙏

[magrinj]

It's been almost a year now just to add a region in the cli... sounds crazy 🤨

[magrinj]

Not really sure of the change, but I've tried locally and it seems to work, I've made a PR here : #8056

[sebsto]

Another customer asking for AWS Amplify support in eu-west-3 #7794

[rudyhadoux]

I confirm.

[rudyhadoux]

Does it take ten years to add a region ?

[rudyhadoux]

Why is it closed ?????

[jhockett]

Hi @rudyhadoux, the issue was closed automatically because a linked PR was merged. It will be included in the next release!

[rudyhadoux]

Good news.

[github-actions]

This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.