Loading
search-img

AWS

Skip Feed

  1. MercedesO (Flexera Software)

    Edited November 13, 2025 at 8:14 AM

    🚀 Headed to AWS re:Invent? The Hidden Cloudverse awaits! ☁️

     

    Hello Community! 

    Our team will be landing in Las Vegas at AWS re:Invent Dec 1-5!Are you attending the show? We invite you to visit Flexera's Hidden Cloud Lounge to recharge, reconnect, and see the Hidden Cloudverse brought to life:  

     

    • Play the Crew Catcher Game, your chance to win your very own Hidden Cloudverse plushie – who will go home with you, Drizzle, Flash, or Nimbus? 
    • 15-Minute Chair Massages, sips, snacks, and recharge stations  
    • Cloud Expert Chats all day + AMA with our CTO Brian Shannon (Dec 3 | 1:30 PM PST)  

     

    Need a caffeine boost during the show? Grab a drink on us at our coffee takeovers, more details on hiddencloudverse.com.  

    We’d love to know who from the Flexera Community will be there, let us know in the comments (please login to comment) - we’ll send you more info including a calendar invite and make sure you get priority lounge access! 

     

    Image of plushies

    Expand Post
    • 4 comments
    • 1.02K views
    Isayla Aleksandrova-Odongo and Courtney Struthers like this.
    1 of 4

  2. 1 of 3

    • Portal User

      snow will just see it as a virtual machine running in AWS.... works fine in my experience - same as it does in Azure... worth using the AWS SIM connector to discover the VM's you have running in AWS too.

  3. Nishant dhyani asked a question.

    October 30, 2020 at 5:20 AM
    Hyper threading

    Hi,

     

    How to know if any cloud instance has hyper threading enabled or not ? I don't see any dedicated column in SNOW reports.

     

    -Nishant

    Question with a best answer.

    Best Answer

    Hi Nishant,

     

    Apologies for the late reply - I'm not sure if this is still an issue or not - but I'll try to answer to the best of my ability.

     

    I assume that you are using Snow Integration Manager with connector(s) for Microsoft Azure and/or AWS. According to the user guides, we don't collect any information on Hyper-threading with these connectors, instead I would suggest that you install a Snow Agent where applicable to be able to gather more information on the hardware and configuration.

     

    To see what we collect with the connectors, please see the user guides:

    https://community.flexera.com/s/article/UserGuideAmazonAWSDiscoveryConnector

    https://community.flexera.com/s/article/UserGuideAzureDiscoveryConnector

     

    Kind regards,

    ...Stefan

    Expand Post
    Stefan Ahsberg by Stefan Ahsberg (Flexera Software)
    • 1 answer
    • 210 views

    • Portal User

      Hi Nishant,  You will find the fields collected and the mapping in the connector user guides on the Support Portal.  Support Portal - User guide AWS connector    Support Portal - User guide Azure connector   (From what I can see, the subscription ID is not collected, but you might want to check that too.  I am not too familiar with these products.) 

  5. 1 of 2

    • tchoplin

      hi

       

      I am surpsied that we don't have more disucssion on this topic as it becomes more an d more the norm

      and I don't know how to manage this..

      if we deploy snow agent: it generates many new servers in Snow..

      and if all have the same name, they are merged..

      even though it is important to measure licenses in use but for running instances.

       

      in fact an auto scaling group is not really a sinlge sevrer nor a collection of servers

      a new kind of assets...

       

      or servers dynamically created during continuous integration process...

       

      as RDS... for a different reason (but no Snow agent but can be BYOL)

       

       

       

       

      Expand Post

  6. ennorab asked a question.

    October 17, 2018 at 7:00 AM
    How to handle cloud instances that change frequently?

    Hi - new to the world of Snow and SAM, and just getting our organisation up and running with agents etc.

    I'm looking to understand how organisations are tracking their cloud inventory such as AWS instances or Azure VM's. In particular, where the instances are spun up and down on a regular basis through automation. We have, for example, our development environment that has around 200 instances running spun up during the day and are then terminated in the evening. The next day a new set of instances will be spun up with completely new IP's, hostnames, MAC addresses etc.

    This is replicated throughout our environments from test, to pre-production and production (with less frequency of changes to production of course - however we still deploy fortnightly a new release through the CI/CD pipeline).

    I can't see how best to manage this scenario because if all the instances are spun up through automation (from templates) - those templates would have the Snow agent installed and we would soon start to see a LOT of computers showing up in the Snow portal, many of which would no longer be in existence.

    Is it therefore not worth deploying the agents out in this way?

    Does the AWS integration solve this in any way?

    How are you tackling this problem in your environments?

    Should we focus on only keeping a manual tracking of the AMI (templates)?

    I'd appreciate your thoughts and suggestions on this.

    Cheers,

    Baronne

    Expand Post
    • 3 answers
    • 223 views

    • THowland

      Hi Baronne, I certainly don't have all the answers to this, but is something that I am actively researching, investigating and lobbying for. In our situation we have opted not not to deploy Snow agents to AWS and Azure instances with the fear of over-inflating our SLM estate and skewing our compliance picture because this isn't a real-time view. I can tell you that the AWS integration/connector doesn't help because this will only provide you with basic discovery of the instances and not the application installed on those instances. I.e. will return the asset name, etc. but not what is installed on it. It is also restricted by AWS account, so if you have multiple accounts you will need to configure the connector for each AWS account in use. What we are doing at present is leveraging other solutions like Cloud Health to retrieve detailed information about what cloud instances are out there, their usage, configuration, consumption and cost. Other solutions like Tanium are also really good if you want to interrogate what is in use and have a mechanism to manage patching and updates, etc. FYI - I am lobbying for connectors for these types of 3rd party solutions too. Overall, because of the ethereal nature of cloud estates there is still a large proportion of the work that is manual interrogation and interpretation of the software usage. Our organisation is working with Snow and Tanium to try find a solution to this ever present challenge. Hope that helps shed some light - or at a minimum reassure you that you are not alone with this. BR, Tyrone
      Expand Post

  7. riyawilliams

    September 18, 2018 at 7:00 AM

    Is there a place for a REST controller in serverless?

     

    Hai All, Is it redundant to have a REST controller in a servlerss application that has http events? e.g. Imagine a serverless application like this: functions:   hello:     handler: com.sandbox.serverless.Handler::handleRequest     events:        - http:            path: message/hello            method: get Would it be redundant to have the handler method proxy a REST controller? If I had a REST controller, it would do this work: Respond to HTTP event Validate input Invoke business layer function Return response to caller Should I just do this work in the handler function? Regards, Riya. Aws developer
    Expand Post
    • 1 comment
    • 250 views

    • Community Manager (Flexera Software)

      Hi Riya! Not sure I'm following you here... Is this Snow Automation Platform related? If so, would you care to explain a bit more what you are trying to do? //Joakim

  8. THowland asked a question.

    April 26, 2018 at 7:00 AM
    Snow for Cloud appears limited?
    *Apologies in advance if this comes across negative - not intended!* I have read through the User Guides for AWS and Azure Connectors and I am a little puzzled at the information retrieved by the connector... - Name - SiteName - DNSHostName - MACaddress - IPAddress There is nothing related to the software in use - seems a little counterintuitive from a Software Asset Management perspective. Can someone clarify and possible shed light to the value of the connectors because this is information that can be retrieved from AD. Thanks.
    • 2 answers
    • 183 views

    • Community Manager (Flexera Software)

      Hello Tyrone, the wording is the key: discovery. Which means for Snow to only find/see the computers that are out there. The next step, to inventory these, is up to the customer and the software distribution method of choice. If all of your cloud computers are also in your AD, then this information could be duplicated. For customers who however do not have them in their AD, this would be a way to discover not yet inventoried computers. Greetings, Roland
      Expand Post

End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
ARTICLES
11 Posts

Related Topics

    +1.800.374.4353
    CONTACT SALES SUPPORT HUB FLEXERA REVENERA
    © 2026 Flexera. All rights reserved.
    Privacy policy Terms and conditions Revenera Community Help
    Loading
    AWS | Flexera