1 回答
- 最新
- 投票最多
- 评论最多
1
Hello,
Yes, this should be possible with IPAM.
See below note from the documentation:
- Improves public IP addresses utilization across your organization: You can use IPAM to share IP address space across AWS accounts. Without using IPAM, you cannot share your public IP space across AWS Organizations accounts.
Currently Amazon VPC IP Address Manager supports doing this from the accounts via AWSCLI:
aws ec2 provision-public-ipv4-pool-cidr --region us-east-2 --ipam-pool-id ipam-pool-04d8e2d9670eeab21 --pool-id ipv4pool-ec2-09037ce61cf068f9a --netmask-length 27 --profile member-account
Note: I have personally not tested this, please update this thread so it can help others with similar requirements.
Thank you
相关内容
- AWS 官方已更新 10 个月前
- AWS 官方已更新 10 个月前
- AWS 官方已更新 2 年前
- AWS 官方已更新 10 个月前
Thanks for your input. I still think that this step in the doc does mention that the least assignable range is a /24 https://docs.aws.amazon.com/vpc/latest/ipam/tutorials-byoip-ipam-console-ipv4.html#tutorials-byoip-ipam-ipv4-console-3
/24 is the overall least you can bring in, that is correct but with IPAM and AWSCLI you can allocate smaller chunks within different accounts.
Thanks Tushar! I get it now. /24 minimum for the pool, but it can go smaller for a vpc. That part was not very clear when I read it. Much appreciated!