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

aws_macie_member_account_association tries to call macie.region.amazonaws.com, but that hostname doesn't resolve in DNS externally #10172

Closed
scumola opened this issue Sep 19, 2019 · 5 comments
Labels
service/macie Issues and PRs that pertain to the macie service.
Milestone

Comments

@scumola
Copy link

scumola commented Sep 19, 2019

Not really sure if this is a terraform issue (should it be calling a different endpoint?) or an AWS issue (should macie.region.amazonaws.com resolve externally?) or can this just not be run outside of AWS maybe?

aws_macie_member_account_association tries to call macie.region.amazonaws.com, but that hostname doesn't resolve in DNS externally.

$ host macie.us-east-2.amazonaws.com
Host macie.us-east-2.amazonaws.com not found: 3(NXDOMAIN)

The error from Terraform:

Error: Error creating Macie member account association: RequestError: send request failed
caused by: Post https://macie.us-east-2.amazonaws.com/: dial tcp: lookup macie.us-east-2.amazonaws.com on mydns.domain.com:53: no such host

I've checked DNS in several locations and it doesn't resolve external to AWS at all from anywhere.

@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Sep 19, 2019
@ewbankkit
Copy link
Contributor

@scumola According to the AWS documentation. Amazon Macie is currently only available in the us-east-1 and us-west-2 regions.
For other regions (e.g. us-east-2 as in your example) the no such host error is expected.

@DrFaust92 DrFaust92 added the service/macie Issues and PRs that pertain to the macie service. label May 21, 2020
@justinretzolk
Copy link
Member

Hey @scumola 👋 Thank you for taking the time to file this issue! Given the comment above, and that there's been a number of AWS provider releases since you initially filed it, can you confirm whether you're still experiencing this behavior?

@justinretzolk justinretzolk added waiting-response Maintainers are waiting on response from community or contributor. and removed needs-triage Waiting for first response or review from a maintainer. labels Dec 9, 2021
@jar-b
Copy link
Member

jar-b commented May 23, 2023

Closed by #31058, merged to main via #31392

@jar-b jar-b closed this as completed May 23, 2023
@jar-b jar-b added this to the v5.0.0 milestone May 23, 2023
@github-actions github-actions bot removed the waiting-response Maintainers are waiting on response from community or contributor. label May 23, 2023
@github-actions
Copy link

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

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
service/macie Issues and PRs that pertain to the macie service.
Projects
None yet
Development

No branches or pull requests

5 participants