Skip to content

Updated aws cli step docs regarding container usages on ec2 #3049

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.

Sign up for GitHub

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

Merged
philipkotliyakov merged 2 commits into from
Mar 4, 2026
Merged

Updated aws cli step docs regarding container usages on ec2 #3049

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b6b745c
added section regarding ec2 http put hopes when running aws cli step …
philipkotliyakov Mar 4, 2026
483eb9a
linting
philipkotliyakov Mar 4, 2026
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
8 changes: 6 additions & 2 deletions src/pages/docs/deployments/custom-scripts/aws-cli-scripts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
layout: src/layouts/Default.astro
pubDate: 2023-01-01
modDate: 2024-08-26
modDate: 2025-03-04
title: AWS CLI and PowerShell scripts
description: AWS CLI and PowerShell Scripts allow you to manage your AWS resources as part of your deployment process.
icon: fa-regular fa-file-code
Expand Down Expand Up @@ -76,7 +76,7 @@ PowerShell scripts run by the `Run an AWS CLI Script` step have access to the AW

This means you can run scripts using a mix of the AWS CLI and PowerShell commands:

```
```powershell
# This will write out information on the Get-AWSPowerShellVersion CmdLet.
get-command Get-AWSPowerShellVersion | fl *

Expand Down Expand Up @@ -128,6 +128,10 @@ To use your own version of the AWS CLI or AWS PowerShell cmdlets when using Dyna
- Configure your step to use a Dynamic Worker pool that supports [execution containers](/docs/projects/steps/execution-containers-for-workers).
- Configure your step to run in an execution container with a [compatible Docker image](/docs/projects/steps/execution-containers-for-workers/#which-image) that contains the versions of the AWS CLI or AWS PowerShell cmdlets that you would like to use.

## EC2 workers and execution containers

If the worker is an EC2 instance and you configure your step to run inside a container on that worker, you must configure the EC2 instance's HTTP PUT response hop limit to 2. This is required because accessing the [Instance Metadata Service](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html) (IMDS) from within a container adds an additional network hop. You can configure this using the [modify-instance-metadata-options](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-instance-metadata-options.html) AWS CLI command.

## Older versions

In Octopus 2021.2 a warning will also appear in the deployment logs if the AWS tools bundled with Octopus Deploy are used in a step. Older versions of Octopus will not display this warning.