Bastion module v1.536.1 not compatible with provider aws 6.x #89
Replies: 1 comment 1 reply
-
Nice catch! The AWS provider version 6 had a breaking change that affected all of our components. As a result we're now upper bound pinning the aws provider version (which is essentially the same as what you did): terraform {
required_version = ">= 1.0.0"
required_providers {
aws = {
source = "hashicorp/aws"
version = ">= 4.0, < 6.0.0" #<----- this line
}
cloudinit = {
source = "hashicorp/cloudinit"
version = ">= 2.2"
}
}
} However, it looks like the release failed for aws-bastion. We will get that fixed! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
When deploying, the aws provider automatically selected version 6. The bastion module uses the aws resource
aws_launch_template
which references argumentelastic_gpu_specification
which is now deprecated in aws provider version 6, but exists in version 5.See https://registry.terraform.io/providers/hashicorp/aws/5.100.0/docs/resources/launch_template#elastic_gpu_specifications-1
This worked for us to get the bastion host component working in the ref architecture.
Hope it helps someone else.
Cheers,
Trung
Beta Was this translation helpful? Give feedback.
All reactions