1 Answer
- Newest
- Most votes
- Most comments
1
You might be missing the service linked role: https://docs.aws.amazon.com/vpc/latest/ipam/choose-single-user-or-orgs-ipam.html
You can enable it by using the following AWS CLI command: aws iam create-service-linked-role --aws-service-name ipam.amazonaws.com
Kudos to Drew for the answer. ;-)
Relevant content
- asked 3 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated a year ago
Thank you, Brettski, for the help. It works and finally pool deleted successfully.
I have a situation when after account removal from organization: IPAM pool ID still show (Allocations tab) given VPC (Resource ID) with attached deleted account (owner ID) - service linked role exist at delegated IPAM account.
I have the same issue as sebp. Can anyone advise?
@sebp @timd I was able to delete the IPAM Pool without releasing the CIDR first.
We had the same issue related to deleted accounts. IPAM doesn't release the CIDR allocations related to VPCs on a deleted account automatically, and we were unable to manually release the allocations. Accounts had been deleted a long time ago, well past the 90-day post-closure period. Had to contact AWS support and ask them to release the allocations. Support advised us to ignore & release the allocations or delete the VPCs prior to closing accounts in order to avoid this in the future.