Closed barthel closed 1 year ago
@mhausenblas, @mahmoud-hafez-aws Combined with #6, this issue becomes a blocker in our organization.
Hello All, The Amazon Managed Grafana team has launched support for VPC connections with your Amazon Managed Grafana workspaces π
Learn more from:
We are also actively collecting user feedback and use cases. If you have any requests or questions regarding the VPC connection feature in Amazon Managed Grafana, feel free to leave a comment here.
Hello All, we expanded the support for Amazon Managed Grafana support for VPC connections in LHR (eu-west-2) and SIN (ap-southeast-1) regions as well upon customers' requests π
Hello Everyone,
Today (2/16/22) Amazon Managed Grafana launch supports for network access control that helps you to restrict network access to your Grafana workspaces!
Check out the What's New post, blog, or user guide on how to use VPC endpoints and customer-managed prefix lists to protect your Grafana workspace from network attacks.
You can also create an interface VPC endpoints to allow AWS resources such as Amazon EC2 instances to access the Amazon Managed Grafana API to manage resources, or you can use a VPC endpoint as part of limiting network access to your Amazon Managed Grafana workspaces. π
Hello @mengdic ,
May I know the schedule for supporting the vpc connection for the Seoul region(ap-northeast-2)?
Hi there. But is it possibile to access Managed Grafana Console from the On-premises through direct connect and so VPC Endpoints? I'm getting "Not Found" error. Any idea?
In my organization, services that are only publicly accessible are not welcome and cause additional configuration effort or simply do not work with other services that are only accessible via the VPC.
We (urgently) need the ability to include Grafana with a VPC endpoint to allow access to (for example) AWS OpenSearch (with VPC endpoint). In combination with the support of Custom Domains (#6) the implementation should work similar to AWS OpenSearch.