Clarify us-east-1 requirement #50
Assignees
Comments
|
Can we just replicate the snapshot to all the other regions and then have a conditional inside the Pulumi program to pull the right one depending on the region? |
AaronFriel
added a commit
to AaronFriel/aws-reference-architecture-pulumi
that referenced
this issue
Nov 28, 2023
This gives users a reliable experience when switching stacks or shells. The Pinecone API key, environment name, and index are stored in the Pulumi config. The AWS region is explicitly configured, ensuring that local profile settings or env vars do not impact deployment success, as described in [pinecone-io#50](pinecone-io#50).
AaronFriel
added a commit
that referenced
this issue
Nov 28, 2023
This gives users a reliable experience when switching stacks or shells. The Pinecone API key, environment name, and index are stored in the Pulumi config. The AWS region is explicitly configured, ensuring that local profile settings or env vars do not impact deployment success, as described in [#50](#50).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For the time being, because the public RDS snapshot that is shared amongst RefArch users is pinned to us-east-1, the RefArch can only be deployed in us-east-1.
We should initially update the docs to make this more clear and figure out a strategy to support other regions going forward.
The text was updated successfully, but these errors were encountered: