Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated ArcBox Azure Costs #464

Merged
merged 1 commit into from
Jan 21, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/azure_jumpstart_arcbox/DataOps/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ ArcBox allows you to experience various Azure Arc-enabled SQL Managed Instance u

## ArcBox Azure Costs

ArcBox resources generate Azure consumption charges from the underlying Azure resources including core compute, storage, networking, and auxiliary services. Note that Azure consumption costs vary depending on the region where ArcBox is deployed. Be mindful of your ArcBox deployments and ensure that you disable or delete ArcBox resources when not in use to avoid unwanted charges. In an effort to reduce the costs, by default the client VM will auto-shutdown at 1800 UTC. This can be changed either during the deployment by altering the parameters for autoShutdownEnabled, autoShutdownTime, and autoShutdownTimezone within the Bicep template or after deployment by changing the [auto-shutdown](https://learn.microsoft.com/azure/virtual-machines/auto-shutdown-vm?tabs=portal) parameters from the Azure Portal. When the _ArcBox-Client_ VM is stopped, there will be no compute charges; however, there will still be charges for the storage components. In addition, [Azure Spot VMs](https://learn.microsoft.com/azure/virtual-machines/spot-vms) can be used to reduce the compute costs of ArcBox. Using this option may result in the _ArcBox-Client_ being evicted when Azure needs the capacity and the VM will no longer be available.
ArcBox resources incur Azure charges for compute, storage, networking, and auxiliary services. Costs vary by region. Disable or delete ArcBox resources when not in use to avoid charges. By default, the client VM auto-shuts down at 1800 UTC to reduce costs. This can be changed during deployment via the Bicep template or later in the Azure Portal. When the _ArcBox-Client_ VM is stopped, compute charges cease, but storage charges remain. Consider using [Azure Spot VMs](https://learn.microsoft.com/azure/virtual-machines/spot-vms) to reduce compute costs, though this may result in eviction when Azure needs capacity.

![screenshot showing the auto-shutdown parameters in the Azure Portal](./arcbox-client-auto-shutdown.png)

Expand Down Expand Up @@ -709,7 +709,7 @@ This section guides you through different settings for enabling Microsoft Defend
![Screenshot showing Defender for SQL security incidents and alerts](./sql-defender-incidents.png)

- Microsoft Defender for Cloud generates an email and sends it to the registered email for alerts. The below screenshot shows an email alert sent by Defender for Cloud when a SQL threat is detected. By default, this email is sent to the registered contact email at the subscription level.

![Screenshot showing Defender for SQL security incidents and alerts](./sql-defender-brute-force-attack-alert.png)

### Arc-enabled SQL Server - least privilege access
Expand Down
8 changes: 4 additions & 4 deletions docs/azure_jumpstart_arcbox/DevOps/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,7 @@ ArcBox deploys several management and operations services that work with ArcBox'

## ArcBox Azure Costs

ArcBox resources generate Azure consumption charges from the underlying Azure resources including core compute, storage, networking, and auxiliary services. Note that Azure consumption costs vary depending on the region where ArcBox is deployed. Be mindful of your ArcBox deployments and ensure that you disable or delete ArcBox resources when not in use to avoid unwanted charges. In an effort to reduce the costs, by default the client VM will auto-shutdown at 1800 UTC. This can be changed either during the deployment by altering the parameters for autoShutdownEnabled, autoShutdownTime, and autoShutdownTimezone within the Bicep template or after deployment by changing the [auto-shutdown](https://learn.microsoft.com/azure/virtual-machines/auto-shutdown-vm?tabs=portal) parameters from the Azure Portal. When the _ArcBox-Client_ VM is stopped, there will be no compute charges; however, there will still be charges for the storage components. In addition, [Azure Spot VMs](https://learn.microsoft.com/azure/virtual-machines/spot-vms) can be used to reduce the compute costs of ArcBox. Using this option may result in the _ArcBox-Client_ being evicted when Azure needs the capacity and the VM will no longer be available.
ArcBox resources incur Azure charges for compute, storage, networking, and auxiliary services. Costs vary by region. Disable or delete ArcBox resources when not in use to avoid charges. By default, the client VM auto-shuts down at 1800 UTC to reduce costs. This can be changed during deployment via the Bicep template or later in the Azure Portal. When the _ArcBox-Client_ VM is stopped, compute charges cease, but storage charges remain. Consider using [Azure Spot VMs](https://learn.microsoft.com/azure/virtual-machines/spot-vms) to reduce compute costs, though this may result in eviction when Azure needs capacity.

![screenshot showing the auto-shutdown parameters in the Azure Portal](./arcbox-client-auto-shutdown.png)

Expand Down Expand Up @@ -438,7 +438,7 @@ ArcBox uses a GitOps configuration on the bookstore application to split traffic

![Diagram of Istio bookstore app traffic split](./smi_traffic_split.png)

- Review the [Istio Traffic Split manifest](https://github.com/microsoft/azure-arc-jumpstart-apps/blob/main/bookstore/yaml/istio-virtualservice.yaml) applied to the _ArcBox-K3s-Data_ cluster
- Review the [Istio Traffic Split manifest](https://github.com/microsoft/azure-arc-jumpstart-apps/blob/main/bookstore/yaml/istio-virtualservice.yaml) applied to the _ArcBox-K3s-Data_ cluster
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Review the [Istio Traffic Split manifest](https://github.com/microsoft/azure-arc-jumpstart-apps/blob/main/bookstore/yaml/istio-virtualservice.yaml) applied to the _ArcBox-K3s-Data_ cluster
- Review the [Istio Traffic Split manifest](https://github.com/microsoft/azure-arc-jumpstart-apps/blob/main/bookstore/yaml/istio-virtualservice.yaml) applied to the _ArcBox-K3s-Data_ cluster.


- To show the Istio traffic split, open the below windows.

Expand Down Expand Up @@ -534,7 +534,7 @@ Optionally, you can explore additional GitOps and RBAC scenarios in a manual fas

- A browser window with the open Hello-Arc application _`http://k3sdevops.devops.com/`_ URL.
- PowerShell running the command _`kubectl get pods -n hello-arc -w`_ command.

```shell
kubectx arcbox-k3s
kubectl get pods -n hello-arc -w
Expand Down Expand Up @@ -652,7 +652,7 @@ ArcBox is a sandbox that can be used for a large variety of use cases, such as a
- Build policy initiatives that apply to your Azure Arc-enabled resources
- Write and test custom policies that apply to your Azure Arc-enabled resources
- Incorporate your own tooling and automation into the existing automation framework
- Create additional guest VMs and onboard them to Azure Arc. Refer to the list of [supported operating systems](https://learn.microsoft.com/azure/azure-arc/servers/prerequisites#supported-operating-systems)
- Create additional guest VMs and onboard them to Azure Arc. Refer to the list of [supported operating systems](https://learn.microsoft.com/azure/azure-arc/servers/prerequisites#supported-operating-systems)

## Clean up the deployment

Expand Down
20 changes: 10 additions & 10 deletions docs/azure_jumpstart_arcbox/ITPro/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ ArcBox deploys several management and operations services that work with ArcBox'

## ArcBox Azure Costs

ArcBox resources generate Azure consumption charges from the underlying Azure resources including core compute, storage, networking and auxiliary services. Note that Azure consumption costs vary depending the region where ArcBox is deployed. Be mindful of your ArcBox deployments and ensure that you disable or delete ArcBox resources when not in use to avoid unwanted charges. In an effort to reduce the costs, by default the client VM will auto-shutdown at 1800 UTC. This can be changed either during the deployment by altering the parameters for autoShutdownEnabled, autoShutdownTime, and autoShutdownTimezone within the Bicep template or after deployment by changing the [auto-shutdown](https://learn.microsoft.com/azure/virtual-machines/auto-shutdown-vm?tabs=portal) parameters from the Azure Portal. When the _ArcBox-Client_ VM is stopped, there will be no compute charges; however, there will still be charges for the storage components. In addition, [Azure Spot VMs](https://learn.microsoft.com/azure/virtual-machines/spot-vms) can be used to reduce the compute costs of ArcBox. Using this option may result in the _ArcBox-Client_ being evicted when Azure needs the capacity and the VM will no longer be available.
ArcBox resources incur Azure charges for compute, storage, networking, and auxiliary services. Costs vary by region. Disable or delete ArcBox resources when not in use to avoid charges. By default, the client VM auto-shuts down at 1800 UTC to reduce costs. This can be changed during deployment via the Bicep template or later in the Azure Portal. When the _ArcBox-Client_ VM is stopped, compute charges cease, but storage charges remain. Consider using [Azure Spot VMs](https://learn.microsoft.com/azure/virtual-machines/spot-vms) to reduce compute costs, though this may result in eviction when Azure needs capacity.

![screenshot showing the auto-shutdown parameters in the Azure Portal](./arcbox-client-auto-shutdown.png)

Expand Down Expand Up @@ -308,10 +308,10 @@ Enter-AzVM -ResourceGroupName $Env:resourceGroup -Name $serverName -LocalUser $l

```powershell
az login --identity

$serverName = "ArcBox-Win2K25"
$localUser = "Administrator"

az ssh arc --resource-group $Env:resourceGroup --name $serverName --local-user $localUser
```

Expand Down Expand Up @@ -469,22 +469,22 @@ Expected output:
```powershell
# Create PowerShell Remoting session
New-PSSession -HostName $serverName -UserName $localUser -Options $options -OutVariable session

# Run a command
Invoke-Command -Session $session -ScriptBlock {Write-Output "Hello $(whoami) from $(hostname)"}

# Enter an interactive session
Enter-PSSession -Session $session[0]

# Disconnect
exit

# Clean-up
$session | Remove-PSSession
```

Expected output:

![Screenshot showing usage of remote PowerShell tunnelled via SSH](./ps_remoting_via_ssh_03.png)

### ArcBox Azure Monitor workbooks
Expand Down Expand Up @@ -666,7 +666,7 @@ This section guides you through different settings for enabling Microsoft Defend
![Screenshot showing Defender for SQL security incidents and alerts](./sql-defender-incidents.png)

- Microsoft Defender for Cloud generates an email and sends it to the registered email for alerts. The below screenshot shows an email alert sent by Defender for Cloud when a SQL threat is detected. By default, this email is sent to the registered contact email at the subscription level.

![Screenshot showing Defender for SQL security incidents and alerts](./sql-defender-brute-force-attack-alert.png)

### Arc-enabled SQL Server - least privilege access
Expand Down Expand Up @@ -769,7 +769,7 @@ ArcBox is a sandbox that can be used for a large variety of use cases, such as a
- Write and test custom policies that apply to your Azure Arc-enabled resources
- Incorporate your own tooling and automation into the existing automation framework
- Build a certificate/secret/key management strategy with your Azure Arc resources
- Create additional guest VMs and onboard them to Azure Arc. Refer to the list of [supported operating systems](https://learn.microsoft.com/azure/azure-arc/servers/prerequisites#supported-operating-systems)
- Create additional guest VMs and onboard them to Azure Arc. Refer to the list of [supported operating systems](https://learn.microsoft.com/azure/azure-arc/servers/prerequisites#supported-operating-systems)

Do you have an interesting use case to share? [Submit an issue](https://aka.ms/JumpstartIssue) on GitHub with your idea and we will consider it for future releases!

Expand Down
Loading