This issue was originally opened by @TechnicalMercenary as hashicorp/packer#10435. It was migrated here as a result of the Packer plugin split. The original body of the issue is below.
Description
When I'm building an GCP VMI, a googlecompute builder, I can specify an 'address' which allows an "pre-allocated static external IP address". I do this because a software repo that I'm pulling from is protected by IP whitelist.
I would like something similar in the 'amazon-ebs' builder and the 'azure-arm' builder. I'm pretty sure that both cloud platforms allow a pre-allocated Static IP to be assigned.
AWS has their Elastic IPs
Azure has 'Public IP address'
Use Case(s)
Allow the AMI/VMI being built to have a known IP. This would allow access to external resources that are secured by IP whitelist ( allow list ).
This issue was originally opened by @TechnicalMercenary as hashicorp/packer#10435. It was migrated here as a result of the Packer plugin split. The original body of the issue is below.
Description
When I'm building an GCP VMI, a googlecompute builder, I can specify an 'address' which allows an "pre-allocated static external IP address". I do this because a software repo that I'm pulling from is protected by IP whitelist.
I would like something similar in the 'amazon-ebs' builder and the 'azure-arm' builder. I'm pretty sure that both cloud platforms allow a pre-allocated Static IP to be assigned.
AWS has their Elastic IPs Azure has 'Public IP address'
Use Case(s)
Allow the AMI/VMI being built to have a known IP. This would allow access to external resources that are secured by IP whitelist ( allow list ).
Potential configuration
See the googlecompute documentation for reference
Potential References