-
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
[New Resource]: aws_ec2_instance_connect_endpoint #32011
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Thanks for raising this issue, I'm picking it up 👍🏼 |
@bschaatsbergen , Thanks for taking it up .. |
Feel free to continue @debojitmegaco :), I'll close my draft PR if necessary. |
Hey guys, do we have an ETA for this? |
PR testing is in Progress..Will keep you posted |
It's worth putting the draft out already for early feedback @debojitmegaco |
Not sure how the process is, just confused that the issue is closed without a release and the resource can also not yet be found in the terraform documentation. Where can one find the currant status about this? |
@TarSzator the work is completed under #31858 and scheduled to be released soon. |
@TarSzator The release is scheduled for Thursday. |
@TarSzator you can get ready for it in the meantime. The documentation is here: https://github.com/hashicorp/terraform-provider-aws/blob/main/website/docs/r/ec2_instance_connect_endpoint.html.markdown |
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
An EC2 Instance Connect Endpoint allows you to connect to an instance, without requiring the instance to have a public IPv4 address. With EC2 Instance Connect Endpoint (EIC Endpoint), customers now have SSH and RDP connectivity to their EC2 instances without using public IP addresses. In past, customers assigned public IPs to their EC2 instances for remote connectivity. With EIC Endpoints, customers can have remote connectivity to their instances in private subnets, eliminating the need to use public IPv4 addresses for connectivity.
Requested Resource(s) and/or Data Source(s)
aws_ec2_instance_connect_endpoint
Potential Terraform Configuration
References
API reference: https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateInstanceConnectEndpoint.html
API docs: https://github.com/aws/aws-sdk-go-v2/blob/main/service/ec2/api_op_CreateInstanceConnectEndpoint.go
User Guide: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Connect-using-EC2-Instance-Connect-Endpoint.html
Would you like to implement a fix?
Yes
The text was updated successfully, but these errors were encountered: