resteq.blogg.se - Splunk news amazon

#SPLUNK NEWS AMAZON HOW TO#
#SPLUNK NEWS AMAZON TRIAL#
#SPLUNK NEWS AMAZON DOWNLOAD#
#SPLUNK NEWS AMAZON FREE#

The number of WorkSpaces that returned an unhealthy status. The number of WorkSpaces that are stopped. The amount of time it takes to initiate a WorkSpaces session. The number of connections that were closed, including user-initiated and failed connections. The number of WorkSpaces that are under maintenance. The round trip time between the WorkSpaces client and the WorkSpace. The number of WorkSpaces that returned a healthy status. You can choose to do this alongside the DirectoryId level metrics or use Splunk to aggregate the values across the virtual workstations to get the big picture. If you want to be able to identify issues at the workstation level (for instance, which workstations are experiencing high latency) then consider ingesting the data at the WorkstationId level. The table below suggests a metric setup that will allow for a comprehensive view across the estate. The table below shows this scenario for an environment with three virtual desktops: CloudWatch “Available” metric with both WorkspaceId and DirectoryId dimensionsĪs we can see above, decisions need to be made on each metric in terms of at which level to ingest the data (per WorkspaceId or per DirectoryId), and then also which aggregate function works best for that metric. For example, the “Available” metric will return the details on all of the virtual workstations if the WorkspaceId dimension is used, or a summary of the entire estate if DirectoryId is used. Most of the AWS CloudWatch Metrics are available at the DirectoryId or the WorkspaceId dimension level but not both. Warning: The default settings result in no data being ingested

The Splunk Add-on populates the Dimension settings as shown below:ĪWS/WorkSpaces Input – Default Metrics Configuration.

Namespace = AWS/WorkSpaces (select from list and hit Enter).

Also, remove any Dimensions in the right-hand section.Īs AWS/WorkSpaces is not one of the listed namespaces you need to add it manually: For this test, remove all of the namespaces from the left-hand side by clicking on the ‘x’. The default Metrics Configuration is set up to ingest from various namespaces.

Metrics Configuration – click Edit in Advanced Mode.

AWS Regions = the region(s) your WorkSpaces run in.

Setup the Input to ingest Amazon WorkSpaces CloudWatch Metrics Setup the account from the Configuration tab in the add-on:

Access the user and click on the Security credentials tab – from here you can create an access key and secret that you will use when setting up the connect in the Splunk Add-on for AWS.

The user now has access to hit the AWS API and retrieve CloudWatch metrics.

Create Policy: CloudWatchMetrics (use the policy below to grant access to all CloudWatch metrics).

Create a group – SplunkCloudWatchMetrics.

Add User (splunk) with programmatic access.

It does this as a user, using a Access and Secret Key to authenticate. The Splunk Add-on for AWS will poll the AWS APIs to collect CloudWatch metric data.

#SPLUNK NEWS AMAZON DOWNLOAD#

They will need to download the client appropriate for the OS they are using on their physical machine.

#SPLUNK NEWS AMAZON HOW TO#

(to see if it shows up in the data later)Įmails will be sent to the test users explaining how to connect.

#SPLUNK NEWS AMAZON FREE#

AutoStop was chosen as it is Free Tier eligible.

Select Bundle – here you can match your users to OS and connection protocols, for testing I chose:.

Select a Directory – defaults should be fine.

Click on the WorkSpaces option then “Launch WorkSpaces”.

Create Directory – took around 20 mins to get to the ready state.

#SPLUNK NEWS AMAZON TRIAL#

Review – note that there are 30 days of trial usage, remember to delete resources after the test to avoid charges.

stick with the default or use a suitable VPC/subnet if appropriate.

Set up Directory: AWS Managed Microsoft AD: Standard Edition.

Building the POC environment Setting up Amazon WorkspacesĪWS are currently offering up to 50 free users on Amazon WorkSpaces.

Amazon WorkSpaces (AWS/Workspaces) is not set up by default, but it can be added as we show here. Out of the box, the Add-on provides templated support for a number of common AWS CloudWatch metric namespaces such as AWS/EC2, AWS/RDS, AWS/Billing, AWS/ApiGateway and more. For monitoring use cases CloudWatch Metrics provide a great way to pull the AWS resource-specific metrics into Splunk. The “Splunk Add-on for AWS” allows you to pull data in various ways from AWS.

There are various routes that can be used to bring the data in. Splunk is brilliant at ingesting data from AWS. VDI provides a secure way to enable home working, ensuring that staff are working from secure and compliant desktop machines, accessed via a remote connection from whatever physical machine they have at home. Amazon Workspaces is a “Desktop-as-a-Service” or Virtual Desktop Infrastructure (VDI) capability from the AWS cloud.