You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/chaos-studio/chaos-studio-configure-customer-managed-keys.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Configure customer-managed keys (preview) for experiment encryption
2
+
title: Configure customer-managed keys [preview] for experiment encryption
3
3
titleSuffix: Azure Chaos Studio
4
4
description: Learn how to configure customer-managed keys (preview) for your Azure Chaos Studio experiment resource using Azure Blob Storage
5
5
services: chaos-studio
@@ -10,7 +10,7 @@ ms.date: 10/06/2023
10
10
ms.topic: how-to
11
11
---
12
12
13
-
# Configure customer-managed keys (preview) for Azure Chaos Studio using Azure Blob Storage
13
+
# Configure customer-managed keys [preview] for Azure Chaos Studio using Azure Blob Storage
14
14
15
15
Azure Chaos Studio automatically encrypts all data stored in your experiment resource with keys that Microsoft provides (service-managed keys). As an optional feature, you can add a second layer of security by also providing your own (customer-managed) encryption key(s). Customer-managed keys offer greater flexibility for controlling access and key-rotation policies.
Copy file name to clipboardExpand all lines: articles/chaos-studio/chaos-studio-private-link-agent-service.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,8 +9,8 @@ ms.author: nikhilkaul
9
9
ms.service: chaos-studio
10
10
ms.custom: ignite-fall-2023
11
11
---
12
-
# How-to: Configure Private Link for Agent-Based experiments
13
-
This guide explains the steps needed to configure Private Link for a Chaos Studio **Agent-based** Experiment. The current user experience is based on the private endpoints support enabled as part of public preview of the private endpoints feature. Expect this experience to evolve with time as the feature is enhanced to GA quality.
12
+
# How-to: Configure Private Link for Agent-Based experiments[Preview]
13
+
This guide explains the steps needed to configure Private Link for a Chaos Studio **Agent-based** Experiment[Preview]. The current user experience is based on the private endpoints support enabled as part of public preview of the private endpoints feature. Expect this experience to evolve with time as the feature is enhanced to GA quality, as it is currently in **preview**.
14
14
15
15
---
16
16
## Prerequisites
@@ -234,6 +234,8 @@ Example of updated agentInstanceConfig.json:
234
234
235
235
**IF** you blocked outbound access to Microsoft Certificate Revocation List (CRL) verification endpoints, then you need to update agentSettings.JSON to disable CRL verification check in the agent.
236
236
237
+
By default this field is set to **true**, so you can either remove this field or set the value to false. See [here](chaos-studio-tutorial-agent-based-cli.md) for more details.
Copy file name to clipboardExpand all lines: articles/chaos-studio/chaos-studio-private-networking.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ Currently, you can only enable certain resource types for Chaos Studio virtual n
27
27
To use Chaos Studio with virtual network injection, you must meet the following requirements.
28
28
1. The `Microsoft.ContainerInstance` and `Microsoft.Relay` resource providers must be registered with your subscription.
29
29
1. The virtual network where Chaos Studio resources will be injected must have two subnets: a container subnet and a relay subnet. A container subnet is used for the Chaos Studio containers that will be injected into your private network. A relay subnet is used to forward communication from Chaos Studio to the containers inside the private network.
30
-
1. Both subnets need at least `/28` in the address space. An example is an address prefix of `10.0.0.0/28` or `10.0.0.0/24`.
30
+
1. Both subnets need at least `/27` in the address space. An example is an address prefix of `10.0.0.0/28` or `10.0.0.0/24`.
31
31
1. The container subnet must be delegated to `Microsoft.ContainerInstance/containerGroups`.
32
32
1. The subnets can be arbitrarily named, but we recommend `ChaosStudioContainerSubnet` and `ChaosStudioRelaySubnet`.
33
33
1. When you enable the desired resource as a target so that you can use it in Chaos Studio experiments, the following properties must be set:
Copy file name to clipboardExpand all lines: articles/chaos-studio/chaos-studio-tutorial-agent-based-cli.md
+33-4Lines changed: 33 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -113,32 +113,61 @@ The chaos agent is an application that runs in your VM or virtual machine scale
113
113
114
114
1. Install the Chaos Studio VM extension. Replace `$VM_RESOURCE_ID` with the resource ID of your VM or replace `$SUBSCRIPTION_ID`, `$RESOURCE_GROUP`, and `$VMSS_NAME` with those properties for your virtual machine scale set. Replace `$AGENT_PROFILE_ID` with the agent Profile ID. Replace `$USER_IDENTITY_CLIENT_ID` with the client ID of your managed identity. Replace `$APP_INSIGHTS_KEY` with your Application Insights instrumentation key. If you aren't using Application Insights, remove that key/value pair.
115
115
116
+
#### Full list of default Agent virtual machine extension configuration
117
+
118
+
Here is the **minimum agent vm extension configuration** required by the user:
119
+
120
+
```azcli-interactive
121
+
{
122
+
"profile": "$AGENT_PROFILE_ID",
123
+
"auth.msi.clientid": "$USER_IDENTITY_CLIENT_ID"
124
+
}
125
+
```
126
+
127
+
Here is **all values for agent vm extension configuration**
128
+
129
+
```azcli-interactive
130
+
{
131
+
"profile": "$AGENT_PROFILE_ID",
132
+
"auth.msi.clientid": "$USER_IDENTITY_CLIENT_ID",
133
+
"appinsightskey": "$APP_INSIGHTS_KEY",
134
+
"overrides": {
135
+
"region": string, default to be null
136
+
"logLevel": {
137
+
"default" : string , default to be Information
138
+
},
139
+
"checkCertRevocation": boolean, default to be false.
140
+
}
141
+
}
142
+
```
143
+
144
+
116
145
#### Install the agent on a virtual machine
117
146
118
147
Windows
119
148
120
149
```azurecli-interactive
121
-
az vm extension set --ids $VM_RESOURCE_ID --name ChaosWindowsAgent --publisher Microsoft.Azure.Chaos --version 1.0 --settings '{"profile": "$AGENT_PROFILE_ID", "auth.msi.clientid":"$USER_IDENTITY_CLIENT_ID", "appinsightskey":"$APP_INSIGHTS_KEY"}'
150
+
az vm extension set --ids $VM_RESOURCE_ID --name ChaosWindowsAgent --publisher Microsoft.Azure.Chaos --version 1.0 --settings '{"profile": "$AGENT_PROFILE_ID", "auth.msi.clientid":"$USER_IDENTITY_CLIENT_ID", "appinsightskey":"$APP_INSIGHTS_KEY"{"Overrides": "CheckCertRevocation" = true}}'
122
151
```
123
152
124
153
Linux
125
154
126
155
```azurecli-interactive
127
-
az vm extension set --ids $VM_RESOURCE_ID --name ChaosLinuxAgent --publisher Microsoft.Azure.Chaos --version 1.0 --settings '{"profile": "$AGENT_PROFILE_ID", "auth.msi.clientid":"$USER_IDENTITY_CLIENT_ID", "appinsightskey":"$APP_INSIGHTS_KEY"}'
156
+
az vm extension set --ids $VM_RESOURCE_ID --name ChaosLinuxAgent --publisher Microsoft.Azure.Chaos --version 1.0 --settings '{"profile": "$AGENT_PROFILE_ID", "auth.msi.clientid":"$USER_IDENTITY_CLIENT_ID", "appinsightskey":"$APP_INSIGHTS_KEY"{"Overrides": "CheckCertRevocation" = true}}'
128
157
```
129
158
130
159
#### Install the agent on a virtual machine scale set
1. If you're setting up a virtual machine scale set, verify that the instances were upgraded to the latest model. If needed, upgrade all instances in the model.
0 commit comments