2개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
0
I get the same error in the same region, and I'm wondering if it's because I'm trying it with a brand new instance that isn't registered with an OpsWorks stack (and I'm not able to register a new stack because OpsWorks is EOL https://docs.aws.amazon.com/opsworks/latest/userguide/stacks-eol-faqs.html ).
Is your instance registered to an existing OpsWorks stack?
Using aws ec2
rather than aws opsworks
is fine using the same instance and EIP, but I'm guessing you have a good reason for wanting to use OpsWorks.
$ aws opsworks --region ap-southeast-2 associate-elastic-ip --instance-id i-0635149fxyzxyzxyz --elastic-ip 13.x.y.z
An error occurred (ResourceNotFoundException) when calling the AssociateElasticIp operation: Unable to find elastic ip with ID 13.x.y.z
$ aws ec2 associate-address --region ap-southeast-2 --instance-id i-0635149fxyzxyzxyz --public-ip 13.x.y.z
{
"AssociationId": "eipassoc-0f5ceba5xyzxyzxyz"
}
$
0
Steve, While you didn't solve the opsworks problem, you did show me that I overlooked the obvious solution in ec2 associate-address. So thanks very much.
jon
답변함 10달 전
관련 콘텐츠
- AWS 공식업데이트됨 3년 전