AWS Lambda CLI gives incorrect(?) error about S3 bucket being in incorrect region

Question

I am running this Bash command:
```
aws lambda publish-layer-version \
    --layer-name pythonPackages \
    --content S3Bucket=dev-file-transfer,S3Key=lambda_layer_python_packages.zip \
    --compatible-runtimes python3.12 \
    --compatible-architectures arm64
```
It gives this error:
```
An error occurred (InvalidParameterValueException) when calling the PublishLayerVersion operation: Error occurred while GetObject. S3 Error Code: PermanentRedirect. S3 Error Message: The bucket is in this region: us-west-1. Please use this region to retry the request
```
saying that the S3 bucket I am working with exists in the us-west-1 region.

But, it doesn't. Everything I have is in us-east-1.
![Enter image description here](/media/postImages/original/IM0sjg-ST9SPeTqkIQU0gEJw)

I have no buckets in us-west-1.

Any ideas how to get around this? Is it a bug?

Accepted Answer

I realized immediately after posting that I am using the wrong bucket name in my command. Someone else owns `dev-file-transfer` and it must be located in us-west-1.

AWS Lambda CLI gives incorrect(?) error about S3 bucket being in incorrect region

Relevanter Inhalt