Skip to content

Conversation

forevermatt
Copy link
Contributor

Added

  • Add GlobalTable replica in secondary region (defaulting to us-west-2)
  • Add the required StreamSpecification GlobalTable property
    • I don't know whether we use this at all, but in case the way we back up the data uses the stream, I set it to send the new value. Documentation is here.

@forevermatt forevermatt requested a review from a team May 23, 2023 20:27
u2fTable: ${self:custom.namespace}_u2f
dev_env: staging
prod_env: production
secondaryRegion: ${env:AWS_REGION_SECONDARY, "us-west-2"}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just verifying if this is correct to default to.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep. I believe our current general plan is to put our primary AWS infrastructure in us-east-2 (to reduce the chances of both our infrastructure and the us-east-1 control planes being down at the same time) and to put our secondary infrastructure in us-west-2 (because it's cheaper than us-west-1). Thanks for checking.

@forevermatt forevermatt merged commit b4c5f93 into develop May 24, 2023
@forevermatt forevermatt deleted the feature/add-secondary-region-to-global-table branch May 24, 2023 14:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants