No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

config:
  PulumiAwsVpc:data:
    aws:region: us-west-1
    active: true
    vpcName: pulumiVpc
    vpcCidr: 192.168.91.0/24
    wLoadSubnetName: wLoadSubnet01
    vRouterSubnetName: vRouterSubnet01
    wLoadSubnetCidr: 192.168.91.16/28
    vRouterSubnetCidr: 192.168.91.0/28
    vpcSecurityGroupName: pulumiVpcSecurityGroup
    igwName: pulumiIgw
    rtTable : pulumiRtTable
    sgGroup: pulumiSgGroup

You have two options:

1. You can create a separate stack for each region. Given that you need to provide separate CIDRs for each VPC and set of subnets (generally), this may be the best approach.
2. You can create explicit providers in code, and specify their region at that time. This would allow you to create multiple VPCs in different regions in a single stack, but you’ll need to take steps to provide separate CIDRs and such for each region.