I am trying lớn delete uploaded image files with the AWS-SDK-Core Ruby Gem.

I have the following code:

require 'aws-sdk-core'

def pull_picture(picture)
    Aws.config = {
        :access_key_id => ENV["AWS_ACCESS_KEY_ID"],
        :secret_access_key => ENV["AWS_SECRET_ACCESS_KEY"],
        :region => 'us-west-2'
    }

    s3 = Aws::S3::Client.new

    test = s3.get_object(
        :bucket => ENV["AWS_S3_BUCKET"],
        :key => picture.image_url.split('/')[-2],   
    )
end

However, I am getting the following error:

The bucket you are attempting lớn access must be addressed using the specified endpoint. Please send all future requests lớn this endpoint.

I know the region is correct because if I change it lớn us-east-1, the following error shows up:

The specified key does not exist.

What am I doing wrong here?

asked Jul 30, năm trước at 1:32

1

It seems likely that this bucket was created in a different region, IE not us-west-2. That's the only time I've seen "The bucket you are attempting lớn access must be addressed using the specified endpoint. Please send all future requests lớn this endpoint."

US Standard is us-east-1

blnc

4,4041 gold badge29 silver badges42 bronze badges

answered Nov 4, năm trước at 0:26

12

I was facing a similar error because the bucket was in region us-west-2 and the URL pattern had bucketname in the path. Once, I changed the URL pattern lớn have bucketname as URL subdomain lớn grab the files and it worked.

For eg previous URL was

https://s3.amazonaws.com/bucketname/filePath/filename

Then I replaced it as

https://bucketname.s3.amazonaws.com/filePath/filename

answered Oct 6, năm nhâm thìn at 6:49

1

After a long tìm kiếm, I found a working solution. The issue was because of the wrong region-code.

below is the list of region-codes, mix the appropriate one and your issue will be solved.

Code                         Name
US East (Ohio)               us-east-2

US East (N. Virginia)       us-east-1

US West (N. California)     us-west-1

US West (Oregon)            us-west-2

Asia Pacific (Hong Kong)    ap-east-1

Asia Pacific (Mumbai)       ap-south-1

Asia Pacific (Osaka-Local)  ap-northeast-3

Asia Pacific (Seoul)        ap-northeast-2

Asia Pacific (Singapore)    ap-southeast-1

Asia Pacific (Sydney)       ap-southeast-2

Asia Pacific (Tokyo)        ap-northeast-1

Canada (Central)            ca-central-1

Europe (Frankfurt)          eu-central-1

Europe (Ireland)            eu-west-1

Europe (London)             eu-west-2

Europe (Paris)             eu-west-3

Europe (Stockholm)         eu-north-1

Middle East (Bahrain)      me-south-1

South America (São Paulo)   sa-east-1

You can find your region-code on click of bucket name right corner.

For mode details Click

answered Dec 27, 2019 at 15:21

In my case, I selected wrong RegionEndpoint. After selecting the correct RegionEndpoint, it started working :)

answered Sep 24, 2020 at 12:58

For those of you using @aws-sdk/client-s3, just be sure lớn supply the bucket's region lớn the client before you send the command. Get it with the CLI:

$ aws s3api get-bucket-location --bucket 
{
    "LocationConstraint": "ca-central-1"
}

