You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a question/concern regarding the deployment environment. Since Cloud9 is deprecated for new customers and I don’t have access to Cloud9 in the US East (N. Virginia) (us-east-1) region, I’m limited to using an existing Cloud9 workspace in Canada Central (ca-central-1). However, I understand that Lambda@Edge functions must be deployed from us-east-1, which likely makes deploying from Cloud9 in ca-central-1 problematic.
Given this, would a local deployment from a Linux environment (e.g., using AWS CLI and CDK) work as an alternative to Cloud9? Are there any specific nuances in this project that I should be aware of when switching to a local Linux-based deployment environment?
Thanks!
The text was updated successfully, but these errors were encountered:
Hi, great project!
I have a question/concern regarding the deployment environment. Since Cloud9 is deprecated for new customers and I don’t have access to Cloud9 in the US East (N. Virginia) (
us-east-1
) region, I’m limited to using an existing Cloud9 workspace in Canada Central (ca-central-1). However, I understand that Lambda@Edge functions must be deployed from us-east-1, which likely makes deploying from Cloud9 inca-central-1
problematic.Given this, would a local deployment from a Linux environment (e.g., using AWS CLI and CDK) work as an alternative to Cloud9? Are there any specific nuances in this project that I should be aware of when switching to a local Linux-based deployment environment?
Thanks!
The text was updated successfully, but these errors were encountered: