Problem:

I&#39;m trying to get the region of the authenticated user from boto3.

Use case:

I&#39;m working on adding cache to https://github.com/pmazurek/aws-fuzzy-finder. I would prefer to cache the result on *per-region* basis.

This package uses boto to get user authentication data (keys and the region). The problem is the region is never passed explicitly by the user, its being taken from one of the many murky places that boto reads so I don&#39;t really have a way of getting it. 

I have tried searching through boto3 api and googling, but couldn&#39;t find anything like a `get_region` or `get_user_data` method. Is it possible?

How to get the region of the current user from boto?

After giving all the rights to invoke function. My Lambda function is not able to invoke another function . Every time I am getting timeout having `30 seconds timeout` issue.  It looks like lambda is not able to get another lambda function

My lambdas are in same region, same policy, same security group .. Also VPC are same in both lambdas. The only thing is different now is lambda functions 

Here are the role rights 

1) created  `AWSLambdaExecute` and `AWSLambdaBasicExecutionRole` 

2) Created one lambda function which is to be called
**Lambda_TEST**

    exports.handler = function(event, context) {
      console.log(&#39;Lambda TEST Received event:&#39;, JSON.stringify(event, null, 2));
      context.succeed(event);
    };

3) Here is a another function from where it is called .

    var AWS = require(&#39;aws-sdk&#39;);
    AWS.config.region = &#39;us-east-1&#39;;
    var lambda = new AWS.Lambda();

    exports.handler = function(event, context) {
     var params = {
       FunctionName: &#39;Lambda_TEST&#39;, // the lambda function we are going to invoke
       InvocationType: &#39;RequestResponse&#39;,
       LogType: &#39;Tail&#39;,
       Payload: &#39;{ &quot;name&quot; : &quot;Arpit&quot; }&#39;
     };

      lambda.invoke(params, function(err, data) {
       if (err) {
        context.fail(err);
       } else {
       context.succeed(&#39;Lambda_TEST said &#39;+ data.Payload);
      }
     })
    };

Reference taken from : [This link][1]


  [1]: https://stackoverflow.com/questions/35754766/nodejs-invoke-an-aws-lambda-function-from-within-another-lambda-function

AWS lambda invoke not calling another lambda function - Node.js

I am at a loss of what I am doing wrong, here is what I have:

*HTML*

    &lt;html&gt;
    &lt;body&gt;
    	&lt;form method=&quot;POST&quot; action=&quot;/upload&quot; enctype=&quot;multipart/form-data&quot;&gt;
            &lt;div class=&quot;field&quot;&gt;
                &lt;label for=&quot;image&quot;&gt;Image Upload&lt;/label&gt;
                &lt;input type=&quot;file&quot; name=&quot;image&quot; id=&quot;image&quot;&gt;
            &lt;/div&gt;
            &lt;input type=&quot;submit&quot; class=&quot;btn&quot; value=&quot;Save&quot;&gt;
        &lt;/form&gt;
    &lt;/body&gt;
    &lt;/html&gt;

`Port` 5000 is my *Node.js* server&#39;s port.

In this example I am using `POST` to `/upload`, and it works fine.

    module.exports = function(app, models) {
    
        var fs = require(&#39;fs&#39;);
        var AWS = require(&#39;aws-sdk&#39;);
        var accessKeyId =  process.env.AWS_ACCESS_KEY || &quot;xxxxxx&quot;;
        var secretAccessKey = process.env.AWS_SECRET_KEY || &quot;+xxxxxx+B+xxxxxxx&quot;;
    
        AWS.config.update({
            accessKeyId: accessKeyId,
            secretAccessKey: secretAccessKey
        });
    
        var s3 = new AWS.S3();
    
        app.post(&#39;/upload&#39;, function(req, res){
           
            var params = {
                Bucket: &#39;makersquest&#39;,
                Key: &#39;myKey1234.png&#39;,
                Body: &quot;Hello&quot;
            };
    
            s3.putObject(params, function (perr, pres) {
                if (perr) {
                    console.log(&quot;Error uploading data: &quot;, perr);
                } else {
                    console.log(&quot;Successfully uploaded data to myBucket/myKey&quot;);
                }
            });
        });
    
    }

Now I want to post the file that I am `POST`ing, which is where the problem arises.

    module.exports = function(app, models) {
    
        var fs = require(&#39;fs&#39;);
        var AWS = require(&#39;aws-sdk&#39;);
        var accessKeyId =  process.env.AWS_ACCESS_KEY || &quot;xxxxxx&quot;;
        var secretAccessKey = process.env.AWS_SECRET_KEY || &quot;+xxxxxx+B+xxxxxxx&quot;;
    
        AWS.config.update({
            accessKeyId: accessKeyId,
            secretAccessKey: secretAccessKey
        });
    
        var s3 = new AWS.S3();
    
        app.post(&#39;/upload&#39;, function(req, res){
            var path = req.files.image.path;
            fs.readFile(path, function(err, file_buffer){
                var params = {
                    Bucket: &#39;makersquest&#39;,
                    Key: &#39;myKey1234.png&#39;,
                    Body: file_buffer
                };
    
                s3.putObject(params, function (perr, pres) {
                    if (perr) {
                        console.log(&quot;Error uploading data: &quot;, perr);
                    } else {
                        console.log(&quot;Successfully uploaded data to myBucket/myKey&quot;);
                    }
                });
            });
        });
    }

The error I get is:

&gt;TypeError: Cannot read property &#39;path&#39; of undefined

As a matter of fact `files` is completely empty.

I am assuming I am missing something pretty obvious but I can&#39;t seem to find it.

Simple file upload to S3 using aws-sdk and Node/Express

I am writing code to upload files to AWS S3 and receiving this exception:

&gt; AmazonClientException: No RegionEndpoint or ServiceURL configured

My code:

    Console.WriteLine(&quot;ready to upload&quot;);
    AWSCredentials credentials;
    credentials = new BasicAWSCredentials(accessKeyID.Trim(), secretKey.Trim());
    AmazonS3Client s3Client = new AmazonS3Client(accessKeyID.Trim(), secretKey.Trim(), Amazon.RegionEndpoint.USEast1);
    Console.WriteLine(&quot;Successful verification&quot;);
    Console.WriteLine(&quot;Check if the bucket exists&quot;);
    if (!CheckBucketExists(s3Client, bucketName))
    {
        s3Client.PutBucket(bucketName);
        Console.WriteLine(&quot;create bucket&quot;);
    }
    TransferUtility utility = new TransferUtility();
    Console.WriteLine(&quot;Upload  Directory......&quot;);
    //exception here
    utility.UploadDirectory(@&quot;E:\telerikFile\13ginabdfglil.com&quot;, bucketName);

The exception:

    Amazon.Runtime.AmazonClientException: No RegionEndpoint or ServiceURL configured
      Amazon.Runtime.ClientConfig.Validate()
      Amazon.S3.AmazonS3Config.Validate()
      Amazon.Runtime.AmazonServiceClient..ctor(AWSCredentials credentials, ClientConfig config)
      Amazon.S3.AmazonS3Client..ctor()
      Amazon.S3.Transfer.TransferUtility..ctor()
      Telerik2Amazon.Program.UploadFile()

What should I do?

No RegionEndpoint or ServiceURL configured

Getting the following exception when using the AWS SDK for Java and Java 1.8u60+.

    com.amazonaws.services.s3.model.AmazonS3Exception: AWS authentication requires a valid Date or x-amz-date header (Service: Amazon S3; Status Code: 403; Error Code: AccessDenied; Request ID: 41C359C079CBAFCF)
        at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1182) ~[aws-java-sdk-core-1.10.10.jar:na]
        at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:770) ~[aws-java-sdk-core-1.10.10.jar:na]
        at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:489) ~[aws-java-sdk-core-1.10.10.jar:na]
        at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:310) ~[aws-java-sdk-core-1.10.10.jar:na]
        at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3608) ~[aws-java-sdk-s3-1.10.10.jar:na]
        at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3561) ~[aws-java-sdk-s3-1.10.10.jar:na]
        at com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:647) ~[aws-java-sdk-s3-1.10.10.jar:na]
        at com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:632) ~[aws-java-sdk-s3-1.10.10.jar:na]

