Question for you fine folks: I'm writing a .NET Core 3.1 console app (C#) with a custom DynamoDB property converter that implements Amazon.DynamoDBv2.DataModel.IPropertyConverter. It works as expected when I tag my POCO class using Amazon.DynamoDBv2.DataModel.DynamoDBPropertyAttribute:
namespace MyStuff
{
using System;
using System.Collections.Generic;
using Amazon.DynamoDBv2.DataModel;
public class Dashboard
{
[DynamoDBProperty(typeof(WidgetConverter))]
public List<Widget> Widgets { get; set; }
}
}Is it possible to wire up the custom DynamoDB property converter without tagging up my POCO class property using the DynamoDBProperty attribute? I've seen some code snippets that add mappings via the context, but I've been unable to get any of them to work.
Hey, hoping you can help - I've cloned the repo from master and am getting the following exception when running the tests:
The value of the property 'type' cannot be parsed. The error is: The type 'AWSSDK_DotNet.IntegrationTests.Tests.DynamoDB.DynamoDBTests+Employee, AWSSDK.IntegrationTestUtilities.Net35' cannot be resolved.Is there a Getting started guide I can refer to
1 reply
I'm calling AmazonLexClient.PostText. On my debug environment and on one server this works fine. On another server, every call to PostText is doubled. It makes two almost simultaneous requests. I'm not calling PostText twice because I've stuck logging all around it. I've confirmed that they are two full requests by checking with Fiddler, and I can see both going through. Lex throws a wobbly because it has two requests at the same time, and sends me a 409 conflict exception, which is the response that comes back to my code, even though one of the requests is actually succesful. Any ideas?
1 reply
Hey room, found a pretty big bug in the AWS SDK. The model generator is not correctly handling nullable types across all products. This could be creating transient errors or silent failures on your calls into the SDK across the entire platform. Just trying to get more visibility on it.
Hello - I'm using the CognitoIdentity SDK, I do not see where I can set the expiration of AWS Credentials.
I am using a two step process:
GetOpenIdTokenForDeveloperIdentity(),
GetCredentialsForIdentity()
I can only set the expiration on the OpenIdToken (1st method), but do not see where to set the expiration for the credentials method (2nd method)
Thank you in advanced for suggestions.
Any advice?
Thanks!
Adding onto the weird issues with S3...
I'm trying to get it working on android for Unity 2019.4 -- running into a NullReference in constructing InternalLog4NetLogger. I use log4net for another dependency, wondering if anyone has any tips. Here's the stack trace:
2020/11/19 08:59:48.166 8135 8160 Error Unity NullReferenceException: Object reference not set to an instance of an object.
2020/11/19 08:59:48.166 8135 8160 Error Unity at Amazon.Runtime.Internal.Util.InternalLog4netLogger..ctor (System.Type declaringType) [0x00000] in <00000000000000000000000000000000>:0
2020/11/19 08:59:48.166 8135 8160 Error Unity at Amazon.Runtime.Internal.Util.Logger..ctor (System.Type type) [0x00000] in <00000000000000000000000000000000>:0
2020/11/19 08:59:48.166 8135 8160 Error Unity at Amazon.Runtime.Internal.Util.Logger.GetLogger (System.Type type) [0x00000] in <00000000000000000000000000000000>:0
2020/11/19 08:59:48.166 8135 8160 Error Unity at Amazon.Util.Internal.AmazonHookedPlatformInfo..cctor () [0x00000] in <00000000000000000000000000000000>:0
2020/11/19 08:59:48.166 8135 8160 Error Unity at Amazon.UnityInitializer.Awake () [0x00000] in <00000000000000000000000000000000>:0
2020/11/19 08:59:48.166 8135 8160 Error Unity at UnityEngine.GameObject.AddComponent[T] () [0x00000] in <00000000000000000000000000000000>:0
2020/11/19 08:59:48.166 8135 8160 Error Unity at Amazon.UnityInitializer.AttachToGameObject (UnityEngine.GameObject gameObject) [0x00000] in <00000000000000000000000000000000>:0
1 reply
aws-lambda-tools-defaults.json is mostly used by the AWS Toolkit for Visual Studio tooling; it shouldn't be consumed by your application. defaults.json remembers the last place you deployed during development. appsettings.json is meant to be consumed by your code. So if you have a lambda function that writes to a SQS queue, your code needs to know which region to look for that queue. For testing, you may configure your local tooling to deploy to US-WEST-2, that would be saved to defaults.json, but your application needs to connect to a queue in US-EAST-1, so the appsettings.json would have us-east-1.
Hi Guys, Im having some issues with setting up a dotnet server that can verify jwt generated from aws cognito.
I am using this sample as my guide. https://aws.amazon.com/blogs/developer/introducing-the-asp-net-core-identity-provider-preview-for-amazon-cognito/
this is what I have done so far
- Create a new cognito User Pool
- Created two App Clients on the UserPool (Both clients are using Client Credentials OAuth Flow as I am after machine to machine auth)
- Used the App Client on the server that will be used to verify the JWT
- Using Postman, and hit the /oauth2/token endpoint using my app client. I Am using grant_type as client_credentials and passing in basic auth. (client id and client secret). I have successfully received an auth token
- Use that token in my auth header to my server. It is passed in as
bearer <token> - I get back a 401 Unauthorized on my protected resource.
I have tried to use both the app clients client id and secret to generate a JWT and both of them say unauthorized. Also I have not created any custom authorization policies. I am only after a authenticated resource at this point before I look at authorization
Hi. I'm getting this error attempting to execute dotnet test in a Docker build process - Unable to get IAM security credentials from EC2 Instance Metadata Service.
I'm running inside of Visual Studio and the docker-compose.override.yml contains:
services:
booking.service:
volumes:
- ${USERPROFILE}/.aws:/root/.aws
environment:
- ASPNETCORE_ENVIRONMENT=Development
- AWS_REGION=ap-southeast-2
- AWS_PROFILE=defaultThe credentials from my PC are being linked as a volume in the Docker container.
The Dockerfile command that is failing is:
RUN ASPNETCORE_ENVIRONMENT="IntegrationTesting" \
AUTOGURU_DATABASE_NAME_SUFFIX="${AUTOGURU_DATABASE_NAME_SUFFIX}" \
AUTOGURU_IS_DOCKER="true" \
AUTOGURU_IS_CI="${AUTOGURU_IS_CI}" \
dotnet test "../Tests/${SERVICE_NAME}.IntegrationTests/${SERVICE_NAME}.IntegrationTests.csproj" -c Release --no-restore -nowarn:CS1591The test is attempting to retrieve a parameter from the SSM Parameter Store using AmazonSimpleSystemsManagementClient which is being instantiated new AmazonSimpleSystemsManagementClient(RegionEndpoint.APSoutheast2).
If I skip the dotnet test step in the Dockerfile, when the containers start they seem to work correctly.
I created an IAM user with read only access to SSM and passed the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY into the dotnet test command and it worked. I want to avoid storing these values in code.
Any ideas?
Hello AWS .NET community! .NET SDK team is conducting a survey to learn about your recent experiences working with the AWS SDK for .NET and its learning resources. Please help us improve the SDK by taking a few minutes to answer the survey questions.
https://amazonmr.au1.qualtrics.com/jfe/form/SV_bqfQLfZ5nhFUiV0
rule(allow: .private, operations: [.read]),
rule(allow: .groups, groupClaim: "cognito:groups", groups: ["admin"], operations: [.read, .create, .update, .delete])
]
I'm using a current version of the .NET AWSSDK.DynamoDBv2 nuget.
I'm using preconditions on PutItem and UpdateItem requests.
Two questions:
- Given I expect and am ready to handle an anticipated conflict, is there any way to avoid the
ConditionalCheckFailedExceptionbeing thrown? - Given the data has already been retrieved in order to run the condition check, is there any way to obtain it when I know there is a conflict (I'd examine it and use it to deduplicate my request without incurring another roundtrip). Or is this a truly hard-baked service-side limitation (the docs dont say for sure its not possible but don't suggest this is catered for either)
AmazonSQSConfig amazonSQSConfig = new AmazonSQSConfig();
amazonSQSConfig.MaxConnectionsPerServer = 10;