AWS Cloud Operations Blog

Tag: AWS PrivateLink

Securely connect Amazon Managed Grafana to data sources using AWS Transit Gateway and AWS PrivateLink

Securely connect Amazon Managed Grafana to data sources using AWS Transit Gateway and AWS PrivateLink

Introduction Modern businesses rely on data from diverse sources across multiple AWS accounts and regions to gain insights and make critical business decisions. By establishing secure private connections to these data sources metrics, logs, and traces can be visualized from a single pane of glass to enable an end-to-end observability solution. Some customers may have […]

How to grant least privilege access to third-parties on your private EC2 instances with AWS Systems Manager

AWS Systems Manager Session Manager provides a more secure way to manage your Amazon Elastic Compute Cloud (EC2) instances without the need to open inbound ports, maintain bastion hosts, or manage SSH keys. Furthermore, you can use it with a combination of AWS services to give access to external third-parties. Due to business requirements, you […]

Announcing inbound network access control in Amazon Managed Grafana

Many customers that use Amazon Managed Grafana have a need to restrict the Grafana workspace public access and enable fine-grained control to allow which traffic sources can reach the Grafana workspace. Today, we are announcing Amazon Managed Grafana’s new feature that supports inbound network access control. This enables you to secure Grafana workspaces using VPC […]

Amazon EC2 instance port forwarding with AWS Systems Manager

Port forwarding is a useful way to redirect network traffic from one IP address and port number combination to another. With port forwarding, you can access an EC2 instance located in a private subnet from your workstation. In this post, we walk through a use case where customers have a strict security requirement for their […]

How to setup and use AWS OpsWorks for Chef Automate or Puppet Enterprise in an isolated subnet

Introduction For enhanced security, it’s often preferable to place resources in AWS within a subnet with no internet access. Recently, AWS expanded the number of services supported by interface VPC endpoints within the AWS ecosystem, so it’s now easier than ever to run AWS OpsWorks for Chef Automate or AWS OpsWorks for Puppet Enterprise within […]