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

[Enhancement]: Adding protocol-details for aws_transfer_server #27695

Closed
maartenschalekamp opened this issue Nov 8, 2022 · 2 comments · Fixed by #28621
Closed

[Enhancement]: Adding protocol-details for aws_transfer_server #27695

maartenschalekamp opened this issue Nov 8, 2022 · 2 comments · Fixed by #28621
Labels
enhancement Requests to existing resources that expand the functionality or scope. good first issue Call to action for new contributors looking for a place to start. Smaller or straightforward issues. service/transfer Issues and PRs that pertain to the transfer service.

Comments

@maartenschalekamp
Copy link

Description

The following resource aws_transfer_server does not have a way to manage the protocol-details. From the documentations

--protocol-details (structure)

    The protocol settings that are configured for your server.

        To indicate passive mode (for FTP and FTPS protocols), use the PassiveIp parameter. Enter a single dotted-quad IPv4 address, such as the external IP address of a firewall, router, or load balancer.
        To ignore the error that is generated when the client attempts to use the SETSTAT command on a file that you are uploading to an Amazon S3 bucket, use the SetStatOption parameter. To have the Transfer Family server ignore the SETSTAT command and upload files without needing to make any changes to your SFTP client, set the value to ENABLE_NO_OP . If you set the SetStatOption parameter to ENABLE_NO_OP , Transfer Family generates a log entry to Amazon CloudWatch Logs, so that you can determine when the client is making a SETSTAT call.
        To determine whether your Transfer Family server resumes recent, negotiated sessions through a unique session ID, use the TlsSessionResumptionMode parameter.
        As2Transports indicates the transport method for the AS2 messages. Currently, only HTTP is supported.

Affected Resource(s) and/or Data Source(s)

aws_transfer_server

Potential Terraform Configuration

protocol_details {
  PassiveIp: "AUTO"
  TlsSessionResumptionMode: "ENFORCED"
  SetStatOption: "ENABLE_NO_OP"
}

References

https://docs.aws.amazon.com/transfer/latest/userguide/API_UpdateServer.html#TransferFamily-UpdateServer-request-ProtocolDetails

Would you like to implement a fix?

No

@maartenschalekamp maartenschalekamp added enhancement Requests to existing resources that expand the functionality or scope. needs-triage Waiting for first response or review from a maintainer. labels Nov 8, 2022
@github-actions
Copy link

github-actions bot commented Nov 8, 2022

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • 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.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@github-actions github-actions bot added the service/transfer Issues and PRs that pertain to the transfer service. label Nov 8, 2022
@justinretzolk justinretzolk added good first issue Call to action for new contributors looking for a place to start. Smaller or straightforward issues. and removed needs-triage Waiting for first response or review from a maintainer. labels Nov 8, 2022
@github-actions
Copy link

github-actions bot commented Apr 7, 2023

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 Apr 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. good first issue Call to action for new contributors looking for a place to start. Smaller or straightforward issues. service/transfer Issues and PRs that pertain to the transfer service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants