Both are showing the same region. "US West (California, USA)" in the console and "us-west2" in the CLI are the same region, as documented in our regions reference where "us-west2" is the region identifier for "US West (California, USA)".

Argh! Why would you create your own region identifiers? Even worse that they are so similar to the AWS region identifiers. https://docs.aws.amazon.com/global-infrastructure/latest/regions/aws-regions.html

Frustration aside – I guess this question just changed. When will you have AWS us-west-2 Oregon support for railway service deployments? I am asking because I am trying to consolidate my railway services, buckets, and supporting MongoDB into the same region.

We use our own region identifiers, not AWS region codes. Our "US West" region (us-west2) is in California, not Oregon. We don't currently have an Oregon region. The available regions are listed at docs.railway.com/deployments/regions, and additional regions may be added in the future, but we don't have a timeline to share for a specific Oregon/us-west-2 equivalent.

I understand your strategic desires to have your own identifiers since that decouples your APIs from AWS', but the similarity is an easy source of confusion.

Regardless, thanks for the update. Please consider an Oregon region for the future. If there's some place I can +1, I'll do so.