Skip to content

Conversation

@rudimocnik
Copy link

We've migrated from EC2 Instance Connect to Session Manager for remote management of metrics-ingestor to align with security best practises and eliminated open inbound ports, and cert management. tfsec code scanner reports open ingress port 22 from /0 as CRITICAL severity

Quick facts:

  • Session manager is a component of AWS systems manager.
  • Requires no opening of inbound ports, no jump host, no SSH keys.
  • Connect to ec2 via an interactive one-click browser-based aws console or through the AWS CLI.
  • Centralized access management with IAM roles
  • You need to grant AWS Systems Manager permission to perform actions on your instances. We grant permission, by giving the EC2 permission to assume an IAM service role that contains the AmazonSSMManagedInstanceCore an AWS managed policy.
  • Session Manager requires ec2 to have ssm agent installed.
  • Many ami come with ssm pre-installed

We would suggest adopting similar hardening for metric_ingestor and other v4 components.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants