-
Notifications
You must be signed in to change notification settings - Fork 163
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
Failing to run in eu-west-1 #176
Comments
Sorry for the delay 🙏 Could be related but the main issue is the Could you confirm that your authentication does not allow that? |
Hey 👋 No worries! As I say, this was from an Administrator account which can ordinarily manage |
The error on #171 is not that the resource does not exists, but that the Service (ec2, sqs, sms, ses, etc) does not exist on that region and I'm quite sure that The error Using "admin" you should never get one of those errors as you should have access to everything. Either way, speaking with the OPS team we think that a good solution for this would be to log the error but continue importing, so the user knows that some resources did not import due to missing permissions but at least we import everything we can with the given permissions :) That would be a solution that would work in your usecase no? |
Yeah I think this is a good solution 🙌 I'm not quite sure why this error is occurring either. I had the same thought process as you, so assumed it might be something to do with the specific request you were making. I'm definitely using API Gateway in that account anyway and Terraform has no issues with |
The only think we are fetching before the I cannot tell if the error is from that one or not, but it has to be from one of those 2 and the AWS error is just a general We'll go for the solution I mentioned and I'll also open another issue to improve errors when fetching the resources IDs that are more complex than just one call. But what we can agree is that somehow you do not have access to something on that context haha. |
New release https://github.com/cycloidio/terracognita/releases/tag/v0.6.4 fixes it :) |
General information:
Describe the bug:
When running against our AWS account with resources in
eu-west-1
, we get a 403 when terracognita tries to call endpoints in API Gateway. Not only are there no resources in API Gateway in this account, but this is being run with AWSAdministratorAccess, so no permissions issues should occur.I think this could be related to #171, where assumptions about certain resources existing in all regions is not true.
Log message
The text was updated successfully, but these errors were encountered: