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

DEV-16804 - sets core connect default cloud provider to s3 #43

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,8 @@
# AWS Tamr Config Repo

## v2.7.0 - February 14th 2023
* Sets default Core Connect provider to `S3` in `tamr-config.yml`

## v2.6.0 - September 14th 2022
* Adds variable `emr_security_configuration` that is passed to the config `TAMR_DATASET_EMR_SECURITY_CONFIGURATION`

Expand Down
1 change: 1 addition & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,6 +53,7 @@ This module creates:
| emr\_managed\_master\_sg\_id | Security group ID of the EMR Managed Master Security Group. | `string` | `""` | no |
| emr\_release\_label | The release label for the Amazon EMR release. | `string` | `"emr-5.29.0"` | no |
| emr\_root\_volume\_size | The size, in GiB, of the EBS root device volume of the Linux AMI that is used for each EMR EC2 instance. | `string` | `"10"` | no |
| emr\_security\_configuration | Security configuration to attach to created EMR Spark clusters. Supported in Tamr v2022.009.0 and later. | `string` | `""` | no |
| emr\_service\_access\_sg\_id | Security group ID of EMR Service Access Security Group. | `string` | `""` | no |
| emr\_service\_role\_name | Name of IAM service role for EMR cluster. | `string` | `""` | no |
| emr\_subnet\_id | ID of the subnet where the EMR cluster will be created. | `string` | `""` | no |
Expand Down
1 change: 1 addition & 0 deletions examples/ephemeral-spark/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,7 @@ No requirements.

| Name | Description |
|------|-------------|
| aws-sg-vm | n/a |
| ec2-key | n/a |
| emr-hbase | n/a |
| ephemeral-spark-iam | n/a |
Expand Down
1 change: 1 addition & 0 deletions examples/minimal/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,7 @@ No requirements.

| Name | Description |
|------|-------------|
| aws-sg-vm | n/a |
| ec2-key | n/a |
| elasticsearch | n/a |
| emr | n/a |
Expand Down
3 changes: 3 additions & 0 deletions tamr-config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -60,3 +60,6 @@ TAMR_BACKUP_EMR_CLUSTER_ID: ${tamr_backup_emr_cluster_id}
# DMS Config
APPS_DMS_ENABLED: ${apps_dms_enabled}
APPS_DMS_DEFAULT_CLOUD_PROVIDER: ${apps_dms_default_cloud_provider}

# Core Connect
TAMR_CONNECT_DEFAULT_CLOUD_PROVIDER: S3