Terraform-provider-aws: Plans to support more custom endpoints in provider AWS (lambda, apigateway, ...)

[hashibot]

_This issue was originally opened by @ebarault as hashicorp/terraform#16544. It was migrated here as a result of the provider split. The original body of the issue is below._

---

Hi,

Following discussion started in https://github.com/hashicorp/terraform/issues/6535 (which is closed now)

From the doc, it seems that provider AWS does not yet support some endpoints customization in the nested endpoints block such as lambda and apigateway.

e.g.

provider "aws" {
  endpoints {
    s3 = "http://localhost:4572"
    # lambda = ...
    # apigateway = ...
  }
}

I was planning to test localstack against my terraform project but these endpoints are missing currently.

It would be nice to match the localstack service coverage !

Are there plan to add the ability to customize more endpoints in AWS provider?

[kprzerwa-r7]

custom endpoints for more aws services? yes please!

[bflad]

Support for custom endpoints for the below have been released in terraform-provider-aws version 1.7.0. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

• acm
• apigateway
• ecr
• ecs
• lambda
• sts
• route53

[hashibot[bot]]

I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!