By default, the templates deploy in the eu-west-1 AWS Region. If you wish to deploy in any other AWS Region, edit the corresponding setting in the provider.tf file.
In practice changing only the provider.tf region results in errors related to creating VPC endpoints in the eu-west-1 region still:
Expand to See Errors
```bash
│ Error: Error creating VPC Endpoint: InvalidServiceName: The Vpc Endpoint Service 'com.amazonaws.eu-west-1.ssm' does not exist
│ status code: 400, request id: 111bccab-2e0f-4f6e-b257-12ef88e70567
│
│ with aws_vpc_endpoint.spoke_vpc_a_ssm_endpoint,
│ on instances.tf line 83, in resource "aws_vpc_endpoint" "spoke_vpc_a_ssm_endpoint":
│ 83: resource "aws_vpc_endpoint" "spoke_vpc_a_ssm_endpoint" {
│
╵
╷
│ Error: Error creating VPC Endpoint: InvalidServiceName: The Vpc Endpoint Service 'com.amazonaws.eu-west-1.ssmmessages' does not exist
│ status code: 400, request id: ecadf264-e47b-4628-8398-9f2802648c1a
│
│ with aws_vpc_endpoint.spoke_vpc_a_ssm_messages_endpoint,
│ on instances.tf line 94, in resource "aws_vpc_endpoint" "spoke_vpc_a_ssm_messages_endpoint":
│ 94: resource "aws_vpc_endpoint" "spoke_vpc_a_ssm_messages_endpoint" {
│
╵
╷
│ Error: Error creating VPC Endpoint: InvalidServiceName: The Vpc Endpoint Service 'com.amazonaws.eu-west-1.ec2messages' does not exist
│ status code: 400, request id: 53aa1671-6095-48f8-bdd5-4f0eaa355054
│
│ with aws_vpc_endpoint.spoke_vpc_a_ec2_messages_endpoint,
│ on instances.tf line 105, in resource "aws_vpc_endpoint" "spoke_vpc_a_ec2_messages_endpoint":
│ 105: resource "aws_vpc_endpoint" "spoke_vpc_a_ec2_messages_endpoint" {
│
╵
╷
│ Error: Error creating VPC Endpoint: InvalidServiceName: The Vpc Endpoint Service 'com.amazonaws.eu-west-1.ssm' does not exist
│ status code: 400, request id: 374adeff-c710-4148-b045-fbf08dccc7c9
│
│ with aws_vpc_endpoint.spoke_vpc_b_ssm_endpoint,
│ on instances.tf line 116, in resource "aws_vpc_endpoint" "spoke_vpc_b_ssm_endpoint":
│ 116: resource "aws_vpc_endpoint" "spoke_vpc_b_ssm_endpoint" {
│
╵
╷
│ Error: Error creating VPC Endpoint: InvalidServiceName: The Vpc Endpoint Service 'com.amazonaws.eu-west-1.ssmmessages' does not exist
│ status code: 400, request id: f883b8c7-d7b3-4de1-b59f-5733b87c408e
│
│ with aws_vpc_endpoint.spoke_vpc_b_ssm_messages_endpoint,
│ on instances.tf line 127, in resource "aws_vpc_endpoint" "spoke_vpc_b_ssm_messages_endpoint":
│ 127: resource "aws_vpc_endpoint" "spoke_vpc_b_ssm_messages_endpoint" {
│
╵
╷
│ Error: Error creating VPC Endpoint: InvalidServiceName: The Vpc Endpoint Service 'com.amazonaws.eu-west-1.ec2messages' does not exist
│ status code: 400, request id: 5024fa06-3191-4848-aa3d-f1ff10d843f1
│
│ with aws_vpc_endpoint.spoke_vpc_b_ec2_messages_endpoint,
│ on instances.tf line 138, in resource "aws_vpc_endpoint" "spoke_vpc_b_ec2_messages_endpoint":
│ 138: resource "aws_vpc_endpoint" "spoke_vpc_b_ec2_messages_endpoint" {
```
Description
The
README.mdsuggest the following:In practice changing only the
provider.tfregion results in errors related to creating VPC endpoints in theeu-west-1region still:Expand to See Errors
```bash │ Error: Error creating VPC Endpoint: InvalidServiceName: The Vpc Endpoint Service 'com.amazonaws.eu-west-1.ssm' does not exist │ status code: 400, request id: 111bccab-2e0f-4f6e-b257-12ef88e70567 │ │ with aws_vpc_endpoint.spoke_vpc_a_ssm_endpoint, │ on instances.tf line 83, in resource "aws_vpc_endpoint" "spoke_vpc_a_ssm_endpoint": │ 83: resource "aws_vpc_endpoint" "spoke_vpc_a_ssm_endpoint" { │ ╵ ╷ │ Error: Error creating VPC Endpoint: InvalidServiceName: The Vpc Endpoint Service 'com.amazonaws.eu-west-1.ssmmessages' does not exist │ status code: 400, request id: ecadf264-e47b-4628-8398-9f2802648c1a │ │ with aws_vpc_endpoint.spoke_vpc_a_ssm_messages_endpoint, │ on instances.tf line 94, in resource "aws_vpc_endpoint" "spoke_vpc_a_ssm_messages_endpoint": │ 94: resource "aws_vpc_endpoint" "spoke_vpc_a_ssm_messages_endpoint" { │ ╵ ╷ │ Error: Error creating VPC Endpoint: InvalidServiceName: The Vpc Endpoint Service 'com.amazonaws.eu-west-1.ec2messages' does not exist │ status code: 400, request id: 53aa1671-6095-48f8-bdd5-4f0eaa355054 │ │ with aws_vpc_endpoint.spoke_vpc_a_ec2_messages_endpoint, │ on instances.tf line 105, in resource "aws_vpc_endpoint" "spoke_vpc_a_ec2_messages_endpoint": │ 105: resource "aws_vpc_endpoint" "spoke_vpc_a_ec2_messages_endpoint" { │ ╵ ╷ │ Error: Error creating VPC Endpoint: InvalidServiceName: The Vpc Endpoint Service 'com.amazonaws.eu-west-1.ssm' does not exist │ status code: 400, request id: 374adeff-c710-4148-b045-fbf08dccc7c9 │ │ with aws_vpc_endpoint.spoke_vpc_b_ssm_endpoint, │ on instances.tf line 116, in resource "aws_vpc_endpoint" "spoke_vpc_b_ssm_endpoint": │ 116: resource "aws_vpc_endpoint" "spoke_vpc_b_ssm_endpoint" { │ ╵ ╷ │ Error: Error creating VPC Endpoint: InvalidServiceName: The Vpc Endpoint Service 'com.amazonaws.eu-west-1.ssmmessages' does not exist │ status code: 400, request id: f883b8c7-d7b3-4de1-b59f-5733b87c408e │ │ with aws_vpc_endpoint.spoke_vpc_b_ssm_messages_endpoint, │ on instances.tf line 127, in resource "aws_vpc_endpoint" "spoke_vpc_b_ssm_messages_endpoint": │ 127: resource "aws_vpc_endpoint" "spoke_vpc_b_ssm_messages_endpoint" { │ ╵ ╷ │ Error: Error creating VPC Endpoint: InvalidServiceName: The Vpc Endpoint Service 'com.amazonaws.eu-west-1.ec2messages' does not exist │ status code: 400, request id: 5024fa06-3191-4848-aa3d-f1ff10d843f1 │ │ with aws_vpc_endpoint.spoke_vpc_b_ec2_messages_endpoint, │ on instances.tf line 138, in resource "aws_vpc_endpoint" "spoke_vpc_b_ec2_messages_endpoint": │ 138: resource "aws_vpc_endpoint" "spoke_vpc_b_ec2_messages_endpoint" { ```