Custom service endpoint configuration

[wellsiau-aws]

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
• The resources and data sources in this provider are generated from the CloudFormation schema, so they can only support the actions that the underlying schema supports. For this reason submitted bugs should be limited to defects in the generation and runtime code of the provider. Customizing behavior of the resource, or noting a gap in behavior are not valid bugs and should be submitted as enhancements to AWS via the CloudFormation Open Coverage Roadmap.

Description

Similar to AWS Standard provider, I think it will be useful to have custom service endpoint configuration.

This will allow us to perform test for newly added resources / features ahead of the general availability of the resources schema in the registry.

New or Affected Resource(s)

• all resources (ideally its a service level endpoint)

Potential Terraform Configuration

provider "awscc" {
  # ... potentially other provider configuration ...

  endpoints {
    dynamodb = "http://localhost:4569"
    s3       = "http://localhost:4572"
  }
}

References

• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/custom-service-endpoints

[wellsiau-aws]

@Drewtul is working on it!