This readme demonstrates how to use Amazon Q Developer CLI to create infrastructure as code (IaC) for deploying a secure, highly available web service using AWS Fargate. Amazon Q Developer CLI extends far beyond container services. By completing this demo, you'll discover its versatility in automating various development tasks, making it a valuable tool for streamlining your software development lifecycle. What is Amazon Q Developer? Amazon Q Developer is an AI-powered assistant designed specifically for software development and DevOps tasks. It helps developers write, understand, and transform code, create infrastructure, troubleshoot issues, and answer questions about AWS services and best practices. This demo focuses on the new feature Amazon Q for command line. Installing Amazon Q for command line

We found complexity dealing with single agent for our booking workflow. With the fully managed multi-agent collaboration capability on Amazon Bedrock, specialized agents work within their domains of expertise, coordinated by a supervisor agent. The supervisor breaks down requests, delegates tasks, and consolidates outputs into a final response. For example, our travel advisor multi-agent system might include agents specialized in scheduling, availability recommendations, making reservations & payment checkout. The following figure shows the team of agents that shows how multi-agent collaboration works in the proposed scenario image Find example here: Bedrock Multi Agent Collaboration Workshop 1 - User Request User request to book a ferry

![alt text](https://raw.githubusercontent.com/awslabs/aws-icons-for-plantuml/main/source/unofficial/AWS-Architecture-Icons_SVG_20200430/SVG%20Light/_Group%20Icons/AWS-Cloud-alt_light-bg.svg "Tech Series" =20x20) Your AWS Account Team brings this in-person and virtual hackathon sessions to level-up your skills in key cloud domains of AI/ML and serverless. Meet your local team in attendance (hover for names) ![alt text](https://d3m889aznlr23d.cloudfront.net/img/events/id/458/458628562/assets/58403e1c344e418f20636d5a2806d3a5.arranp-high-res-current-photo.jpeg "Arran Peterson" =80x80) This is our list of hints and tips for this hackathon. JOIN EVENT: https://app.chime.aws/meetings Hydrate Sandbox Instructions: https://github.com/arranpeterson/dam

:::info :warning: This event is now completed. Post workshop follow items have been added. click on this link ::: ![AWS Workshop](https://raw.githubusercontent.com/awslabs/aws-icons-for-plantuml/main/source/unofficial/AWS-Architecture-Icons_SVG_20200430/SVG%20Light/_Group%20Icons/AWS-Cloud-alt_light-bg.svg "Tech Series" =20x20) Meet the local team in attendance (hover for names) ![Arran Peterson](https://d3m889aznlr23d.cloudfront.net/img/events/id/458/458628562/assets/58403e1c344e418f20636d5a2806d3a5.arranp-high-res-current-photo.jpeg "Arran Peterson" =80x80) ![Luke N](https://d3m889aznlr23d.cloudfront.net/img/events/id/458/458628562/assets/8017d0b1195a9d57f1b44457f03b329f.lnotley-high-res-current-photo.jpeg "Luke Notley" =80x80) This is our list of hints and tips for this workshop.

Jump to Sections on IAM Lambda Function Tips Mock API Responses Administrivia, Schedule and Planning The event will be delivered as follows:

:::info :bulb: This template is for SACE new students. ::: 🎉 Welcome Hi:smile: Welcome to 42 Adelaide SACE CLOUD Week!! By the time you have finished this week's activities, you will have completed more then 30 hours of AWS Cloud Training! :book: AWS Student Information

![alt text](https://raw.githubusercontent.com/awslabs/aws-icons-for-plantuml/main/source/unofficial/AWS-Architecture-Icons_SVG_20200430/SVG%20Light/_Group%20Icons/AWS-Cloud-alt_light-bg.svg "Tech Series" =20x20) Meet the local team in attendance (hover for names) ![alt text](https://d3m889aznlr23d.cloudfront.net/img/events/id/458/458628562/assets/58403e1c344e418f20636d5a2806d3a5.arranp-high-res-current-photo.jpeg "Arran Peterson" =80x80) ![alt text](https://media.licdn.com/dms/image/C4D03AQG9CgDKQWYPhQ/profile-displayphoto-shrink_200_200/0/1516811637369?e=1721260800&v=beta&t=pmqpGPSzl2jrZ05Seiqt4fKQeaI0nzeS3shM342h26k "Josh Tow" =80x80) This is our list of hints and tips from the ECS presentation. Follow Up Items TBC ECS Best Practices

This is our list of hints and tips for this workshop. JOIN EVENT: https://catalog.workshops.aws/join Complete OTP to an email address (Any that you can access over public internet) Code will be on the TV screen for you to type. Read "Terms and Conditions", select "I agree with the Terms and Conditions" and click "Join event". On the next page, click "Open AWS Console" URL link. Skip the entire sections: "Introduction" & "Setup" this is already done!

Showcase the Amazon Textract API and how we can process Invoices programmatically in an extensible event driven workflow in under one hour! In this lab you will process an invoice by creating a simple serverless event driven workflow by: Use Amazon Textract to extract form data from the sample invoice file Configure an AWS Lambda function to make an API call to Amazon Textract, then extract expense data from the sample file Create a simple event driven workload by adding an Amazon S3 event trigger to invoke the Lambda function for any PUT events that meet the criteria Validate that the response JSON file received in the S3 bucket contains the expected results. Review the results in Amazon CloudWatch Logs

This is our list of hints and tips for this workshop. JOIN EVENT: https://catalog.workshops.aws/join Complete OTP to an email address (Any that you can access over public internet) Code will be on the TV screen for you to type. Read "Terms and Conditions", select "I agree with the Terms and Conditions" and click "Join event". On the next page, click "Open AWS Console" URL link. Skip the entire sections: "Introduction" & "Setup" this is already done!

When security incidents occur, your ability to react swiftly to an incident is critical for minimizing the damage caused. In this post we will walk through an example to showcase how to isolate a workload, so we can perform forensic investigation and root cause analysis, specifically for Amazon ECS workloads. Establishing a reliable alerting system that can promptly notify you of suspicious activities (Amazon GuardDuty Runtime Monitoring for ECS) is the foundational step in crafting an effective incident response plan. In the event of an incident, you'll need to make rapid decisions regarding whether to terminate and replace the affected container or isolate and examine it. If you opt to isolate the container as part of a forensic investigation and root cause analysis, follow the set of activities below. Example Incident Response Plan Reduce the Blast Radius By isolating the impacted ECS Container Instance or Fargate task, you're instructing the ECS scheduler to refrain from scheduling a task or tasks onto an affected instance. This isolation allows you to take the compremised artifacts offline for forensic analysis without causing disruptions to other running tasks in the cluster. Identify the Compromised ECS Container Instance or Fargate task: Identify the specific ECS Container Instance or Fargate task that you suspect has been compromised. Update Container Instance Metadata: Add custom metadata tags to the compromised ECS Container Instance to mark it for forensic analysis. For example, you can add a tag like "forensic=true" to the instance. Adjust the ECS Service or Task Definition: Update the ECS service or task definition to include placement constraints that exclude the ECS Container Instance with the "forensic=true" tag. This way, the scheduler will avoid scheduling new tasks on the compromised instance. Isolate the Task with a Security Group Rule: Create a security group rule to deny all inbound and outbound traffic to the compromised task.

:::info :bulb: This template is for onboarding new students. ::: 🎉 Welcome Hi:smile: Welcome to 42 Adelaide AWS learning path!! By the time you have completed this learning path you will have completed 20 hours of AWS Cloud Training, recieved 4 training badges and will have the knowledge to sit the AWS Certified Cloud Practioner exam. :book: AWS Student Information

![alt text](https://raw.githubusercontent.com/awslabs/aws-icons-for-plantuml/main/source/unofficial/AWS-Architecture-Icons_SVG_20200430/SVG%20Light/_Group%20Icons/AWS-Cloud-alt_light-bg.svg "Tech Series" =20x20) When running capacity providers or launch-type EC2 in your ECS Task Definitions you may have the need to access the underlying ECS Container Instances (EC2) for rudimentary troubleshooting, do this via AWS System Manager. The System Manager settings need to be applied via the EC2 IAM Instance Profile to your Container Instances. Once the policy is applied you can use AWS System Manager for ECS Container Instance troubleshooting in the following ways: Interactive Shell Remote Commands Automation Runbooks supplied by AWS for common tasks Attach the System Manager policies to the ecsInstanceRole Open the IAM console at https://console.aws.amazon.com/iam/.

![alt text](https://raw.githubusercontent.com/awslabs/aws-icons-for-plantuml/main/source/unofficial/AWS-Architecture-Icons_SVG_20200430/SVG%20Light/_Group%20Icons/AWS-Cloud-alt_light-bg.svg "Tech Series" =20x20) Integrating security measures in your rudimentary pipeline build and releases of container images is a critical part of building an application in the AWS Shared Responsibility Model. Build tasks like Dockerfile linting, secret scanning and vulnerability scanning should all be integrated within your AWS CodeBuild as they are important security controls before an image is used in an application. Up until now for vulnerability scanning the choice of many is to use third party solutions like Anchore which is primarily used for checking your image for any Common Vulnerabilities and Exposure (CVE). Amazon Elastic Container Registry (ECR) now supports Image Scanning where we can do this via an AWS managed service and no longer have to deploy a client server API architecture with additional resources within our container builds. To successfully scan our container images using AWS native services we must run the aws ecr image-scan-compute aws-cli command during our container image build steps to complete an image scan and wait until the findings can be accessed. The command will poll every 5 seconds until successful state has been reached. The command is a paginated operation and will retrieve the entire data set of results. The identified vulnerability results can be returned in JSON with the following levels of severity - Critical, High, Medium and Low. When the image scan completes we can specify a vulnerability threshold like "High or Critical", which upon finding any of the criticalities can fail the build step and subsequent pipeline execution. Unlike third party solutions all the scan findings are natively integrated with Amazon ECR, Amazon Inspector and AWS Security Hub. AWS-CLI commands Start a scan: aws ecr start-image-scan --repository-name <image-repository-name> --image-id imageTag=<image-tag> Wait for the scan to complete:

![alt text](https://raw.githubusercontent.com/awslabs/aws-icons-for-plantuml/main/source/unofficial/AWS-Architecture-Icons_SVG_20200430/SVG%20Light/_Group%20Icons/AWS-Cloud-alt_light-bg.svg "Tech Series" =20x20) In this AWS workshop we will deploy a VPC Network and ECS Cluster with capacity providers to leverage Spot instance type. Clone the repository cd ~/environment git clone https://github.com/awslabs/ec2-spot-workshops.git cd ec2-spot-workshops/workshops/ecs-spot-capacity-providers We are defining our deployment configuration via code using AWS Cloudformation. Let’s look through the code to better understand what resources CloudFormation will create. Update the CFN Stack We first need to update the CFN template to latest schema standards, open ec2-spot-workshops/workshops/ecs-spot-capacity-providers/ecs-spot-workshop-cfn.yaml for editing in your IDE. (Cloud9)

![alt text](https://raw.githubusercontent.com/awslabs/aws-icons-for-plantuml/main/source/unofficial/AWS-Architecture-Icons_SVG_20200430/SVG%20Light/_Group%20Icons/AWS-Cloud-alt_light-bg.svg "Tech Series" =20x20) This workshop is aimed at software engineers and platform engineers who want to get hands-on experience with Amazon ECS service connect, and using them to build container solutions for ECS workloads. Amazon ECS service connect provides opinionated management of service-to-service communication. It does this by building opinionated management of both service discovery and a service mesh. This provides a unified way to refer to your services within namespaces, and standardized metrics and logs to monitor all of your applications on Amazon ECS. There is no additional infrastructure configuration required for service-to-service communication when using Amazon ECS service connect. Amazon ECS service connect configures each task for your applications to discover services. Now developers can reference and connect to their services by logical names, and ECS Service Connect will ensure that traffic is load balanced across healthy service endpoints. Operators can enjoy simplified infrastructure configuration, where load balancers are deployed only for external traffic. Additionally, all service communications inside VPCs are configured automatically, now with better insights into traffic right in the ECS Console, that simplifies both the operational and debugging experience. Download the cloud formation templates Log into the Cloud9 environment and with an open Terminal window complete the following steps to setup the labs

![alt text](https://raw.githubusercontent.com/awslabs/aws-icons-for-plantuml/main/source/unofficial/AWS-Architecture-Icons_SVG_20200430/SVG%20Light/_Group%20Icons/AWS-Cloud-alt_light-bg.svg "Tech Series" =20x20) In this AWS workshop we will deploy a VPC Network and ECS Cluster with capacity providers to leverage Task Placement Constraints to deploy ARM or GPU based definitions to the required container instance type. https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement-constraints.html Clone the repository cd ~/environment git clone https://github.com/aws-containers/ecsworkshop-advanced-scheduling-chapter.git cd ecsworkshop-advanced-scheduling-chapter We are defining our deployment configuration via code using AWS Cloudformation. Let’s look through the code to better understand what resources CloudFormation will create.

![alt text](https://raw.githubusercontent.com/awslabs/aws-icons-for-plantuml/main/source/unofficial/AWS-Architecture-Icons_SVG_20200430/SVG%20Light/_Group%20Icons/AWS-Cloud-alt_light-bg.svg "Tech Series" =20x20) This workshop is aimed at software engineers and platform engineers who want to get hands-on experience with AWS CI/CD tools, and using them to build pipelines for ECS workloads. The workshop consists of a number of lab modules, each designed to demonstrate a number of CI/CD concepts. It makes use of AWS services like AWS CodePipeline, AWS CodeCommit, AWS CodeBuild, AWS CloudFormation, and AWS CodeDeploy Clone the repository Log into the Cloud9 environment and with an open Terminal window complete the following steps to setup the labs cd ~/environment git clone https://github.com/aws-samples/cicd-for-ecs-workshop-code.git cd cicd-for-ecs-workshop-code

title: DR/VPC Immersion Day description: For customers on the day to reference. Event Engine: https://dashboard.eventengine.run/ We have a collaborative session Chime link: https://chime.aws/8370378359 Lab Content

![alt text](https://raw.githubusercontent.com/awslabs/aws-icons-for-plantuml/main/source/unofficial/AWS-Architecture-Icons_SVG_20200430/SVG%20Light/_Group%20Icons/AWS-Cloud-alt_light-bg.svg "Tech Series" =20x20) The AWS Adelaide Tech Series brings in-person sessions to level-up your skills in key cloud domains. Meet the local team in attendance (hover for names) ![alt text](https://d3m889aznlr23d.cloudfront.net/img/events/id/458/458628562/assets/58403e1c344e418f20636d5a2806d3a5.arranp-high-res-current-photo.jpeg "Arran Peterson" =80x80) ![alt text](https://d3m889aznlr23d.cloudfront.net/img/events/id/458/458628562/assets/26ce144744ef9e861d846f867b833f27.adp-high-res-current-photo.jpeg "Andy Pettica" =80x80) ![alt text](https://d3m889aznlr23d.cloudfront.net/img/events/id/458/458628562/assets/9eed3888dbec81ea186fecfdacee61b9.ifal-300dpi.jpeg "Ian Falconer" =80x80) ![alt text](https://d3m889aznlr23d.cloudfront.net/img/events/id/458/458628562/assets/4a5f8328a5058437653a2d5f917c0459.joshmci-high-res-current-photo.jpeg "Josh McIntosh" =80x80) ![alt text](https://d3m889aznlr23d.cloudfront.net/img/events/id/458/458656470/assets/092abf8cac6f715907e14a6f2478bbc7.rrego-high-res-current-photo.jpeg "Rene Abrego" =80x80) ![alt text](https://d3m889aznlr23d.cloudfront.net/img/events/id/458/458716629/assets/b638e9972bf7c3929eea64e50cc671dd.karan-sethi.jpeg "Karan Sethi" =80x80) This is our list of hints and tips for this workshop. JOIN EVENT: https://catalog.workshops.aws/join Complete OTP to an email address (Any that you can access over public internet) Code will be on the TV screen for you to type.