Hi Guys,
Is this connector on the horizon for the system? 25% of our estate is in AWS and managing the licence compliance for these is a pain in SNOW. Machines are regularly created/terminated and although we can automate the agent deployment, our compliance is always skewed because of the licencing.
Thanks Mark, but we do not have the automation platform as part of our solution.
I am very interested to find out about the AWS connector in the pipeline! Maybe someone else in the community has information on this?
Are there any updates on the integration with AWS? Our specific problem is compliance for Windows Server since the virtual machines in AWS come with the required license but Snow still allocates our on-premise licenses for these machines.
I notice that the model is set to Elastic Cloud 2 so the inventory agent recognizes the hypervisor. We just need a way to indicate that the license is provided with the machine.
Hi there,
We have a discovery connector that is due for release at the end of this month - it will help you find AWS instances that are in use across the business that you were perhaps not already aware of. There will also be an Azure discovery connector at the same time with the same functionality - to discover Azure instances that were not previously known about.
Then as we traverse into 2018, we will be bringing further functionality to both of these connectors to enable more cost modelling to be applicable and ultimately to ensure that all costs can be brought to bear including those associated with other software licenses that are required for the software that is running within the virtual instances themselves. We will also be adding connectors for Googles Cloud service as well as VMware's technology as we known that this is prevalent in the private cloud environment(s)
I hope that this helps, but please do let me know if you need further clarity.
Many thanks,
Simon.
Hi Simon,
Does the AWS Discovery connector reach AWS RDS instances? My organisation relies on the RDS instance types a lot, which as we all may/may not know - does not support Snow agents.
Apologies in advance if this is a daft question with an easy answer.
Thanks.
- Tyrone
HI there,
I apologise profusely for not noticing this question Tyrone.
In short, today our solution does not hook into the Relational Database Service, however we are considering adding such capability, we just need to determine what information from the service is valuable to an asset manager.
If you are interested to engage with one of my team to help with this work, please let me know and I will connect the dots.
Many thanks,
Simon
Thanks Simon - appreciate the follow up.
Where Oracle and Microsoft permit BYOL models on RDS, it would be useful and centered around the Oracle and Microsoft SQL Server deployments; however, in saying that Microsoft have notified AWS that they are removing the ability/right to use Microsoft licenses on a BYOL model on the AWS RDS service (doesn't impact EC2 deployments). We spotted this 'accidental' announcement on a release document which has subsequently been deleted when we approached Amazon about it and AWS and Microsoft have yet to make an official announcement regarding this topic.
Happy to be assist where I can if you see value in developing something like this..
Hi Simon (and Tyrone)
The information that would be good to capture on RDS via the AWS connector would be:
This should be sufficient to calculate the licence requirement for BYOL deployments.
Thanks, Jonathan
on Jun 27, 2017
Hi Josh,
I am aware that there is already an AWS automation book available for Snow Automation Platform, this lets you automate many of the processes around the provisioning and management of AWS.
https://www.snowsoftware.com/sites/default/files/documents/cloud_iaas_optimization_for_aws_en_screen_0.pdf
I am fairly sure at the Snow Storm event, there was talk of an AWS connector in the pipeline, but I cant find my notes at the moment, so maybe someone else can confirm.