AWS Java SDK - AWS authentication requires a valid Date or x-amz-date header

Can someone explain how to fix a missing config error with Node.js? I&#39;ve followed all the examples from the [aws doc page](http://docs.aws.amazon.com/AWSJavaScriptSDK/guide/node-configuring.html) but I still get this error no matter what.

    { [ConfigError: Missing region in config]
    message: &#39;Missing region in config&#39;,
    code: &#39;ConfigError&#39;,
    time: Wed Jun 24 2015 21:39:58 GMT-0400 (EDT) }&gt;{ thumbnail: 
     { fieldname: &#39;thumbnail&#39;,
     originalname: &#39;testDoc.pdf&#39;,
     name: &#39;testDoc.pdf&#39;,
     encoding: &#39;7bit&#39;,
     mimetype: &#39;application/pdf&#39;,
    path: &#39;uploads/testDoc.pdf&#39;,
     extension: &#39;pdf&#39;,
     size: 24,
     truncated: false,
     buffer: null } }
     POST / 200 81.530 ms - -

Here is my code:

    var express = require(&#39;express&#39;);
    var router = express.Router();
    var AWS = require(&#39;aws-sdk&#39;);
    var dd = new AWS.DynamoDB();
    var s3 = new AWS.S3();
    var bucketName = &#39;my-bucket&#39;;
    
    AWS.config.update({region:&#39;us-east-1&#39;});

    (...)

Configuring region in Node.js AWS SDK

I get an error `AWS::S3::Errors::InvalidRequest The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.` when I try upload file to S3 bucket in new Frankfurt region. All works properly with `US Standard` region.

Script:

    backup_file = &#39;/media/db-backup_for_dev/2014-10-23_02-00-07/slave_dump.sql.gz&#39;
    s3 = AWS::S3.new(
        access_key_id:     AMAZONS3[&#39;access_key_id&#39;],
        secret_access_key: AMAZONS3[&#39;secret_access_key&#39;]
    )
 
    s3_bucket = s3.buckets[&#39;test-frankfurt&#39;]
 
    # Folder and file name
    s3_name = &quot;database-backups-last20days/#{File.basename(File.dirname(backup_file))}_#{File.basename(backup_file)}&quot;
 
    file_obj = s3_bucket.objects[s3_name]
    file_obj.write(file: backup_file)

aws-sdk (1.56.0)

How to fix it?

Thank you.

The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256

I&#39;m aware of the existence of https://wiki.apache.org/hadoop/AmazonS3 and the following words:

&gt; S3 Native FileSystem (URI scheme: s3n) A native filesystem for reading and writing regular files on S3. The advantage of this filesystem is that you can access files on S3 that were written with other tools. Conversely, other tools can access files written using Hadoop. The disadvantage is the 5GB limit on file size imposed by S3.
&gt;
&gt; S3A (URI scheme: s3a) A successor to the S3 Native, s3n fs, the S3a: system uses Amazon&#39;s libraries to interact with S3. This allows S3a to support larger files (no more 5GB limit), higher performance operations and more. The filesystem is intended to be a replacement for/successor to S3 Native: all objects accessible from s3n:// URLs should also be accessible from s3a simply by replacing the URL schema.
&gt;
&gt; S3 Block FileSystem (URI scheme: s3) A block-based filesystem backed by S3. Files are stored as blocks, just like they are in HDFS. This permits efficient implementation of renames. This filesystem requires you to dedicate a bucket for the filesystem - you should not use an existing bucket containing files, or write other files to the same bucket. The files stored by this filesystem can be larger than 5GB, but they are not interoperable with other S3 tools.


Why a letter change on the URI could make such difference? For example 

    val data = sc.textFile(&quot;s3n://bucket-name/key&quot;)

to 

    val data = sc.textFile(&quot;s3a://bucket-name/key&quot;)

What is the technical difference underlying this change? Are there any good articles that I can read on this?





Technically what is the difference between s3n, s3a and s3?

In a Node.js project I am attempting to get data back from S3. 

When I use `getSignedURL`, everything works: 

    aws.getSignedUrl(&#39;getObject&#39;, params, function(err, url){
        console.log(url); 
    }); 

My params are: 
    
    var params = {
                  Bucket: &quot;test-aws-imagery&quot;, 
                  Key: &quot;TILES/Level4/A3_B3_C2/A5_B67_C59_Tiles.par&quot;

If I take the URL output to the console and paste it in a web browser, it downloads the file I need.  

However, if I try to use `getObject` I get all sorts of odd behavior.  I believe I am just using it incorrectly.  This is what I&#39;ve tried: 

    aws.getObject(params, function(err, data){
        console.log(data); 
        console.log(err); 
    }); 

Outputs: 
    
    { 
      AcceptRanges: &#39;bytes&#39;,
      LastModified: &#39;Wed, 06 Apr 2016 20:04:02 GMT&#39;,
      ContentLength: &#39;1602862&#39;,
      ETag: &#39;9826l1e5725fbd52l88ge3f5v0c123a4&quot;&#39;,
      ContentType: &#39;application/octet-stream&#39;,
      Metadata: {},
      Body: &lt;Buffer 01 00 00 00  ... &gt; }

      null

So it appears that this is working properly.  However, when I put a breakpoint on one of the `console.log`s, my IDE (NetBeans) throws an error and refuses to show the value of data. While this could just be the IDE, I decided to try other ways to use `getObject`. 

    aws.getObject(params).on(&#39;httpData&#39;, function(chunk){
        console.log(chunk); 
    }).on(&#39;httpDone&#39;, function(data){
        console.log(data); 
    });

This does not output anything.  Putting a breakpoint in shows that the code never reaches either of the `console.log`s.  I also tried: 

    aws.getObject(params).on(&#39;success&#39;, function(data){
        console.log(data); 
    });

However, this also does not output anything and placing a breakpoint shows that the `console.log` is never reached. 

What am I doing wrong?

 

How to get response from S3 getObject in Node.js?

Let&#39;s say that I have a machine that I want to be able to write to a certain log file stored on an S3 bucket.

So, the machine needs to have writing abilities to that bucket, but, I don&#39;t want it to have the ability to overwrite or delete any files in that bucket (including the one I want it to write to). 

So basically, I want my machine to be able to only append data to that log file, without overriding it or downloading it.

Is there a way to configure my S3 to work like that? Maybe there&#39;s some IAM policy I can attach to it so it will work like I want?

Append data to an S3 object

I would like to check if a key exists in a given bucket using Java. I looked at the API but there aren&#39;t any methods that are useful. I tried to use `getObject` but it threw an exception.


How to check if a specified key exists in a given S3 bucket using Java

I have the following function which I use to invoke a Lambda function from within my code.

However when I try to use it within a Lambda function, I get the following error: 

    AWS lambda undefined 0.27s 3 retries] invoke({ FunctionName: &#39;my-function-name&#39;,
      InvocationType: &#39;RequestResponse&#39;,
      LogType: &#39;Tail&#39;,
      Payload: &lt;Buffer &gt; })

How can I invoke a Lambda function from within a Lambda function?

My function:

    &#39;use strict&#39;;
    
    var AWS = require(&quot;aws-sdk&quot;);
    
    var lambda = new AWS.Lambda({
        apiVersion: &#39;2015-03-31&#39;,
        endpoint: &#39;https://lambda.&#39; + process.env.DYNAMODB_REGION + &#39;.amazonaws.com&#39;,
        logger: console
    });
    
    var lambdaHandler = {};
    
    // @var payload - type:string
    // @var functionName - type:string
    lambdaHandler.invokeFunction = function (payload, functionName, callback) {
    
        var params = {
            FunctionName: functionName, /* required */
            InvocationType: &quot;RequestResponse&quot;,
            LogType: &quot;Tail&quot;,
            Payload: new Buffer(payload, &#39;utf8&#39;)
        };
    
        var lambdaRequestObj = lambda.invoke(params);
    
        lambdaRequestObj.on(&#39;success&#39;, function(response) {
            console.log(response.data);
        });
    
        lambdaRequestObj.on(&#39;error&#39;, function(response) {
            console.log(response.error.message);
        });
    
        lambdaRequestObj.on(&#39;complete&#39;, function(response) {
            console.log(&#39;Complete&#39;);
        });
    
        lambdaRequestObj.send();
    
        callback();
    };
    
    module.exports = lambdaHandler;

Nodejs - Invoke an AWS.Lambda function from within another lambda function

Maybe this is just me experiencing such an annoying &quot;feature&quot;:

After upgrading from Xcode 6.0.1 to Xcode 6.1, things changed. Xcode 6.1 is forever indexing the project or compiling source files. The project is not a huge one. It just contains a bunch of Swift files and AWS SDK 2.0 Cocoapods in the workspace. I don&#39;t think it should prevent the whole to index and compile smoothly. I tried with some aws-sdk-ios-samples, just to see how Xcode 6.1 works on them, and it ended up in the same forever waiting.

What solutions I have tried so far:
 
 1. Deleting &quot;Derived Data&quot; in the Organizer, and re-open and workspace. (fail to fix)
 2. &quot;Show Package Contents&quot; on the .xcodeproj file and deleting .xcworkspace as in (https://stackoverflow.com/questions/6355667/xcode-4-slow-performance)

None of them worked, unfortunately.

P.S. maybe I should try re-creating the project?
My computer settings:
MacBook Pro (Retina, 13-inch, Mid 2014), Memory 8 GB 1600 MHz DDR3, with Yosemite. (I think this is enough for running this small project.)

Swift Xcode Index Freezing or Slow

I am working with the AWS SDK using the KMS libary. I would like to use async and await instead of callbacks.

    import AWS, { KMS } from &quot;aws-sdk&quot;;
    
    this.kms = new AWS.KMS();
    
    const key = await this.kms.generateDataKey();


However this does not work, when wrapped in an async function.

How can i use async and await here?

How to use Async and Await with AWS SDK Javascript

I am trying to send SNS messeges to android through web api.
Downloaded and installed the SDK from http://aws.amazon.com/developers/getting-started/php/

Got following error while running sample.php:

    Fatal error: Uncaught exception &#39;Aws\Common\Exception\InstanceProfileCredentialsException&#39; with message &#39;Error retrieving credentials from the instance profile metadata server. When you are not running inside of Amazon EC2, you must provide your AWS access key ID and secret access key in the &quot;key&quot; and &quot;secret&quot; options when creating a client or provide an instantiated Aws\Common\Credentials\CredentialsInterface object. ([curl] 28: Connection timed out after 5016 milliseconds [url] http://169.254.169.254/latest/meta-data/iam/security-credentials/)&#39; in C:\xampp\htdocs\aws-php\vendor\aws\aws-sdk-php\src\Aws\Common\InstanceMetadata\InstanceMetadataClient.php:85 Stack trace: #0 C:\xampp\htdocs\aws-php\vendor\aws\aws-sdk-php\src\Aws\Common\Credentials\RefreshableInstanceProfileCredentials.php(52): Aws\Common\InstanceMetadata\InstanceMetadataClient-&gt;getInstanceProfileCredentials() #1 C:\xampp\htdocs\aws-php\vendor\aws\aws-sdk-php\src\Aws\Common\Credentials\AbstractRefreshableCredentials.php(54): Aws\Common\Credentials\Refreshable in C:\xampp\htdocs\aws-php\vendor\aws\aws-sdk-php\src\Aws\Common\InstanceMetadata\InstanceMetadataClient.php on line 85

A little guidance on this topic will help me a lot


AWS SDK for PHP: Error retrieving credentials from the instance profile metadata server

I&#39;m getting the error &quot;The role defined for the function cannot be assumed by Lambda&quot; when I&#39;m trying to create a lambda function with create-function command.

&gt;    aws lambda create-function  
&gt; --region us-west-2  
&gt; --function-name HelloPython  
&gt; --zip-file fileb://hello_python.zip  
&gt; --role arn:aws:iam::my-acc-account-id:role/default   
&gt; --handler hello_python.my_handler  
&gt; --runtime python2.7  
&gt; --timeout 15  
&gt; --memory-size 512

The role defined for the function cannot be assumed by Lambda

I&#39;m trying to read the files available on Amazon S3, as the question explains the problem. I couldn&#39;t find an alternative call for the deprecated constructor.

Here&#39;s the code:

    private String AccessKeyID = &quot;xxxxxxxxxxxxxxxxxxxx&quot;;
    private String SecretAccessKey = &quot;xxxxxxxxxxxxxxxxxxxxxxxxxxxxx&quot;;
    private static String bucketName     = &quot;documentcontainer&quot;;
    private static String keyName     = &quot;test&quot;;
    //private static String uploadFileName    = &quot;/PATH TO FILE WHICH WANT TO UPLOAD/abc.txt&quot;;

    AWSCredentials credentials = new BasicAWSCredentials(AccessKeyID, SecretAccessKey);

    void downloadfile() throws IOException
    {

        // Problem lies here - AmazonS3Client is deprecated
        AmazonS3 s3client = new AmazonS3Client(credentials);
            try {
            System.out.println(&quot;Downloading an object...&quot;);
            S3Object s3object = s3client.getObject(new GetObjectRequest(
                    bucketName, keyName));
            System.out.println(&quot;Content-Type: &quot;  +
                    s3object.getObjectMetadata().getContentType());
            InputStream input = s3object.getObjectContent();

            BufferedReader reader = new BufferedReader(new InputStreamReader(input));
            while (true) {
                String line = reader.readLine();
                if (line == null) break;

                System.out.println(&quot;    &quot; + line);
            }
            System.out.println();
        } catch (AmazonServiceException ase) {
              //do something
        } catch (AmazonClientException ace) {
            // do something
        }
     }

Any help? If more explanation is needed please mention it.
I have checked on the sample code provided in .zip file of SDK, and it&#39;s the same.

AmazonS3Client(credentials) is deprecated

I have gone through the question titled &quot;Setting the AWS region programmatically 1&quot; but it doesn&#39;t provide all the answers I need.

Q1: I&#39;m getting a `SDKClientException-Unable to find a region via the region provider chain`. What am I doing wrong? or is there a typo that I missed.

    public class CreateS3Bucket {

	public static void main(String[] args) throws IOException {
		
		BasicAWSCredentials creds = new BasicAWSCredentials(&quot;aws-access-key&quot;, &quot;aws-secret-key&quot;);
		AmazonS3 s3Client = AmazonS3ClientBuilder.standard().withCredentials(new AWSStaticCredentialsProvider(creds)).build();
		
		Region region = Region.getRegion(Regions.US_EAST_1);
		s3Client.setRegion(region);
		
		try {
			String bucketName = &quot;testBucket&quot; + UUID.randomUUID();
			s3Client.createBucket(bucketName);
			System.out.println(&quot;Bucket Created Successfully.&quot;);
		
		} catch(AmazonServiceException awse) {
			
			System.out.println(&quot;This means that your request made it AWS S3 but got rejected&quot;);
			System.out.println(&quot;Error Message:&quot; +awse.getMessage());
			System.out.println(&quot;Error Message:&quot; +awse.getErrorCode());
			System.out.println(&quot;Error Message:&quot; +awse.getErrorType());
			System.out.println(&quot;Error Message:&quot; +awse.getRequestId());
			
		} catch (AmazonClientException ace) {
			
			System.out.println(&quot;The Amazon Client encountered an Error with network Connectivity&quot;);
			System.out.println(&quot;Error Message:&quot; + ace.getMessage());
		}
		
		
	}

}

Q2: What code changes needs to be done if I want to build a Lambda Function out of it? I&#39;m aware how to create a lambda function and roles that it needs. Just need to know if the code that I have written needs to changed. How should I implement the LambdaFuctionHandler class as below:

    import com.amazonaws.services.lambda.runtime.Context;
    import com.amazonaws.services.lambda.runtime.RequestHandler;

     public class LambdaFunctionHandler implements RequestHandler&lt;String, String&gt; {

    @Override
    public String handleRequest(String input, Context context) {
        context.getLogger().log(&quot;Input: &quot; + input);

        
        return null;
    }

    }




AWS Java SDK - Unable to find a region via the region provider chain

I&#39;ve been going through AWS DynamoDB docs and, for the life of me, cannot figure out what&#39;s the core difference between batchGetItem() and Query(). Both retrieve items based on primary keys from tables and indexes. The only difference is in the size of the items retrieved but that doesn&#39;t seem like a ground breaking difference. Both also support conditional updates.

In what cases should I use batchGetItem over Query and vice-versa?

What&#39;s the difference between BatchGetItem and Query in DynamoDB?

I want to delete a file from Amazon S3 using Javascript. I have already uploaded the file using Javascript. Any ideas?

How do I delete an object on AWS S3 using Javascript?

I am getting an error when calling to `assume role` method of STS. It says that the user is not authorized to perform `sts:AsumeRole` on resource `xxx`.

I did the following:

 1. I created a role to access to S3 bucket.
 2. I ran a test over policy simulator and works fine
 3. I created a new group, and in it, i created a new policy that
    enables all sts actions, over all resources.
 4. I ran a test with the policy simulator, to sts assume role, pointing
    to the ARN of role created at step one; and it works fine
 5. I created a new user, and put it in group created at step 3
 6. With the credentials of the new user, i try to get a new credentials
    using sts asume role, but throw me an error that say my user is not
    authorized to perform sts:AssumeRole

What am I doing wrong?

Policy in Group

    {
        &quot;Version&quot;: &quot;2012-10-17&quot;,
        &quot;Statement&quot;: [
            {
                &quot;Sid&quot;: &quot;some-large-id&quot;,
                &quot;Effect&quot;: &quot;Allow&quot;,
                &quot;Action&quot;: [
                    &quot;sts:*&quot;
                ],
                &quot;Resource&quot;: [
                    &quot;*&quot;
                ]
            }
        ]
    }

Policy in role

    {
        &quot;Version&quot;: &quot;2012-10-17&quot;,
        &quot;Statement&quot;: [
            {
                &quot;Sid&quot;: &quot;another-large-id&quot;,
                &quot;Effect&quot;: &quot;Allow&quot;,
                &quot;Action&quot;: [
                    &quot;s3:PutObject&quot;
                ],
                &quot;Resource&quot;: [
                    &quot;arn:aws:s3:::my-bucket-name/*&quot;
                ]
            }
        ]
    }

And finally calling like this

    let policy = {
    	&quot;Version&quot;: &quot;2012-10-17&quot;,
    	&quot;Statement&quot;: [
    		{
    			&quot;Sid&quot;: &quot;new-custom-id&quot;,
    			&quot;Effect&quot;: &quot;Allow&quot;,
    			&quot;Action&quot;: [&quot;s3:PutObject&quot;],
    			&quot;Resource&quot;: [&quot;arn:aws:s3:::my-bucket-name/*&quot;]
    		}
    	]
    };
    
    let params = {
    	DurationSeconds: 3600, 
    	ExternalId: &#39;some-value&#39;, 
    	Policy: JSON.stringify(policy), 
    	RoleArn: &quot;arn:aws:iam::NUMBER:role/ROLE-NAME&quot;, //Cheked, role is the same that step one
    	RoleSessionName: this.makeNewSessionId()
    };
    let sts = new AWS.STS({ apiVersion: &#39;2012-08-10&#39; });
    
    sts.assumeRole(params, (err, data) =&gt; {
    	if(err) console.log(err);
    	else console.log(data);
    });

All Aws Sdk Solutions on Gang of Coders

Total of 21 Aws Sdk Solutions