By using AWS re:Post, you agree to the Terms of Use

Unanswered Questions tagged with AWS Command Line Interface

Sort by most recent

Browse through the questions and answers listed below or filter and sort to narrow down your results.

0
answers
0
votes
17
views
asked 9 days ago

CodeBuild Bug? AWS CLI broken on AL2/aarch64 env, error "pyenv: version `3.9.7' is not installed"

## Summary: On CodeBuild projects running on AL2/aarch64, running the `aws` CLI command (any command works, I use `--version` as a sanity check) yields the following error: ``` [Container] 2022/09/10 02:39:37 Running command aws --version pyenv: version `3.9.7' is not installed (set by /codebuild/output/src576940877/src/.python-version) ``` The process exits with status code 1 and the build terminates. I can reproduce the error exactly on my M1 MBP running locally, following the instructions for local agent usage [here](https://docs.aws.amazon.com/codebuild/latest/userguide/use-codebuild-agent.html). ## Steps to Reproduce 1. Create minimal buildspec.yml: ```yml version: 0.2 phases: build: commands: - aws --version ``` 2. Launch on CodeBuild project set to AL2/aarch64, on SMALL size build. ## Expected behavior Build should pass. Output of command should be: ``` [Container] 2022/09/10 03:00:41 Running command /usr/local/bin/aws --version aws-cli/2.7.31 Python/3.9.11 Linux/5.10.104-linuxkit exe/aarch64.amzn.2 prompt/off ``` ## Actual behavior Output is actually: ``` [Container] 2022/09/10 02:39:37 Running command aws --version pyenv: version `3.9.7' is not installed (set by /codebuild/output/src576940877/src/.python-version) ``` ## Workaround The AWS CLI can be installed manually and run via direct path: ``` version: 0.2 phases: install: runtime-versions: python: 3.9 commands: - curl "https://awscli.amazonaws.com/awscli-exe-linux-aarch64.zip" -o "awscliv2.zip" - unzip awscliv2.zip - ./aws/install build: commands: - /usr/local/bin/aws --version ``` This produces the expected output and the build succeeds.
0
answers
0
votes
20
views
asked 15 days ago

How do we look up more verbose information by RequestID's thrown in AWS CloudFormation events which status reports CREATE_FAILED?

Without setting up a CloudTrail and executing a CFN template which rolls back, I have started looking at Debugging options. I found [this](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-api-logging-cloudtrail.html) which says we can see the most recent without a created trail. I tried to find RequestId documentation from [here](https://docs.aws.amazon.com/search/doc-search.html?searchPath=documentation-guide&searchQuery=resourceid&this_doc_product=AWS+CloudFormation&facet_doc_product=AWS+CloudFormation) entering 'requested' in the search bar, which returned many unrelated items to my specific case (thanks for the attempt Kendra:). I also have looked at cli docs [here](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-listing-event-history.html) I guess I fist need to know what a RequestID is capable of helping me trace, as I am doing a simple debug of an instance I already know that has the wrong AMI ID for that region, but am trying. to re-familiarize myself. with fixing CFN templates after being out of the loop for a few years. I'd like to know how someone else handles a CREATE _FAILED and ways to use the status reason in a verbose way. Each reason appears to be ';' separated, so even just a point in that direction might help weed through the mountain of information here. Thanks ahead of time- Rudy
0
answers
0
votes
26
views
asked 2 months ago