Skip to content

[Enhancement]: DMS with Postgres Source and Redshift Target - map_boolean_as_boolean to be supported in redshift_settings  #40423

Closed as duplicate of#38814
@merkeb-de

Description

Description

The AWS DMS Documentation for a replication from Postgres to Redshift states that for mapping Boolean from Postgres to Boolean data type in Redshift the MapBooleanAsBoolean must be applied in both source and target endpoint.

However, the terraform equivalent key for that map_boolean_as_boolean is only supported in the postgres_settings but not in redshift_settings. This causes boolean data type to be mapped to varchar(1) data type.

The Error log while including the key in redshift_settings

Error: Unsupported argument

│ on ../modules/dms/end-points.tf line 36, in resource "aws_dms_endpoint" "redshift_dms_postgres_target_endpoint":
│ 36: map_boolean_as_boolean = true #--redshift-settings '{"MapBooleanAsBoolean": true}'

│ An argument named "map_boolean_as_boolean" is not expected here.

Aws Doc link stating it has to be included in both target and source

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

Resource - aws_dms_endpoint
Argument - redshift_settings

Potential Terraform Configuration

resource "aws_dms_endpoint" "redshift_dms_postgres_target_endpoint" {
redshift_settings {
map_boolean_as_boolean = true # New Key requested 
}
}

References

Using the MapBooleanAsBoolean PostgreSQL endpoint setting

Using the MapBooleanAsBoolean in Redshift Settings

Would you like to implement a fix?

None

Metadata

Assignees

No one assigned

    Labels

    enhancementRequests to existing resources that expand the functionality or scope.good first issueCall to action for new contributors looking for a place to start. Smaller or straightforward issues.service/dmsIssues and PRs that pertain to the dms service.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions