You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that the VPC has instance_tenancy set to default and the first aws_instance resource has tenancy set to default while the second aws_instance resource has tenancy set to dedicated.
I verified the tenancy via the AWS console and it works as expected. It would be really useful to update the docs to include this field. I would do so and open a PR, but I do not know where/if the docs are on GitHub (I did look).
The text was updated successfully, but these errors were encountered:
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
locked and limited conversation to collaborators
Apr 29, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The
aws_instance
resource supports thetenancy
field, but it is not documented.See the gist here: https://gist.github.com/conorgil/76f8959d674270228f0c
Note that the VPC has
instance_tenancy
set todefault
and the firstaws_instance
resource hastenancy
set todefault
while the secondaws_instance
resource hastenancy
set todedicated
.I verified the tenancy via the AWS console and it works as expected. It would be really useful to update the docs to include this field. I would do so and open a PR, but I do not know where/if the docs are on GitHub (I did look).
The text was updated successfully, but these errors were encountered: