Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

stacks which use EdgeFunctions must have an explicitly set region #1725

Closed
rnrnstar2 opened this issue Jul 7, 2024 · 1 comment
Closed
Labels
pending-triage Incoming issues that need categorization

Comments

@rnrnstar2
Copy link

Environment information

System:
  OS: macOS 12.7.3
  CPU: (4) x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
  Memory: 40.34 MB / 8.00 GB
  Shell: /bin/zsh
Binaries:
  Node: 20.14.0 - ~/.nvm/versions/node/v20.14.0/bin/node
  Yarn: undefined - undefined
  npm: 10.7.0 - ~/.nvm/versions/node/v20.14.0/bin/npm
  pnpm: undefined - undefined
NPM Packages:
  @aws-amplify/backend: 1.0.0
  @aws-amplify/backend-cli: 1.0.1
  aws-amplify: 6.3.8
  aws-cdk: Not Found
  aws-cdk-lib: Not Found
  typescript: 5.4.5
AWS environment variables:
  AWS_PROFILE = rnrnstar-us
  AWS_STS_REGIONAL_ENDPOINTS = regional
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
No CDK environment variables

Description

I tried to create an EdgeFunction with cdk, but the following error occurred because backend.createStack does not allow you to set the region.

Unable to build the Amplify backend definition.

Caused By: Error: stacks which use EdgeFunctions must have an explicitly set region
at EdgeFunction.createCrossRegionFunction (/Users/suzumuradaichi/github/MiracleLinkMaker/node_modules/aws-cdk-lib/aws-cloudfront/lib/experimental/edge-function.js:1:7079)

Resolution: Check your backend definition in the amplify folder for syntax and type errors.

@rnrnstar2 rnrnstar2 added the pending-triage Incoming issues that need categorization label Jul 7, 2024
@ykethan
Copy link
Member

ykethan commented Jul 8, 2024

Hey @rnrnstar2, thank you for reaching out. The issue is currently being tracked on #1663. PR providing additional information on this: #1675
Closing this issue as duplicate.

@ykethan ykethan closed this as not planned Won't fix, can't repro, duplicate, stale Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending-triage Incoming issues that need categorization
Projects
None yet
Development

No branches or pull requests

2 participants