Bastions on demand in an AWS VPC

Re:Bastions on demand in an AWS VPC by ldoughty on Tuesday June 23, 2020 @11:02PM (#23623530)

I manage a lot of ec2 instances on dozens of AWS accounts... I can't see a reason to use this particular method... Even if you want to spin up bastion on demand like this, why Fargate, why terraform?

In the simplest form, I'd go with AWS CloudFormation of an EC2 instance. Remove the additional step of an ECS cluster if you don't already have one. An EC2 instance can access cluster VMs, or other VPC objects just as easily. Can it's wrap this in AWS SAM or CloudFormation + a controller like GitLab or Jenkins...

The benefit here is that when you're done, you have an AWS CloudFormation stack to kill... No need for anyone to have teraform installed to find and remove all associated resources.

Of course, this is all if you can't use Systems manager or the CLI to achieve your goals

[ Parent | on HN ]

Re:Bastions on demand in an AWS VPC by brodouevencode on Tuesday June 23, 2020 @11:16PM (#23623622)

> why Fargate

Because it's easy to throw containers at the problem. Coupled with savings plans this can be pretty cheap.

> why terraform

Because it's easier for most than CloudFormation, and has all the benefits of decomposable stacks just like CF.

[ Parent | on HN ]