Leveraging the Google Agent Development Kit (ADK) and the underlying Gemini LLM to build cross cloud apps with the Python programming language deployed to the ECS Express service on AWS.
Aren’t There a Billion Python Agent Demos?
Yes there are.
Python has traditionally been the main coding language for ML and AI tools. The goal of this article is to provide a minimal viable basic working MCP stdio server that can be run locally without any unneeded extra code or extensions.
What Is Python?
Python is an interpreted language that allows for rapid development and testing and has deep libraries for working with ML and AI:
Python Version Management
One of the downsides of the wide deployment of Python has been managing the language versions across platforms and maintaining a supported version.
The pyenv tool enables deploying consistent versions of Python:
GitHub - pyenv/pyenv: Simple Python version management
As of writing — the mainstream python version is 3.13. To validate your current Python:
admin@ip-172-31-70-211:~/gemini-cli-aws/mcp-lightsail-python-aws$ python --version
Python 3.13.12
Amazon ECS Express
Amazon ECS Express Mode (announced Nov 2025) is a simplified deployment feature for Amazon Elastic Container Service (ECS) designed to rapidly launch containerized applications, APIs, and web services on AWS Fargate. It automates infrastructure setup — including load balancing, networking, scaling, and HTTPS endpoints — allowing developers to deploy from container image to production in a single step.
More details are available here:
Gemini CLI
If not pre-installed you can download the Gemini CLI to interact with the source files and provide real-time assistance:
npm install -g @google/gemini-cli
Testing the Gemini CLI Environment
Once you have all the tools and the correct Node.js version in place- you can test the startup of Gemini CLI. You will need to authenticate with a Key or your Google Account:
▝▜▄ Gemini CLI v0.33.1
▝▜▄
▗▟▀ Logged in with Google /auth
▝▀ Gemini Code Assist Standard /upgrade
Node Version Management
Gemini CLI needs a consistent, up to date version of Node. The nvm command can be used to get a standard Node environment:
Docker Version Management
The AWS Cli tools and Lightsail extensions need current version of Docker. If your environment does not provide a recent docker tool- the Docker Version Manager can be used to downlaod the latest supported Docker:
AWS CLI
The AWS CLI provides a command line tool to directly access AWS services from your current environment. Full details on the CLI are available here:
Install Docker, AWS CLI, and the Lightsail Control plugin for containers
Agent Development Kit
The Google Agent Development Kit (ADK) is an open-source, Python-based framework designed to streamline the creation, deployment, and orchestration of sophisticated, multi-agent AI systems. It treats agent development like software engineering, offering modularity, state management, and built-in tools (like Google Search) to build autonomous agents.
The ADK can be installed from here:
This seems like a lot of Configuration!
Getting the key tools in place is the first step to working across Cloud environments.
Where do I start?
The strategy for starting multimodal real time cross cloud agent development is a incremental step by step approach.
The agents in the demo are based on the original code lab:
Way Back Home - Building an ADK Bi-Directional Streaming Agent | Google Codelabs
First, the basic development environment is setup with the required system variables, and a working Gemini CLI configuration.
Then, a minimal ADK Agent is built with the visual builder. Next — the entire solution is deployed to Amazon ECS Express.
Setup the Basic Environment
At this point you should have a working Python environment and a working Gemini CLI installation. All of the relevant code examples and documentation is available in GitHub. This repo has a wide variety of samples- but this lab will focus on the ‘level_3-ecsexpress’ setup.
The next step is to clone the GitHub repository to your local environment:
cd ~
git clone https://github.com/xbill9/gemini-cli-aws
cd level_3-ecsexpress
Then run init.sh from the cloned directory.
The script will attempt to determine your shell environment and set the correct variables:
source init.sh
If your session times out or you need to re-authenticate- you can run the set_env.sh script to reset your environment variables:
source set_env.sh
Variables like PROJECT_ID need to be setup for use in the various build scripts- so the set_env script can be used to reset the environment if you time-out.
Verify The ADK Installation
To verify the setup, run the ADK CLI locally with Agent1:
xbill@penguin:~/gemini-cli-aws/level_3-ecsexpress/backend/app$ adk run biometric_agent
Log setup complete: /tmp/agents_log/agent.20260405_093812.log
To access latest log: tail -F /tmp/agents_log/agent.latest.log
/home/xbill/.local/lib/python3.13/site-packages/google/adk/cli/cli.py:204: UserWarning: [EXPERIMENTAL] InMemoryCredentialService: This feature is experimental and may change or be removed in future versions without notice. It may introduce breaking changes at any time.
credential_service = InMemoryCredentialService()
/home/xbill/.local/lib/python3.13/site-packages/google/adk/auth/credential_service/in_memory_credential_service.py:33: UserWarning: [EXPERIMENTAL] BaseCredentialService: This feature is experimental and may change or be removed in future versions without notice. It may introduce breaking changes at any time.
super(). __init__ ()
Running agent biometric_agent, type exit to exit.
Deploying to Amazon ECS Express
The first step is to refresh the AWS credentials in the current build environment:
xbill@penguin:~/gemini-cli-aws/level_3-ecsexpress$ aws login --remote
Then a utility script caches the credentials on the local system for building:
xbill@penguin:~/gemini-cli-aws/level_3-ecsexpress$ source save-aws-creds.sh
Exporting AWS credentials...
Successfully saved credentials to .aws_creds
The Makefile will now automatically use these for deployments.
Run the deploy version on the local system: 0.0s 0.0s
You can validate the final result by checking the messages:
make deploy
✦ The application has been successfully deployed to AWS ECS Express Mode.
- Service Status: ACTIVE
- Public Endpoint: [https://bi-59e66ed2dcde45dcb1b347ce8d6ca7b8.ecs.us-east-1.on.aws](https://bi-59e66ed2dcde45dcb1b347ce8d6ca7b8.ecs.us-east-1.on.aws)
([https://bi-59e66ed2dcde45dcb1b347ce8d6ca7b8.ecs.us-east-1.on.aws](https://bi-59e66ed2dcde45dcb1b347ce8d6ca7b8.ecs.us-east-1.on.aws))
- Deployment Cycle: IAM roles created/verified, Docker image built and pushed to ECR, and ECS service updated.
You can now access your biometric-scout-service at the above URL.
Once the container is deployed- you can then get the endpoint:
make status
You can then get the endpoint URL:
bi-59e66ed2dcde45dcb1b347ce8d6ca7b8.ecs.us-east-1.on.aws
The service will be visible in the AWS console:
Running the Web Interface
Start a connection to the ECS Express Deployed app:
https://bi-59e66ed2dcde45dcb1b347ce8d6ca7b8.ecs.us-east-1.on.aws/
Then connect to the app :
Then use the Live model to process audio and video:
Finally — complete the sequence:
Summary
The Agent Development Kit was used to enable a multi-modal agent using the Gemini Live Model. This Agent was tested locally with the CLI and then deployed to Amazon ECS Express. This approach validates that cross cloud tools can be used — even with more complex agents.





Top comments (0)