const client = new S3Client({ region: "ca-central-1", credentials...

answered Mar 9, 2022 at 22:48

2

Though S3 bucket is global but while accessing bucket we need lớn give region. I was getting error in .netcore, Once I added region in below code, it start working.

var s3Client = new AmazonS3Client(Amazon.RegionEndpoint.USWest2);

answered Jan 19, 2022 at 15:08

In C# you can tự a following kiểm tra, I assume, similar code is possible with other SDKs:

        var client = new AmazonS3Client(
            credentials.AccessKey,
            credentials.ClientSecret,
            new AmazonS3Config{}
        );

        var bucketLocationRequest = new GetBucketLocationRequest
        {
            BucketName = amazonS3Bucket.BucketName
        };

        var response = await client.GetBucketLocationAsync(bucketLocationRequest);
        var region = response.Location;

        var regionEndpoint = region != null ? RegionEndpoint.GetBySystemName(region.Value) : RegionEndpoint.EUCentral1;
       
        var clientWithRegion = new AmazonS3Client(
            credentials.AccessKey,
            credentials.ClientSecret,
            new AmazonS3Config
            {
                RegionEndpoint = regionEndpoint
            }
        );

answered Jul 10, 2022 at 19:32

1

Look at your aws-exports config tệp tin, there should already u a region, just selected the same region.

mine was: "aws_project_region": "us-east-2"

So I put region: 'us-east-2'

Worked for u.

answered Sep 1, 2023 at 2:58

1

None of the above answers fixed my issue.

The above answers are probably more likely the cause of your problem but my issue was that I was using the wrong bucket name. It was a valid bucket name, it just wasn't my bucket.

The bucket I was pointing lớn was in a different region that my lambda function so sánh kiểm tra your bucket name!

answered May 15, 2019 at 13:48

I encountered this issue when using a different AWS profile. I saw the error when I was using an tài khoản with admin permissions, so sánh the possibility of permissions issues seemed unlikely.

It's really a pet peeve of mine that AWS is so sánh prone lớn issuing error messages that have such little correlation with the required actions, from a user perspective.

answered Mar 4, 2020 at 16:27

In my case the bucket name was wrong.

answered May 6, 2022 at 4:28

For many S3 API packages (I recently had this problem the npm s3 package) you can run rẩy into issues where the region is assumed lớn be US Standard, and lookup by name will require you lớn explicitly define the region if you choose lớn host a bucket outside of that region.

answered Mar 16, năm nhâm thìn at 2:44

For ppl who are still facing this issue, try adding s3_host as follows lớn the config hash

   :storage => :s3,
   :s3_credentials => {:access_key_id => access key,
   :secret_access_key => secret access key},
   :bucket => bucket name here,
   :s3_host_name => s3-us-west-1.amazonaws.com or whatever comes as per your region}.

This fixed the issue for u.

answered Jan 25, 2017 at 7:21

I had same error. It occurred when s3 client was created with different endpoint phàn nàn the one which was mix up while creating bucket.

  • ERROR CODE - The bucket was mix up with EAST Region.

s3Client = New AmazonS3Client(AWS_ACCESS_KEY, AWS_SECRET_KEY, RegionEndpoint.USWest2)

  • FIX

s3Client = New AmazonS3Client(AWS_ACCESS_KEY, AWS_SECRET_KEY, RegionEndpoint.USEast1)

answered Dec 27, 2018 at 14:03

During the creation of S3Client you can specify the endpoint mapping lớn a particular region. If mặc định of s3.amazonaws.com then bucket will be created in us-east-1 which is North Virginia.

More details on S3 endpoints and regions in AWS docs: http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region.

So, always make sure about the endpoint/region while creating the S3Client and access S3 resouces using the same client in the same region.

If the bucket is created from AWS S3 Console, then kiểm tra the region from the console for that bucket then create a S3 Client in that region using the endpoint details mentioned in the above links.

answered Oct 21, 2017 at 20:48

I Have faced the same issue.After a lot of struggle I found that the real issue is with the com.amazonaws dependencies.After adding dependencies this error got disappeared.

answered Jan 26, 2019 at 10:47

I got this exception on c#.net, It was fixed after changing the RegionEndpoint value on client creation as below

var client = new AmazonS3Client(accesKey,secretKey, RegionEndpoint.APSoutheast2)

answered Nov 24, 2022 at 5:32 

Had the same issue when executing gitlab pipeline with Terraform. Resolved by adding correct provider region lớn provider.tf

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 5.0"
    }
    awscc = {
      source  = "hashicorp/awscc"
      version = "~> 0.1"
    }
  }

provider "awscc" {
  region = "Region of s3 bucket"
}

I got this error when I tried lớn access a bucket that didn't exist.

I mistakenly switched a path variable with the bucket name variable and so sánh the bucket name had the tệp tin path value. So maybe double-check, if the bucket name that you mix on your request is correct.

answered May 2, 2018 at 13:07

I live in uk was keep on trying for 'us-west-2'region. So redirected lớn 'eu-west-2'. The correct region for S3 is 'eu-west-2'

answered Sep 27, 2019 at 12:35

This occurred for u when I had a source ip constraint on the policy being used by the user (access key / secret key) lớn create the s3 bucket. My IP was accurate--but for some reason it wouldn't work and gave this error.

answered Oct 2, 2019 at 1:46