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.

Sign up for GitHub

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

Jump to bottom

Block Device Mapping support for AWS Launch Configurations #865

Closed
jschneiderhan opened this issue Jan 25, 2015 · 3 comments
Closed

Block Device Mapping support for AWS Launch Configurations #865

jschneiderhan opened this issue Jan 25, 2015 · 3 comments

Comments

@jschneiderhan
Copy link
Contributor

It would be nice to be able to specify block_device_mappings for aws_launch_configuration resources.

I'm working on a PR to add support.
@xueshanf
Copy link

See #756. It is accepted as an enhancement.

@jschneiderhan
Copy link
Contributor Author

Oh OK, thanks @xueshanf. I'll close this as a duplicate.

omeid added a commit to omeid/terraform that referenced this issue Mar 30, 2018
@omeid
db_instance: set SourceRegion based on source_db arn.
fe2b112 
As Per AmazonRDS/API/CreateDBInstanceReadReplica docs

		If you create an encrypted Read Replica in a different AWS Region,
		then you must specify a KMS key for the destination AWS Region.
		KMS encryption keys are specific to the AWS Region that they are
		created in, and you can't use encryption keys from one AWS Region
		in another AWS Region.

This commit sets the Read Replica Source Region based on the
replicate_source_db arn.

kms_key_id is managed as usual.
Fixes:  hashicorp#518
Related: hashicorp#3337, hashicorp#865
@ghost
Copy link

ghost commented May 4, 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 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.

@ghost ghost locked and limited conversation to collaborators May 4, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jschneiderhan @xueshanf