> For the complete documentation index, see [llms.txt](https://notes.morph3.blog/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://notes.morph3.blog/cloud.md).

# Cloud

* <https://docs.aws.amazon.com/cli/latest/reference/index.html#cli-aws>

## Basic Commands

```
aws s3 ls s3://<bucketname>
aws s3 cp ./poc.txt s3://<bucketname>/poc.txt
aws s3 sync s3://<bucketname>
```

## If you have Access Key and Secret Key

Command below enumerates your access and secret key. Additional buckets can be found via this way.

```
python3 /opt/enumerate-iam/enumerate-iam.py --access-key <accesskey> --secret-key <secretkey>
```

Set your credentials under `~/.aws/credentials`

```
❯ cat ~/.aws/credentials
[default]
aws_access_key_id = <accesskey>
aws_secret_access_key = <secretkey>
```

Some s3api command examples

```
aws s3api list-buckets --query "Buckets[].Name"
aws s3api get-bucket-tagging --bucket <bucketname>
```

If the key has access to lambda function we can check what functions it have

```
aws lambda list-functions
aws lambda list-tags --resource arn:aws:lambda:eu-west-1:957405373060:function:lambdaThrusters-8697c51
```

EC2

```
aws ec2 describe-tags
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://notes.morph3.blog/cloud.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
