Use an Elastic IPs w/Secondary IP for Keycloak on a single EC2 instance
General MR
Summary
This introduces a new option -a, for provisioning a Secondary public IP to make it much easier to use both a Public and Passthrough Istio Gateway on a single EC2 without having to spin up two instances / use a MetalLB. When this feature is used, an IPv4 Public Address will not be auto-assigned, but instead two Elastic IPs will be attached.
I submitted a request to AWS to get the limit of 20 EIPs bumped to 100 EIPs (which was approved). This should be more than sufficient given that there are usually not more than 5-10 dev instances up at a time, and likely many people will not use/need this all the time.
Any unattached Elastic IPs will be cleaned up on the next run. I thought about doing this doing this as a shutdown script, however that would require an IAM Instance Profile, which is possible but not sure we want to do that.
Relevant logs/screenshots
N/A
Merge request reports
Activity
assigned to @danny-radiusmethod
added 1 commit
- 350a5be0 - adding feature to deallocate all EIPs for a given user
added 1 commit
- 7a4d6e3b - still use the auto assigned IP if not using secondary IP
added 16 commits
-
3e1fac36...d2637f34 - 4 commits from branch
master - d1db7f87 - script working for passthrough and public on the same ec2 instance
- b94285f2 - optionally create secondary ip
- aae7488e - fixing unix epoch calculation
- d30f0ba9 - fix help condition
- 8ac76627 - some echo tweaks
- 4723be32 - adding feature to deallocate all EIPs for a given user
- d2f3394d - fixing some bugs fod
- 93f4794e - more fixes for k3d cmd
- 04bad1c1 - still use the auto assigned IP if not using secondary IP
- 7dd877c4 - clean up unused elastic ips on each run
- 69871f0e - adding instructions for keycloak
- ae3bbfb8 - adding spacing back
Toggle commit list-
3e1fac36...d2637f34 - 4 commits from branch