close

Infrastructure-as-Code (IaC)

Amazon Web Services (AWS)

How do I create a CloudFormation template to enable local zones?

by Roy "rat" Tokeshi on

Here is an example of a CloudFormation template that enables a specific Local Zone in an AWS region:

AWSTemplateFormatVersion: '2010-09-09'
Resources:
     LocalZone:
          Type: AWS::EC2::AvailabilityZoneGroup
          Properties:
               GroupName: LocalZoneGroup
               SupportedPlatforms:
                    - add:
                         - "zone_name"

In this example, replace “zone_name” with the name of the Local Zone you want to enable. This CloudFormation template creates an availability zone group named “LocalZoneGroup” and adds the specified Local Zone to the group. Once this CloudFormation stack has been created, the specified Local Zone will be enabled for use in your AWS environment.

You can also modify this CloudFormation template to enable multiple Local Zones by adding additional elements to the SupportedPlatforms list. Use the AWS CLI or the AWS Management Console to manage and configure the Local Zones that have been enabled using this CloudFormation template.

read more
Amazon Web Services (AWS)Infrastructure-as-Code (IaC)

How to script AWS CLI to describe instances on Amazon WorkSpaces

by Roy "rat" Tokeshi on

Here’s an example of a bash script that uses the AWS CLI to describe Amazon WorkSpaces instances:

bash
!/bin/bash
# Define the AWS region to use
REGION="us-west-2"
# Use the AWS CLI to describe the Amazon Workspaces instances
INSTANCES=$(aws workspaces describe-workspaces --region $REGION)
# Print the information for each instance
echo "Information for all Amazon Workspaces instances:"
echo $INSTANCES | jq -r '.Workspaces[] | "\(.DirectoryId) \(.UserName) \(.WorkspaceId) \(.State)"'

In this example, the script uses the aws workspaces describe-workspaces command to get information about all Amazon WorkSpaces instances in the specified region (us-west-2 in this case). The output of the command is stored in the INSTANCES variable. The script then uses the jq command to parse the JSON output and print the DirectoryId, UserName, WorkspaceId, and State of each instance.

You’ll need to have the AWS CLI and jq installed on your system to run this script.

read more