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

Feature Request: Please add s3 as an engine type for DMS endpoints #2165

Closed
gevansBigG opened this issue Nov 2, 2017 · 4 comments
Closed
Labels
enhancement Requests to existing resources that expand the functionality or scope.
Milestone

Comments

@gevansBigG
Copy link

Please add support for S3 as a dms endpoint. See: http://docs.aws.amazon.com/dms/latest/userguide/CHAP_Target.S3.html
https://github.com/aws/aws-sdk-go/blob/master/service/databasemigrationservice/api.go

Terraform Version: All

Affected Resource(s):aws_dms_endpoint

Expected Behavior:

User should be able to specify S3 as the engine_name argument. As a result of this, most of the other arguments will become optional, and some new arguments will need to be created: bucket_name, bucket_folder, table_structure and CDC path (optional).

@paddycarver paddycarver added the enhancement Requests to existing resources that expand the functionality or scope. label Nov 21, 2017
@altay13
Copy link

altay13 commented Dec 11, 2017

Hey @gevansBigG this is already added and waiting for merge
@paddycarver
#1685

@bflad
Copy link
Contributor

bflad commented May 7, 2018

Support has been merged in via #1685 and #4447 and will release in v1.18.0 of the AWS provider in two days.

@bflad bflad closed this as completed May 7, 2018
@bflad
Copy link
Contributor

bflad commented May 10, 2018

This has been released in version 1.18.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

@ghost
Copy link

ghost commented Apr 6, 2020

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!

@ghost ghost locked and limited conversation to collaborators Apr 6, 2020
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.
Projects
None yet
Development

No branches or pull requests

5 participants