You must specify an allocation id when mapping an address to a VPC instance
reorg-hhasibul opened this issue · 5 comments
We are getting this error on AWS Centos. we created a brand new VPC.
You must specify an allocation id when mapping an address to a VPC instance (Service: AmazonEC2; Status Code: 400; Error Code: InvalidParameterCombination; Request ID: ****
Same from my side. New VPC created by stack and error during creation:
is there any workaround for this issue?
Any updates on this? Running into this issue as well.
@reorg-hhasibul and @mykhailo-neredko-zaelab I was able to mitigate this by editing the cloudfront template EIP resource.
I added Domain to the Properties attribute of the EIP resource.
...
"EIP": {
"Type": "AWS::EC2::EIP",
"Properties": {
"InstanceId": {
"Ref": "TableauServer"
},
"Domain": "vpc" // add this line. by default domain is "EC2".
}
},
...My problem was running this cloudformation template in a private subnet. The template requires a public subnet but this isn't very practical. I believe this template should default to using a private subnet as that's probably the most common use case.
Thanks for the research @zaqk. Would you like to create a pull request for the change? We can test that through our CI and merge.
Regarding the instance placement in public subnet, the single deployment scenario is meant to be used for demo/testing. If you want something robust, you can checkout the cluster options described here and the corresponding templates in this repo. The cluster version will create instances in the private subnets in 3 AZs and expose a Load Balancer DNS to access the server.