-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Support AWS Global Accelerator #6739
Comments
The first resource for managing the accelerator itself, |
The new |
The |
The |
Hi folks 👋 Since general "Support AWS Service X" issues tend to become a collect-all for random feature requests and bug reports, I'm going to close this issue out just to prevent that problem now. There is already a new separate issue to support managing Global Accelerator Endpoint Groups via a new For other Global Accelerator feature requests and bug reports, please file new GitHub issue(s). Thanks! 👍 |
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! |
Community Note
Description
During Re:Invent 2018 AWS Global Accelerator was announced. This feature request is for implementing resources for it in Terraform AWS provider.
New or Affected Resource(s)
Question about dynamic blocks
Let me know what are the AWS provider guidelines regarding working around Terraform dynamic blocks. Since the new Terraform release is just around the corner, do you think it makes sense to create the aws_accelerator_endpoint_configuration meta-resource (does not directly map to AWS API)?
References
The text was updated successfully, but these errors were encountered: