Skip to content

Unable to plan/apply with a custom CA bundle defined #23224

Description

@repl-mike-roest

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

Terraform v1.1.5
on darwin_amd64

  • provider registry.terraform.io/hashicorp/aws v4.1.0
  • provider registry.terraform.io/hashicorp/random v3.1.0
  • provider registry.terraform.io/integrations/github v4.20.0

Affected Resource(s)

all

Terraform Configuration Files

Any configs

Debug Output

https://gist.github.com/repl-mike-roest/ec6247ad53b59c548a8b0875b69c90d0

Expected Behavior

a plan/apply should work

Actual Behavior

❯ terraform plan
╷
│ Error: error creating AWS SDK v1 session: Error creating AWS session: LoadCustomCABundleError: unable to load custom CA bundle, HTTPClient's transport unsupported type
│ caused by: unsupported transport, http.suppressBadHTTPRedirectTransport
│
│   with provider["registry.terraform.io/hashicorp/aws"],
│   on provider.tf line 1, in provider "aws":
│    1: provider "aws" {
│
╵
❯ terraform apply
╷
│ Error: error creating AWS SDK v1 session: Error creating AWS session: LoadCustomCABundleError: unable to load custom CA bundle, HTTPClient's transport unsupported type
│ caused by: unsupported transport, http.suppressBadHTTPRedirectTransport
│
│   with provider["registry.terraform.io/hashicorp/aws"],
│   on provider.tf line 1, in provider "aws":
│    1: provider "aws" {
│
╵

Steps to Reproduce

  1. terraform apply

Important Factoids

We run a zero trust networking config that requires custom CA bundles to allow for SSL inspection

References

seems potentially related to #23182 as with 4.0.0 I get the same error as in that issue.

using 3.74.2 my custom CA bundle works and I'm able to plan/apply

  • #0000

Metadata

Metadata

Assignees

Labels

bugAddresses a defect in current functionality.providerPertains to the provider itself, rather than any interaction with AWS.regressionPertains to a degraded workflow resulting from an upstream patch or internal enhancement.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions