Skip to content
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

Transfer server cannot transition from public to an external VPC endpoint #16556

Closed
ghost opened this issue Dec 2, 2020 · 2 comments · Fixed by #17539
Closed

Transfer server cannot transition from public to an external VPC endpoint #16556

ghost opened this issue Dec 2, 2020 · 2 comments · Fixed by #17539
Labels
bug Addresses a defect in current functionality. service/transfer Issues and PRs that pertain to the transfer service.

Comments

@ghost
Copy link

ghost commented Dec 2, 2020

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

Terraform CLI and Terraform AWS Provider Version

Terraform v0.13.5
provider[registry.terraform.io/hashicorp/aws] 3.13.*, 3.13.*, 3.13.*

Affected Resource(s)

  • aws_transfer_server

Terraform Configuration Files

resource "aws_transfer_server" "my_transfer_server" {
  identity_provider_type = "SERVICE_MANAGED"
+   endpoint_type          = "VPC"
+   endpoint_details {
+     subnet_ids             = xxx
+     vpc_id                 = xxx
+     address_allocation_ids = [xxx]
+   }
}

Debug Output

Apologies as I do not have this available to report.

Panic Output

Apologies again, not available to report.

Expected Behavior

The transfer service should use the specified [external] VPC.

Actual Behavior

Apply failed with cannot add Address Allocation ID's at that time.

Steps to Reproduce

  1. Create public endpoint AWS Transfer Family Instance.
  2. Create VPC infrastructure for VPC type transfer family.
  3. Change endpoint type to VPC, passing in the three necessary fields: VPC ID, Subnet IDs, Address Allocation IDs (see + lines above in the configuration file example)

Important Factoids

Workaround: removing the Address Allocation ID's allows an apply to work, but creates an internal resource instead of external. Adding them back after this apply correctly creates the external type and associates the IP Address.

@ghost ghost added the service/transfer Issues and PRs that pertain to the transfer service. label Dec 2, 2020
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Dec 2, 2020
@ewbankkit ewbankkit added bug Addresses a defect in current functionality. and removed needs-triage Waiting for first response or review from a maintainer. labels May 6, 2021
@ewbankkit
Copy link
Contributor

@hh-nharward Thanks for raising this issue.
Whilst looking at merging #13371 I have been taking an in-depth look at this code and think I see the bug (we are not clearing the AddressAllocationIds specified for the UpdateServer call). I will address this as part of the merge.

@github-actions
Copy link

github-actions bot commented Aug 2, 2021

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. service/transfer Issues and PRs that pertain to the transfer service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant