-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
[Enhancement]: aws_mwaa_environment output webserver_vpc_endpoint_service and database_vpc_endpoint_service #36085
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Warning This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
This functionality has been released in v5.46.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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. |
Description
When creating a new environment with endpoint_management set to CUSTOMER.
The next step would have been to use aws_vpc_endpoint to create the webserver and database endpoint. However these 2 properties are not in the output.
Affected Resource(s) and/or Data Source(s)
aws_mwaa_environment
Potential Terraform Configuration
No response
References
AWS CLI does output these properties https://docs.aws.amazon.com/cli/latest/reference/mwaa/get-environment.html
Would you like to implement a fix?
Yes
The text was updated successfully, but these errors were encountered: