Hot answers tagged

3

Use EC2 instances behind an ELB. Upon launch, your nodes should download and install the latest security updates and do whatever other configuration is necessary to get your application running. As for cycling out your instances, once a day: Create a second EC2 node Wait for it to configure itself and become available Add the second node to the ELB ...


2

If you always have folks leaving & joining, and you care a bit about security you might want to consider multi factor authentication along with Teleport. The 'cluster' concept in Teleport should let users automatically login to new hosts in a cluster with no intervention. You can also specify the duration of SSH keys and create/delete users across ...


1

No one will fake your IP range to get pass a firewall. The only way to do this is easily if your app is all UDP. That said just allowing your office's IP in is the first start. You might want to expand on that as the company grows. Like does everyone in the office need access to the whole AWS VPC? If not then you are looking at site to site VPN connection ...


1

Yes, it can be done. You need to pass the security group identifier (for Security Group A) into the template for Template B as a parameter. From there, you can reference Security Group A in a AWS::EC2::SecurityGroupIngress resource. { "AWSTemplateFormatVersion" : "2010-09-09", "Parameters" : { "SecurityGroupA" : { "Description" :...



Only top voted, non community-wiki answers of a minimum length are eligible