-
Notifications
You must be signed in to change notification settings - Fork 126
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
Stack fails #201
Comments
I am using the Cloud9 instructions (https://catalog.workshops.aws/observability/en-US/installation/not-using-ee/setup-cloud9) and experienced the same issue. Is there a workaround? |
Same error here when trying to deploy in my own AWS account (not at AWS event) |
Hello @ashishvd1, Can you confirm that we can close out this issue? |
The first stack itself fails.
[ERROR] 2023-02-01T02:54:03.361Z 0d0b484a-a3ce-4481-8b37-a95a6c1b4d29 An error occurred (IncorrectState) when calling the AssociateIamInstanceProfile operation: There is an existing association for instance i-00fd9028cfc49c644
Traceback (most recent call last):
File "/var/task/index.py", line 43, in lambda_handler
response = ec2.associate_iam_instance_profile(IamInstanceProfile=iam_instance_profile, InstanceId=instance['InstanceId'])
File "/var/runtime/botocore/client.py", line 391, in _api_call
return self._make_api_call(operation_name, kwargs)
File "/var/runtime/botocore/client.py", line 719, in _make_api_call
raise error_class(parsed_response, operation_name)
botocore.exceptions.ClientError: An error occurred (IncorrectState) when calling the AssociateIamInstanceProfile operation: There is an existing association for instance i-00fd9028cfc49c644
The text was updated successfully, but these errors were encountered: