When sending an SQS message, the library attempts to flatten the extra parameters from sendMessage() at sqs-2012-11-15.dart:1681 in the auto generated package. The optional parameters are for the messageAttributes (Map<String, MessageAttribute>) and messageSystemAttributes (Map<String, MessageSystemAttribute>). Somewhere down the line, send() gets called at query.dart:42 in the shared auto generated package which calls _buildRequest() > flatQueryParams() > _flatten() all in the same file. _flatten checks for the type to flatten it for the request but fails because there is no case to handle MessageAttribute or MessageSystemAttribute. I would fix and submit another PR but I don't really have the time. Here is the error:

[VERBOSE-2:ui_dart_state.cc(157)] Unhandled Exception: Invalid argument(s): Unknown type at "MessageAttributes.entry.1.value": MessageAttributeValue (Instance of 'MessageAttributeValue')
#0      _flatten (package:shared_aws_api/src/protocol/query.dart:140:3)
#1      _SyncIterator.moveNext (dart:core-patch/core_patch.dart:146:12)
#2      _SyncIterator.moveNext (dart:core-patch/core_patch.dart:139:32)
#3      _SyncIterator.moveNext (dart:core-patch/core_patch.dart:139:32)
#4      MapMixin.addEntries (dart:collection/maps.dart:172:23)
#5      new Map.fromEntries (dart:core/map.dart:187:17)
#6      flatQueryParams (package:shared_aws_api/src/protocol/query.dart:89:14)
#7      QueryProtocol._buildRequest (package:shared_aws_api/src/protocol/query.dart:74:26)
#8      QueryProtocol.send (package:shared_aws_api/src/protocol/query.dart:49:16)
#9      SQS.sendMessage (package:aws_sqs_api/sqs-2012-11-05.dart:1705:37)

EDIT: Here is my code causing the error:

    sqs.sendMessage(
        messageBody: unsentEntries[i].toJson().toString(),
        queueUrl: sqsUrl,
        messageGroupId: unsentEntries[i].company.shortName.replaceAll(' ', ''),
        messageDeduplicationId: utils.getUuid(),
        messageAttributes: <String, MessageAttributeValue>{
          'companyId': new MessageAttributeValue(dataType:'string', stringValue: unsentEntries[i].company.id)
        });

Suggestion

I suggest a discussion about a general solution in order to make a feature complete Dart AWS SDK.

What has been done

I made an attempt to generate all AWS services, statically typed, by building a general source code generator. This seemed promising until I realised all nuances and the complexity of AWS services in aggregate.

Idea

Why not copy the JS SDK architecture, and just type it statically at the bounds of the API.

TypedClassInputArgument -> serviceFunction() -> TypedClassInputArgument.toJson() -> JS SDK implemented in Dart -> JSON -> TypedClassOutput.fromJson()

By this design, the architecture and reference implementation would be given. Most of the specifics of Dart, such as signing requests, etc, is already solved. The underlying architecture would need to be implemented, such as the core and protocols.

It would then be as easy as to prepend a JSON defined API with final Map<String, dynamic> definition = and rename the file to .dart in order to have a statically compilable Dart Map to load in runtime.

Hello,

The headers map passed to the send() function of the RestXmlProtocol is not passed to the _buildRequest() method and are not sent to the server. As a result, S3 object metadatas cannot be uploaded.

try {
      CognitoAuthSession session = await Amplify.Auth.fetchAuthSession(
          options: CognitoSessionOptions(getAWSCredentials: true));

      AwsClientCredentials cred = AwsClientCredentials(
          accessKey: session.credentials.awsAccessKey,
          secretKey: session.credentials.awsSecretKey,
          sessionToken: session.credentials.sessionToken);

      final service = Lambda(region: region, credentials: cred);

      try {
        List<int> list =
            '{"key1": "value1","key2": "value2","key3": "value3"}'.codeUnits;

        InvocationResponse updateItemOutput = await service.invoke(
            functionName: "amplify-lambda-invoke-test",
            invocationType: InvocationType.event,
            payload: Uint8List.fromList(list));
        print(updateItemOutput.payload);
      } catch (e) {
        print("asd");
        print(e);
      }
    } on AuthError catch (e) {
      print(e);
    }

This code snippet successfully invokes a lambda function but it returns a catch error "202 UnknownError: 202". Whereas this functions response should be "Hello from lambda". What am I doing wrong?

I would like better type safety and user ergonomics for enumerated parameters.

A suggestion would be enums with extensions:

enum AttributeAction {
  ADD,
  PUT,
  DELETE
}

extension on AttributeAction {
  String get name {
    switch (this) {
      case AttributeAction.ADD:
        return 'ADD';
      case AttributeAction.PUT:
        return 'PUT';
      case AttributeAction.DELETE:
        return 'DELETE';
    }
    throw Exception('This will never throw');
  }
}

This would be received as such:

foo(AttributeAction action) {
  bar(action.name)
}

And the call foo() would be:

foo(AttributeAction.ADD) ;

@isoos, what do you think?

/cc @Schwusch

The current aws_client/lib/generated directory is 28MB. package:googleapis is a similar package, it is generated from service definitions, and it already had issues on pub.dev with dartdoc-generation or analysis timing out.

Should we aim for N smaller packages instead of one big "everything-in-it" package?

I've made an AWS SDK generator and I thought I'd show one of the services it generates for you to give your thoughts on. If there is interest, I can provide the other AWS services as well.

Hello, s3 upload successful but throws error return error message = ""<" expected"

My code:

try {
  await service.putObject(
    bucket: bucketName,
    key: fileName,
    body: imageFile.readAsBytesSync(),
    acl: ObjectCannedACL.publicRead,
  );
} catch (ex) {
  var error= ex;
}

When using CloudWatch.putMetricData(), this error is observed:

MalformedInput Sender: timestamp must follow ISO8601
#0 QueryProtocol.send (package:shared_aws_api/src/protocol/query.dart:100:7)
<asynchronous suspension>
#1 CloudWatch.putMetricData (package:aws_cloudwatch_api/monitoring-2010-08-01.dart:2605:5)
<asynchronous suspension>
#2 FutureExtensions.onError.<anonymous closure> (dart:async/future.dart:1014:15)
<asynchronous suspension>

Username validation seems to be incorrect. I'm getting an error on adminDisableUser and adminDeleteUser with the username: 79fa9100-69d0-4fa0-aeef-68c6e7bf5d66

Invalid argument (username): Argument does not conform to [\p{L}\p{M}\p{S}\p{N}\p{P}]+: "79fa9100-69d0-4fa0-aeef-68c6e7bf5d66"

It seems that #144 requires a breaking change in the protocol library. I've a related change in the code generator that would update how the attribute's toJson() is called, and together with this PR they seem to generate the required format for SQS.

Hi! I did some tests here with aws_lambda_api: ^1.2.0 and the amplify_flutter: ^1.0.0-next.1+1 the future version of the amplify_flutter seems to be incompatible with the aws_lambda_api at the moment we do the login and use the session key via aws_lambda_api. When we try to use it with logged user seems to be invalid. Do you'll intend to make the lib compatible in the next release?

Presently there is no out-of-the-box way to use this package from a container instance to access S3 via an IAM role. I am no expert, but I believe this may be due to there not being a credential provider making use of the AWS_CONTAINER_CREDENTIALS_RELATIVE_URI environment variable.

(Edited to correct description.)

When sending a request using this signing scheme from ECS tasks on fargate, I get the following response:

<Error><Code>AccessDenied</Code><Message>There were headers present in the request which were not signed</Message><HeadersNotSigned>x-amz-security-token</HeadersNotSigned>

Moving the addition of the X-Amz-Security-Token header before the canonicalization of headers resolved this error for me.

final service = S3(
    region: getAWSRegion(),
    credentials: AwsClientCredentials(
      accessKey: getAWSAccessKey(),
      secretKey: getAWSSecretKey(),
    ),
);

await service.putObject(
    bucket: getAWSS3Bucket(),
    key: path,
    body: await file.readAsBytes(),
    contentType: 'application/octet-stream',
);

This adds all the credential providers available in aws_credential_providers as a default argument in the service constructors.

That means that services now, by default, can resolve assumed role credentials and from IMDS as well.