text:
Support multi-tenant

Describe the feature you'd like to request
Amplify DataStore with Multi-tenancy
As a SaaS software company, we have customers whose data not only needs to be protected from each other, but also need finer access for different employees within the company.  Furthermore, our professional motorsports team customers need software that is local-first, so that their data may be manipulated, viewed, and analyzed by our software in a standalone fashion on their laptops (Electron) and mobile devices (and web), later to be backed up to the cloud and synced with other team engineers.  We work with SRO Motorsports, which AWS is a title sponsor.
At first glance, Amplify DataStore's selective sync with AppSync and DynamoDb seemed like a promising technology to implement local-first data with cloud sync, but we then realized in our discussion with AWS staff on Discord that multi-tenancy was not easily provided out of the box.
Describe the solution you'd like
Multi-tenant local-first data base that can sync with cloud, running on

Windows & Mac Desktops (Electron),
PWA,
Mobile

We'd like to see a complete front-to-back multi-tenant example, from a customer user's authentication in an Amplify app, to DataStore read/write, AppSync, to DynamoDb.
Describe alternatives you've considered
We've read about several including those mentioned here.  We are currently experimenting with Couchbase Lite and may also try Firebase.
Additional context
No response
Is this something that you'd be interested in working on?

[X] 👋 I may be able to implement this feature request

Would this feature include a breaking change?

[ ] ⚠ This feature might incur a breaking change

I support this request. Also looking for a multi-tenancy solution for users to sign in based on email domain so compant data remains separate only sharing the UI.

Hey @kenklin :wave: thanks for raising this! The multi-tenant request appears to be a duplicate of a few other issues around the topic:

https://github.com/aws-amplify/amplify-category-api/issues/449
https://github.com/aws-amplify/amplify-category-api/issues/281
https://github.com/aws-amplify/amplify-category-api/issues/949
https://github.com/aws-amplify/amplify-category-api/issues/452
https://github.com/aws-amplify/amplify-category-api/issues/335

I'm going to mark this as a documentation feature-request to look into adding an example like this!

authors: Rudgey84 josefaidt kenklin

repo: aws-amplify/amplify-category-api


text:
【gen2】Please support querying secondary indices with reqResBasedClient

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
18
Amplify CLI Version
@aws-amplify/backend: 1.0.3   @aws-amplify/backend-cli: 1.0.1
What operating system are you using?
mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
no
Describe the bug
I'm implementing ISR (Incremental Static Regeneration) functionality with gen2 and Next.js 14. I've attempted to achieve this using the following approach, which works for fetching data by ID:
import React from 'react';
import { reqResBasedClient, runWithAmplifyServerContext } from "@/app/isr/[id]/_lib/amplifyServerUtils";
import { unstable_cache } from "next/cache";

const getCacheData = unstable_cache((id: string) => {
    return runWithAmplifyServerContext({
        nextServerContext: null,
        operation: async (contextSpec) => {
          const res = await reqResBasedClient.models.Todo.get(contextSpec, { id });
          return res.data;
        },
    }),
    ['todo'],
    { revalidate: 30, tags: ['todo-list'] }
});

type PageProps = {
    params: { id: string };
};

const Page = async ({ params }: PageProps) => {
    const data = await getCacheData(params.id);
    return (

            content: {data?.content}

    );
};

export default Page;

Since unstable_cache doesn't support cookies, I'm using reqResBasedClient to handle the server-side operations.
However, this approach doesn't work for secondary indexes. I would like to achieve something similar to fetching data by a secondary index, like this:
const getCacheData = unstable_cache((type: string) => {
    return runWithAmplifyServerContext({
        nextServerContext: null,
        operation: async (contextSpec) => {
            const res = await reqResBasedClient.models.Todo.listByType(contextSpec, { type: 'TODO' });
            return res.data;
        },
    }),
    ['todo'],
    { revalidate: 30, tags: ['todo-list'] }
});

Expected behavior
Secondary index support with contextSpec
Reproduction steps
https://github.com/sevenkkk/amplify-next-isr/blob/main/app/isr/[id]/page.tsx
Project Identifier
No response
Log output

# Put your logs below this line

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hi @sevenkkk 👋 thanks for raising this issue. Can you explain a little bit more about why "this approach doesn't work for secondary indexes"?
Are you seeing any error messages or getting unexpected results?

Revisited this and realized that the issue is actually that the listByType query doesn't accept a contextSpec so I tried that got the error:

I'll mark this as a bug for the team to investigate further

@chrisbonifacio I hope you can help me deal with this problem first. Please

In the meantime, I would recommend using the client.graphql API instead to perform the query

Here's an example of what a refactor would look like:
import React from "react";
import {
  reqResBasedClient,
  runWithAmplifyServerContext,
} from "@/app/isr/[id]/_lib/amplifyServerUtils";
import { unstable_cache } from "next/cache";
import { listByType } from "@/queries";

const getCacheData = unstable_cache(
  (type: string) => {
    return runWithAmplifyServerContext({
      nextServerContext: null,
      operation: async (contextSpec) => {
        const res = await reqResBasedClient.graphql(contextSpec, {
          query: listByType,
          variables: {
            type,
          },
        });
        return res.data;
      },
    });
  },
  ["todo"],
  { revalidate: 30, tags: ["todo-list"] }
);

type PageProps = {
  params: { type: string };
};

const Page = async ({ params }: PageProps) => {
  const { listByType: data } = await getCacheData(params.type);
  return
content:{data?.items[0].content}
;
};

export default Page;

You can generate the listByType query using the following command:
npx ampx generate graphql-client-code

Hey @sevenkkk, we just released a bug fix for this issue. Please run the following to update the dependency in your project:
npm update @aws-amplify/data-schema

source: gharchive/issue

authors: chrisbonifacio iartemiev sevenkkk

license_type: permissive

license_source: github-api


text:
chore: merge cdkv2 to main

Description of changes
This PR merges cdkv2 branch to main

CDK / CloudFormation Parameters Changed

Issue #, if available

Description of how you validated changes
Checklist

[x] PR description included
[x] yarn test passes
[x] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
[ ] Any CDK or CloudFormation parameter changes are called out explicitly

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

2 questions I dropped inline, and the last is why the graphql-predictions-transformer packages wouldn't have had a version bump but graphql-relational-schema-transformer would have? The changes in this PR looks similar, but maybe it's related to manual changes you merged in from main

Confirmed offline it’s because 2.21.16-beta.1 is greater than 2.21.15 , but 3.2.48 from main was greater than 3.2.48-beta.X from cdk branch. I.e. when I resolve version conflicts I pick version that’s higher per semver spec.
So that regardless if we ship beta/tag/GA afterwards lerna picks next correct increment.
(not doing this led to version conflicts at release steps when we shipped tags/betas).
from GA release perspective it doesn’t matter, but if we were to cut beta tag it would. so just being precise here.

Because these were reviewed iteratively on-branch, approving this after reviewing the package.json files and discussing w/ Kamil. Approach seems reasonable, and we have verification mechanisms after the CLI merges and an RC is cut.

source: gharchive/pull-request

authors: alharris-at sobolk


text:
In nextjs 13, While pulling existing amplify backend, graphql folder is not added in src folder.

Amplify CLI Version
12.6.0
Question
In nextjs 13, While pulling existing amplify backend, graphql folder is not added in src folder. How to resolve this.

Hey @RZ-Jyothsna, thank you for reaching out. We can generate the graphql folder by running amplify configure codegen and run the through the flow. If the project already has the .graphqlconfig.yml present, we can run amplify codegen to generate the folder.

closing the issue due to inactivity. please feel free in reaching out to us, we would be happy in diving deeper.

authors: RZ-Jyothsna ykethan

repo: aws-amplify/amplify-cli


text:
I have delete a api, now i want to undo the operation.

** Which Category is your question related to? **
amplify add and remove api
** What AWS Services are you utilizing? **
AWS APPSYNC amplify api remove
** Provide additional details e.g. code snippets **
1: I have added an api
2. i made the changes to the api but havent pushed the changes
3. i didnt like the stuff i did in there and so i deleted it.
3. its as shown in the image.
4 now i want to undo the operation which says remove.
how do i do that.
P.S i havent done amplify push yet.

@hafizali05
Just want to get exactly what happened. You've created and pushed your api before, and the api related resources have already been created in the cloud, right?
Then you made local changes without pushing them to the cloud, but you don't want to keep those local changes.

I did amplify pull --restore and it was back to what I wanted.

I had a similar challenged but I resolved it by copying and replacing my #current_cloud_backend folder with the backend folder. In my case, the locally served app was faultless so check again before you follow this approach.

authors: JoeLamptey UnleashedMind hafizali05


text:
Cannot update to amplify 5.0.0

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v15.1.0
Amplify CLI Version
4.51.3
What operating system are you using?
macOS 10.15.7
Amplify Categories
Not applicable
Amplify Commands
Not applicable
Describe the bug
When trying to update to 5.0.0 using any of these commands:
npm install -g @aws-amplify/cli
OR
sudo npm install -g @aws-amplify/cli --unsafe-perm=true
I receive this error:
6089 verbose stack Error: ENOENT: no such file or directory, chmod '/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/aws-cdk/bin/cdk'

Expected behavior
Installation goes OK.
Reproduction steps
Just try to update from 4.51.3 to 5.0.0 using my computer or my configuration.
GraphQL schema(s)
NA
Log output
NA
Additional information
No response

Hey @Ricardo1980 thanks for raising this! Can you try clearing npm cache with npm cache clean and re-attempt the upgrade?

I'm facing the same issue. Have tried 'npm -g cache clean --force' and then installing again but didn't work.

I was able to reproduce this issue with Node v15.7 and npm v7.4.3, and was able to resolve it by upgrading npm with npm i -g npm to update to v7.18.1 and re-attempt upgrade of Amplify CLI.
Can you try upgrading npm to the latest version and re-attempt the upgrade?

After removing manually node and npm, and then installing again with brew, it worked.


text:
Domain activation is Failed - existing wildcard Cloudfront conflict?

App Id: d3203l8rg5g22r
Region: eu-west-2
Step: Domain activation
Status: Failed
Issue/question
Should I be able to set up custom domain if I have an existing Cloudfront distro bound to wildcard domain?
I already have multiple cloudfront distros where one is bound to wildcard domain and others to specific sub-domains.  Eg.

Cloudfront distribution #1 - *.foo.com
Cloudfront distribution #2 - admin.foo.com

The above works directly from Cloudfront.
What I'm trying to do now is set up Amplify Console App on a custom domain - www.foo.com.
Error message
One or more of the CNAMEs you provided are already associated with a different resource.
Additional information
What I've tried

Removing everything (I'm aware of) from all AWS accounts which could be bound to www.foo.com
Waiting 12+ hours after removal and trying again
Without apex/root domain - eg. foo.com

Cheers

@jaymcguinness Sorry. You can't do this. CloudFront will not allow you to attach wild card in one distribution and subdomain in another distribution.

Really? Cos I have exactly that working already.

@jaymcguinness https://stackoverflow.com/questions/54115340/cnamealreadyexists-when-setting-a-wildcard-cname-in-a-cloudfront-distribution.
Can you add your www.foo.com to amplify app right now?

Sadly not - so to recap.
I can manually setup 2 distributions - one wildcard, one subdomain and it works.
I removed the manually created www.foo.com distribution, waited 12 hours and tried to create www.foo.com via Amplify app, but it fails with above error.

@jaymcguinness . Looks like your www. domain is still attached to a cloudFront distribution.
It's in account 087xxxx22640 with distribution ID: d3glvhegruywac.
That should be the root cause

HI @garyleefight
Lol - no, that's me just creating it again (just now) manually to check I wasn't going mad!

Feel free to close - and I'll re-create the problem and open a new issue if that's easier.

Closing this issue, please feel free to re-open if you are still facing issues.

authors: Athena96 garyleefight jaymcguinness

repo: aws-amplify/amplify-console


text:
Isolate connection pool used by AWS

Use a named connection pool on built-in hackney implementation, so all requests made by this library will be isolated.
As this library doesn't define any application or supervision tree, the connection pool will be initiated lazily by hackney itself on the first call. It can be still be overwritten, so users could create pools per AWS service or more complicated needs.

@andrewhr awesome, thank you! :purple_heart:

authors: andrewhr philss

repo: aws-beam/aws-elixir


text:
cfn-lint cannot check condition when checking resource type is supported or not

CloudFormation Lint Version
0.76.1
What operating system are you using?
docker
Describe the bug
I am using cfn-lint to check my cloudformation template. I have following logic:
Check if the region is not cn-north-1 or cn-northwest-1,  it will create AWS::GlobalAccelerator::Accelerator resource, otherwise, it will not create AWS::GlobalAccelerator::Accelerator resource.
But now I got following error when we are running cfn-lint to check my cloudformation template:
E3001 Invalid or unsupported Type AWS::GlobalAccelerator::Accelerator for resource Accelerator in cn-northwest-1
cdk.out/xxx.template.json:1416:4
I guess this is a bug, could you please help to fix this error?
Thanks,
Mingtong
Expected behavior
I expect my template can be validated successfully.
Reproduction template
Conditions:
acceleratorEnableCondition:
Fn::Not:
- Fn::Or:
- Fn::Equals:
- Ref: AWS::Region
- cn-north-1
- Fn::Equals:
- Ref: AWS::Region
- cn-northwest-1
MyAccelerator:
Type: AWS::GlobalAccelerator::Accelerator
Properties:
Name: myAccelerator
Enabled: true
Condition: acceleratorEnableCondition

Your problem seem to be checking AWS::GlobalAccelerator::Accelerator against a cn- region that doesn't support it. You can override this by validating the template against a region with most features going GA, e.g. us-east-1 or ap-northeast-1, instead of your own AWS region.
cfn-lint -r REGION ANOTHER_REGION .... -t template.yml

My opinion to cfn-lint is designed as a static type checker against specifications, which may not handle dynamic values as robustly as static values.
In your case requires evaluating the condition with AWS::Region = cn-north-1 to know AcceleratorEnableCondition = False to skip the accelerator block, which cannot generally be done.
Consider this, there is no general solution to know if IsProduction is true / false without further context.
Condition:
  IsProduction: !Equals
    - NodeEnv
    - "production"
Parameter:
  NodeEnv:
    Type: String
Resource:
  Accel:
    Condition: IsProduction
    Type: AWS::GlobalAccelerator::Accelerator

We have methodologies to solve some of this as we use logic to compare condition scenarios to evaluate the results of the template.  (SAT solvers using sympy).  That logic needs to be expanded to this scenario. This is a pretty specific scenario in which the resources Condition is based on a condition that does and Equals against !Ref AWS::Region. We should actually be able to use the --regions parameter to determine if the resource is available in a certain region.

authors: dengmingtong kddejong kftsehk

repo: aws-cloudformation/cfn-lint


text:
New Fargate Rules

cfn-lint version: (cfn-lint --version): 0.32.1
Description of issue. New Rule Suggestions for ECS Fargate
Having just tried to deploy a new task alongside some existing tasks in Fargate, I ran across quite a few deployment failures that cfn-lint didn't warn me against, so this issue is simply a proposal for new rules to cover these cases.

[ ] [Error] When an AWS::ECS::Service has its LaunchType set to FARGATE, it cannot have SchedulingStrategy set to DAEMON. Currently the only supported SchedulingStrategy is REPLICA. Reference: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html#service_scheduler.
[ ] [Error] When an AWS::ECS::TaskDefinition has its NetworkMode set to awsvpc, then any AWS::ECS::TaskDefinition ContainerDefinition subresources should either not specify any HostPort within each PortMappings entry, or should set it to equal the corresponding ContainerPort. Reference: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-taskdefinition-containerdefinitions.html#cfn-ecs-taskdefinition-containerdefinition-portmappings.
[ ] [Error] When an AWS::ECS::TaskDefinition has its NetworkMode set to awsvpc, its parent AWS::ECS::Service resource must specify a NetworkConfiguration (which should be of type AWS::ECS::Service AwsVpcConfiguration. Reference: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html#cfn-ecs-service-networkconfiguration.
[x] [Error] Every AWS::ECS::TaskDefinition must contain at least one AWS::ECS::TaskDefinition ContainerDefinition that has Essential set to true. Reference: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-taskdefinition-containerdefinitions.html#cfn-ecs-taskdefinition-containerdefinition-essential. https://github.com/aws-cloudformation/cfn-python-lint/pull/1548

Adding another suggestion to fargate rules:
[ ] Error When AWS::ECS::Service has LauchType set to FARGATE, but the TaskDefinition it references does not specify "RequiresCapabilities": ["FARGATE"]

repo: aws-cloudformation/cfn-python-lint


text:
pin code-gen to ACK runtime 0.6.0

Issue N/A
Description of changes:

Adds a test case for pinning code-generator to the ACK runtime v0.6.0.
Bump ack-generate version to v0.6.0

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/lgtm

authors: A-Hilaly jaypipes


text:
BUG: Submitter only creates a single task for all shots. It should make 1 task per shot in the MRQ

Expected Behaviour
For each shot in the MRQ, a single task should be created, allowing parallel rendering.
(In an ideal world, we would also offer sub shot chunking as well, but this is trickier with stochastic problems).
I could no see a way around this?
Current Behaviour
For the MRQ, only a single task is made.
It should make a task per shot ( as in Deadline 10's behaviour)
Reproduction Steps
Create a multi shot setup in the MRQ ( Meerkat scene is great).
Submit the job - you only get a single task.
Code Snippet
NA

This feature is crucial for us, as we handle large renders that require fast turnaround times.  Without it, the advantage of rendering with AWS dissolves.  Will buy beer for the first person who pushes out a fix.  :)

Hello @andymanaws! Thank you for your contribution. This is a great enhancement suggestion. We have added this to our backlog and will look into prioritizing it accordingly.
We will reach out here with any updates or questions.

authors: andymanaws jusiskin steve-fong


text:
An error occurred while executing the state 'run_create_pipeline?' (entered at the event id #33). Invalid path '$.Input.account_provisioning.run_create_pipeline': The choice state's condition path references an invalid value."

Terraform Version & Prov:
AFT Version:
1.9.1
Terraform Version & Provider Versions
Please provide the outputs of terraform version and terraform providers from within your AFT environment
terraform version
0.15.5

terraform providers
AWS

Bug Description
We have deployed control tower and AFT for terraform in a separate AFT account using Terraform, aft version 1.9.1. After deploying aft new account request is working fine,  it is running pipeline for creating the account whenever we add new account request terraform code in our AFT account request repository.
But account customisation is not working and even we can't see the state machine for account-provisioning-customization as well as no pipeline for any of the account created for account customisation.
When we try to run the aft-invoke-customization step function then we are getting below error.
Note: The logs mentions about account creation but the account is already existing and we are making customisation through account-customization.
{
"Cause": "An error occurred while executing the state 'run_create_pipeline?' (entered at the event id #33). Invalid path '$.Input.account_provisioning.run_create_pipeline': The choice state's condition path references an invalid value.",
"Error": "States.Runtime",
"ExecutionArn": "arn:aws:states:us-east-2::execution:aft-account-provisioning-framework:e5c48973-f6fa-4def-beaf-55ca11e33ba2",
"Input": "{"account_info":{"account":{"id":"","email":"shared_acct@email","name":"shared-account",
"joined_method":"CREATED","joined_date":"2023-03-09 07:51:44.747000+00:00","status":"ACTIVE","parent_id":"ou-38lh-9att8jja","parent_type":"ORGANIZATIONAL_UNIT",
"type":"account","vendor":"aws"}},"control_tower_event":{},"account_request":{"custom_fields":"{\"group\":\"prod\"}","change_management_parameters":
{"change_reason":"Create new ControlPlane account shared-account","change_requested_by":"shared_acct@email.com"},"id":"shared_acct@email.com","control_tower_parameters":
{"AccountEmail":"sharedservices-account@email","SSOUserFirstName":"-sharedservices-account","SSOUserLastName":"sharedservices-account"
,"ManagedOrganizationalUnit":"controlplane-ou","AccountName":"shared-account","SSOUserEmail":"shared_acct@email.com@email"},"account_tags":
{"Environment":"prod","Owner":"sharedservices-account sharedservices-account","Project":"xyz","Vended":"true","created_by":"
sharedservices-account@email"},"account_customizations_name":"shared-customizations"},"account_provisioning":{"run_create_pipeline":"true"},
"customization_request_id":"c0bb8f9a-9f82-4c30-a62c-96119a391b53"}",
"InputDetails": {
"Included": true
},
"Name": "e5c48973-f6fa-4def-beaf-55ca11e33ba2",
"StartDate": 1679307003825,
"StateMachineArn": "arn:aws:states:us-east-2::stateMachine:aft-account-provisioning-framework",
"Status": "FAILED",
"StopDate": 1679307036829
}
To Reproduce
Steps to reproduce the behavior:

Add terraform code in account-customization repository under account_customization_name valued folder
Run the Step function with below input
{
"include": [
{
"type": "accounts",
"target_value": [
""
]
}
]
}

Expected behavior
It should deploy resources mentioned in the Terraform in the target account.
Related Logs
Please let us know if the AFT deployment logs are required or any other logs from the cloud watch I can provide.
Additional context
Add any other context about the problem here.

@vneekhra , a missing state machine could mean that the AFT deployment was not successful.
Could you confirm that AFT was deployed successfully and no errors were encountered?

got the same issue, my AFT deployment was successful without any error.

@snebhu3 teh AFT deploymnet was successful and it has deployed around 325 resources ... no errors were reported in aft deployment. And for depoying AFT we have used the latest terraform version 1.4.2 (so it is indeed higher then 0.15.x).
And even now if I try redeploying aft it reports no changes .... belwo is the snippt of the aft deployment:
_```
_module.aft.module.aft_customizations.aws_iam_role_policy.aft_invoke_customizations_sfn: Refreshing state... [id=aft-invoke-customizations-execution-role:aft-invoke-customizations-policy]
module.aft.module.aft_customizations.aws_iam_role_policy.aft_identify_targets_lambda: Refreshing state... [id=aft-identify-targets-execution-role:aft-identify-targets-policy]
module.aft.module.aft_customizations.aws_sfn_state_machine.aft_invoke_customizations_sfn: Refreshing state... [id=arn:aws:states:us-east-2:<12-digit-aft-account-id>:stateMachine:aft-invoke-customizations]
No changes. Your infrastructure matches the configuration.
Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.
Releasing state lock. This may take a few moments...
Apply complete! Resources: 0 added, 0 changed, 0 destroyed.
Outputs:
aft_management_account_id = "<12-digit-aft-account-id>"
audit_account_id = "<12-digit-audit-account-id>"
ct_management_account_id = "<12-digit-ct-account-id>"
log_archive_account_id = "<12-digit-logarchive-account-id>"
region = "us-east-2"

[[ -f terraform.tfstate ]]_

@rupadhy3 I got it working by adding following files here in the repo aft-account-provisioning-customizations which will create the missing state.

@ahmedfourti
Thanks for info, the issue is resolved.
Though these files were already there in our aft-account-provisioning-customizations repository, but somereason they were not picked up during AFT deployment.
So we just had to make a dummy commit into the repository and that triggered aft to deploy the state machine from our aft-account-provisioning-customizations.
Though the current issue is resolved but the I still see a bug ... that AFT during deployment should take the repository content and deploy it, it should not explicitly wait for another commit into the repository to deploy the state machine, if the files are already present.
Regards

@rupadhy3 thank you for your response. This should not be the case ideally.
For understanding the root cause, a deeper troubleshooting will be required in the CT environment.
Please reach out to AWS Premium Support for assistance on understanding the root cause.
Closing the ticket since the issue has been resolved.

For me, after I created/updated the account-provisioning-customizations repository in GitHub, the final missing step was to update my codestar-connections app to include this new repository.


text:
Updated role_arn to fix deprecation warning

Understanding that no PRs are being taken - submitting this as a feature request to fix deprecation warning in pipelines.
Error is as follows:
Warning: Deprecated Parameters

The following parameters have been deprecated. Replace them as follows:
     * role_arn -> assume_role.role_arn

Default response
# Contributing to the AWS Control Tower Account Factory for Terraform

Thank you for your interest in contributing to the AWS Control Tower Account Factory for Terraform.

At this time, we are not accepting contributions. If contributions are accepted in the future, the AWS Control Tower Account Factory for Terraform is released under the [Apache license](http://aws.amazon.com/apache2.0/) and any code submitted will be released under that license.

If you have a feature request, please create an issue using the Feature Request template, thanks!

Thanks for the pull request! As you already noted, we’re not accepting contributions at this time, but we’ll add this to our feature request backlog

authors: hunttom sk-at-amazon


text:
docs: update documentation for aspectJ

Issue #, if available: #1271
Description of changes:
Added installation steps in core modules and described the aspectJ configuration for both Java 1.8 and 11+. Together with @scottgerring, we thought it would be better to use the old plugin (org.codehaus.mojo groupId) for Java 1.8 and the new one (dev.aspectj groupId) for Java 11+, instead of adding additional configuration and complexity (enforcing aspectj-rt 1.9.7)
Checklist

[x] Meet tenets criteria
[ ] Update tests
[x] Update docs
[x] PR title follows conventional commit semantics

Breaking change checklist

RFC issue #:

[ ] Migration process documented
[ ] Implement warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

We should also update the sam templates... https://github.com/aws/aws-sam-cli-app-templates/

repo: aws-powertools/powertools-lambda-java


text:
Bug: Pydantic "escape hatch" no longer available

Expected Behaviour
The Parser documentation FAQ states that an "escape hatch" mechanism can be used to access imports from the base pydantic library that are not otherwise available as imports from aws_lambda_powertools.utilities.parser: https://docs.powertools.aws.dev/lambda/python/latest/utilities/parser/#faq.
Current Behaviour
aws_lambda_powertools.utilities.parser.pydantic is not a valid import path. (This may have been an older feature that has since been removed.)
Code snippet
from aws_lambda_powertools.utilities.parser.pydantic import <what you'd like to import'>
Possible Solution
If all pydantic imports can be made available at aws_lambda_powertools.utilities.parser.pydantic (likely by modifying aws_lambda_powertools/utilities/parser/__init__.py), that would be ideal. Otherwise, the documentation should be updated to remove this feature.
Steps to Reproduce
Attempting to import anything from aws_lambda_powertools.utilities.parser.pydantic will result in an import error.
Powertools for AWS Lambda (Python) version
latest
AWS Lambda function runtime
3.12
Packaging format used
Lambda Layers
Debugging logs
No response

For reference, I was trying to import computed_field, but
from aws_lambda_powertools.utilities.parser import computed_field

is not a valid import.

Hey @areifert thanks a lot for opening this issue! In fact we are not exporting Pydantic objects from parser and we explain that in our upgrade guide to v3.
In Powertools v3 we have dropped support for Pydantic v1 and are only supporting Pydantic v2 which is why we are no longer exporting pydantic types directly and allowing customers to import them directly from Pydantic. First, I must say that I agree with that we need to update our documentation and we are already doing this. I'll try to merge this PR as soon as possible to prevent this type of error.
Let me explain some reasons why we removed this export:
1 - Pydantic V2 was a complete refactoring of the Pydantic project and they made several changes including, but not limited, to the way they export types, classes, methods, and others. If we continue to expose them directly from Powertools and some export in Pydantic has changed, our customers may get the impression that there is some bug in Powertools and that is not the experience we want to have for our customers.
2 - The way we were doing this was by exposing everything exposed from pydantic to our customers, but there is a long discussion in the Pydantic repository about how https://github.com/pydantic/pydantic/discussions/6748 when importing and loading things in this new version. We don't want our customers to inadvertently import everything from Pydantic and this could create some slowdown in their functions.
Can you please try importing them directly from Pydantic?

@leandrodamascena: this is perfect, thanks for the detailed response. I was able to import computed_field directly from Pydantic.
It looks like some Pydantic exports are still available from aws_lambda_powertools.utilities.parser (e.g., BaseModel); going forward, is it recommended that all of these be imported directly from Pydantic instead?
(P.S.: I've been using Powertools for only a month or two and am really enjoying it, thanks for all you do!)

It looks like some Pydantic exports are still available from aws_lambda_powertools.utilities.parser (e.g., BaseModel); going forward, is it recommended that all of these be imported directly from Pydantic instead?

This is expected because now we just export BaseModel, Field, ValidationError, field_validator, and model_validator, the functions/classes that we must use in our utilities, including parser. The old way we were exporting  * from pydantic and errors.

(P.S.: I've been using Powertools for only a month or two and am really enjoying it, thanks for all you do!)

Hey, that's awesome to hear! We're here to support you in any way you need. Feel free to open an issue or talk to us on our Discord server https://discord.gg/B8zZKbbyET
Closing this issue.

authors: areifert leandrodamascena

repo: aws-powertools/powertools-lambda-python


text:
Pr/9 updated

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Merging first version of the NL translation


text:
Python Issue

At present attempting to run the code however this error is being returned. Tired with older versions of the CDK however same error is returned
Software
npm 8.3.1
Python 3.10.2
CDK 2.12.0 (build c9786db)
aws-cli/2.4.3 Python/3.8.8 Windows/10 exe/AMD64 prompt/off
cdk bootstrap aws://OPPS/eu-west-2
Traceback (most recent call last):
  File "C:\Users\USER\Documents\Git\aws-cdk-tfsec\app.py", line 5, in <module>
    from aws_cdk import core
  File "C:\Users\USER\AppData\Local\Programs\Python\Python310\lib\site-packages\aws_cdk\core\__init__.py", line 4925, in <module>
    class ConstructNode(metaclass=jsii.JSIIMeta, jsii_type="@aws-cdk/core.ConstructNode"):
  File "C:\Users\USER\AppData\Local\Programs\Python\Python310\lib\site-packages\aws_cdk\core\__init__.py", line 4963, in ConstructNode
    runtime_info: typing.Optional[aws_cdk.cx_api.RuntimeInfo] = None,
AttributeError: module 'aws_cdk.cx_api' has no attribute 'RuntimeInfo'

Hi @steveyminecraft
Thanks for reporting this issue. I want to ask you if you could test two things:

Downgrade the CDK version to 1.103.0 (It's not mentioned in the README but the dependencies are set for this particular version)
Could you try with Python 3.7 ?  I have tested also with Python 3.9, 3.10 and 3.12 and getting a different issue with the core package of CDK.

Please let me know your tests.

Hi @steveyminecraft ,
Did you have any chance to review my suggestions?
Regards

Closing due to inactivity

authors: cesarpball steveyminecraft

repo: aws-samples/aws-cdk-tfsec


text:
Self Hosted - Cloudformation - [Makefile:27: deploy-cloudwan-active] Error 255

Fails with error when using make deploy.
From Stackset status
The following resource(s) failed to update: [CoreNetwork].
1 validation error detected: Value 'Incorrect policy. (Service: NetworkManager, Status Code: 400, Request ID: a7b53b81-3ffe-4888-b02a-e132513ef8a3): [{ErrorCode: MAXIMUM_ITEMS_EXCEEDED, Message: $.segment-actions[1].destinations: blackhole may only exist in a singleton list}, {ErrorCode: INVALID_STRING, Message: $.segment-actions[1].destinations[0]: attachment identifiers must be prefixed with "attachment-" and must end in 17 characters where all characters are from the set "a..f" or "0..9"}, {ErrorCode: CONSTANT_VIOLATION, Message: $.segment-actions[1].destinations[0]: must be a constant value blackhole}, {ErrorCode: INVALID_STRING, Message: $.segment-actions[1].destinations[1]: attachment identifiers must be prefixed with "attachment-" and must end in 17 characters where all characters are from the set "a..f" or "0..9"}, {ErrorCode: CONSTANT_VIOLATION, Message: $.segment-actions[1].destinations[1]: must be a constant value blackhole}, {ErrorCode: REQUIRED_PROPERTY, Message: $.segment-actions[1].mode: is missing but it is required}, {ErrorCode: REQUIRED_PROPERTY, Message: $.segment-actions[1].share-with: is missing but it is required}, {ErrorCode: MAXIMUM_ITEMS_EXCEEDED, Message: $.segment-actions[2].destinations: blackhole may only exist in a singleton list}, {ErrorCode: INVALID_STRING, Message: $.segment-actions[2].destinations[0]: attachment identifiers must be prefixed with "attachment-" and must end in 17 characters where all characters are from the set "a..f" or "0..9"}, {ErrorCode: CONSTANT_VIOLATION, Message: $.segment-actions[2].destinations[0]: must be a constant value blackhole}, {ErrorCode: INVALID_STRING, Message: $.segment-actions[2].destinations[1]: attachment identifiers must be prefixed with "attachment-" and must end in 17 characters where all characters are from the set "a..f" or "0..9"}, {ErrorCode: CONSTANT_VIOLATION, Message: $.segment-actions[2].destinations[1]: must be a constant value blackhole}, {ErrorCode: REQUIRED_PROPERTY, Message: $.segment-actions[2].mode: is missing but it is required}, {ErrorCode: REQUIRED_PROPERTY, Message: $.segment-actions[2].share-with: is missing but it is required}]' at 'statusMessage' failed to satisfy constraint: Member must have length less than or equal to 1024

Updated the CloudFormation code with the udpate of the Cloud WAN Workshop (added TGW - CloudWAN peering, plus minor changes in the original code). Tested with new version and everything should be fixed now.
Check the README, as now we implemented a new way to deploy the resources.

repo: aws-samples/aws-cloudwan-workshop-code


text:
Release docker image for arm64

The following file has been created and modified :
Added .travis.yml file to build and push the image for both amd64 and arm64 platforms.
Signed-off-by: odidev odidev@puresoftware.com

Can you please review this PR and let me know if any changes are required?

repo: aws-samples/ecs-demo-php-simple-app


text:
Impacts of AWS Lambda end of support for Node.js 16

I recently recieved an email titled "AWS Lambda end of support for Node.js 16" mentioning that I have two impacted functions from my step-by-step deployment of this repository. Specifically they are ImgTransformationStack-imageoptimization and ImgTransformationStack-LogRetention when I look at them on the Health Dashboard.
Do you have a recommended plan of action for upgrading these to ensure support is maintained and the code continues to function as expected? Thanks!

Hello, in the latest version of the code, we upgraded NodeJs versions. So the question is how to upgrade to the latest code version, with minimal impact on production?
I can think of the following approaches, but I haven't tested any of them yet to give you an authoritative recommendation:

Update the CDK code with the latest version and deploy again to evolve existing resources. To validate it before deploying to production, you can deploy the old code in a different account, then update with the new code, and verify if there was no issues.
Deploy the new code with new resources, then copy generated images to the new S3 bucket, then shift traffic to the new CloudFront distribution, by moving the CNAME from the old one to the new one. However with this approach, CloudFront cache will need to be populated again. Also note that you'd need to verify beforehand if you can deploy the same stack twice in a single AWS Account, because we did not test this scenario.

I can add some info about your second point. I tried to to change the stack name, and then ran cdk deploy..
CDK detected it needed a new deploy, but the deploy failed with:
Invalid request provided: AWS::CloudFront::ResponseHeadersPolicy: Another response headers policy with the same name already exists within the aws account.
It seems to be because the policy name needs to be unique, and it is always set to responseHeadersPolicyName: 'ImageResponsePolicy',

@JanC89 did a quick fix to make it work https://github.com/aws-samples/image-optimization/commit/6b4d7dd1872e0ae682e8e1de1634b1c270b5e2b5

@achrafsouk thanks for the input! I believe I'll take your second recommended approach. I am not well versed in AWS, so don't want to accidentally burn myself. Do you mind if I ask a few questions?

A "Deploy the new code with new resources" is effectively just following the guide again, correct? Should work with no issues now that you made this change https://github.com/aws-samples/image-optimization/commit/6b4d7dd1872e0ae682e8e1de1634b1c270b5e2b5
Do you have guidance on how to properly copy generated images to the new S3?
Any guidance on how to make DNS/CNAME changes?
With the CloudFront cache needing to be repopulated, this will simply cause minor delays on the users end, no loss of images, correct?

Thank you so much, I really appreciate it!

Yes, but I highly recommend you to try this operation first on a non production environment
Use the AWS CLI, with the S3 sync command to copy all images from the old generated image bucket to the new one
Since both distributions are in the same AWS Account, follow steps described in Use the AssociateAlias API to move your CNAME. Don't forget at the end to change the DNS record of your domain to point to the new distribution
It will cause cache misses, so additional delays for your users for a couple of hours. It's best to do it in low traffic time.

Thanks so much! In the original guide, I used the option cdk deploy -c S3_IMAGE_BUCKET_NAME=’YOUR_S3_BUCKET_NAME’
Is it a valid option to have the new deploy link to the same bucket & skip the step on moving images?

the new deploy has to point to the same bucket holding the original images. Its the bucket from which the Lambda will fetch images for processing. The bucket I was talking about was the bucket created by the solution that holds the generated images. Copying images from this bucket is optional, but highly recommended to avoid having your Lambda to generate all image variants again.

Got it, thanks. When I ran the cdk deploy command, I received the same ImgTransformationStack.ImageDeliveryDomain that I previously had. When I look at my distributions I only see 1. I also am not able to query the ListConflictingAliases endpoint after trying several method. Additionally my current distribution is not functioning correctly even though it looks like the Lambda functions are updated 😅
Sorry for all the issues, but I expected for this to deploy a new Distribution linked to the some source S3 bucket. Did I do something wrong?

Ah! because you have used the same application name in the cdk project. It means that you have in reality followed the first option for migration, which is upgrading the existing stack, and i am glad it worked without any challenges.

I modified several things, changed the code to add the quality option and also put two distributions together in the same cloudfront, with an alias, one for transforming images and the other for CDN.
These changes... will they reset?

Reset following what?

authors: Hipocrita JanC89 achrafsouk larrettgee

repo: aws-samples/image-optimization


text:
v0.4.0: CDK 移行

Motivation
#47
Proposed Changes

CDK への移行

バックエンドの CDK への移行
フロントエンド連携部分の修正
ドキュメントの更新
v0.3.0 からの移行ガイドの作成
lint の導入
GitHub Action による lint, build テスト

google workspace, entraIDでもログインが可能なことを検証しました。
PRありがとうございます！とてもよくなりました！！
マージしましょう！

authors: maekawataiki ysekiy

repo: aws-samples/jp-rag-sample


text:
The runtime parameter of python3.7 is no longer supported

Hello,
I am trying to use the project for Forwarding TCP ports over SSH tunnel.
I am trying to deploy the section IAM SSM Setup
While running the command:
cdk -a "$APP" deploy SSH-IAM-SSM-Stack \
  -c sagemaker_role="$SAGEMAKER_ROLE_ARN" \
  -c user_role="$USER_ROLE_ARN"

I am getting the following error L:
6:02:16 PM | CREATE_FAILED        | AWS::Lambda::Function   | TrustRelationshipLambdaTrigger562CEAC4
Resource handler returned message: "The runtime parameter of python3.7 is no longer supported for creating or updating AWS Lambda functions. We recommend you use
the new runtime (python3.12) while creating or updating functions.

Is there a workaround to avoid this issue ?
Regards
Clement

Hi, @clementrey-dev , thank you for pointing this out. It will be fixed in the new release, I'm working on it now.

Hi @ivan-khvostishkov, I also got blocked by this issue. Is there any update on the fix?
Is the only alternative the manual steps given here?

@ivan-khvostishkov I followed the manual steps given in the doc, but unfortunately it did not work for me as far as I could tell. I am not able to see the sagemaker instances on SSM console under Systems Manager/Fleet Manager/Managed nodes. I am also not able to see the instances with
➜ sm-ssh list
SageMaker SSH Helper v2.2.0
Listing SageMaker instances for sagemaker
  Region: us-west-2
  Type: all
  FQDN: sagemaker

Neither with
➜ aws sagemaker list-notebook-instances
{
    "NotebookInstances": []
}

Can you please confirm that the manual steps given in the doc are up-to-date and valid?

Hi team, I produced a fix for the automated CDK + Cloud9 way. Request to please review once you have a chance to do so.
Thanks team,
Rohan

Hi @ivan-khvostishkov can you please look into the PR please? it's been open for two weeks so gentle reminder.

Fixed and released in v2.2.1

authors: 108krohan clementrey-dev ivan-khvostishkov mfatihaktas

repo: aws-samples/sagemaker-ssh-helper


text:
Created two AWS CLI snippets

Created AWS CLI snippets for listing CloudFormation stacks in a region and for retrieving all the AWS Lambda functions in a CloudFormation stack.
These are very useful for when you want to find details of the correct function in the AWS CLI quickly.
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Great, thanks for contribution @padajo !

repo: aws-samples/serverless-snippets


text:
Fresh deployment of DREM fails in the LeaderboardDeployToS3 stage

Fresh pull of the code and deployment is resulting in LeaderboardDeployToS3 failing.
Code build error is below
Status: Downloaded newer image for public.ecr.aws/sam/build-nodejs18.x:latest
npm notice
npm notice New major version of npm available! 10.7.0 -> 11.0.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.0.0
npm notice To update run: npm install -g npm@11.0.0
npm notice
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: react-scripts@5.0.1
npm error Found: typescript@5.7.2
npm error node_modules/typescript
npm error   peerOptional typescript@"^5" from i18next@24.2.0
npm error   node_modules/i18next
npm error     peer i18next@">= 23.2.3" from react-i18next@13.5.0
npm error     node_modules/react-i18next
npm error       react-i18next@"^13.2.0" from the root project
npm error   peer typescript@">=4.2.0" from ts-api-utils@1.4.3
npm error   node_modules/ts-api-utils
npm error     ts-api-utils@"^1.0.1" from @typescript-eslint/eslint-plugin@6.21.0
npm error     node_modules/@typescript-eslint/eslint-plugin
npm error       dev @typescript-eslint/eslint-plugin@"^6.5.0" from the root project
npm error       1 more (eslint-plugin-jest)
npm error     ts-api-utils@"^1.0.1" from @typescript-eslint/type-utils@6.21.0
npm error     node_modules/@typescript-eslint/type-utils
npm error       @typescript-eslint/type-utils@"6.21.0" from @typescript-eslint/eslint-plugin@6.21.0
npm error       node_modules/@typescript-eslint/eslint-plugin
npm error         dev @typescript-eslint/eslint-plugin@"^6.5.0" from the root project
npm error         1 more (eslint-plugin-jest)
npm error     1 more (@typescript-eslint/typescript-estree)
npm error
npm error Could not resolve dependency:
npm error peerOptional typescript@"^3.2.1 || ^4" from react-scripts@5.0.1
npm error node_modules/react-scripts
npm error   react-scripts@"5.0.1" from the root project
npm error
npm error Conflicting peer dependency: typescript@4.9.5
npm error node_modules/typescript
npm error   peerOptional typescript@"^3.2.1 || ^4" from react-scripts@5.0.1
npm error   node_modules/react-scripts
npm error     react-scripts@"5.0.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/empty-cache/_logs/2024-12-21T17_01_21_838Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/empty-cache/_logs/2024-12-21T17_01_21_838Z-debug-0.log
[Container] 2024/12/21 17:01:46.346323 Command did not exit successfully docker run --rm -v $(pwd):/foo -w /foo public.ecr.aws/sam/build-nodejs18.x:latest bash -c 'npm install --cache /tmp/empty-cache && npm run build' exit status 1
[Container] 2024/12/21 17:01:46.350513 Phase complete: BUILD State: FAILED
[Container] 2024/12/21 17:01:46.350530 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: docker run --rm -v $(pwd):/foo -w /foo public.ecr.aws/sam/build-nodejs18.x:latest bash -c 'npm install --cache /tmp/empty-cache && npm run build'. Reason: exit status 1
[Container] 2024/12/21 17:01:46.388561 Entering phase POST_BUILD
[Container] 2024/12/21 17:01:46.390581 Phase complete: POST_BUILD State: SUCCEEDED
[Container] 2024/12/21 17:01:46.390596 Phase context status code:  Message:
[Container] 2024/12/21 17:01:46.431124 Set report auto-discover timeout to 5 seconds
[Container] 2024/12/21 17:01:46.431167 Expanding base directory path:  .
[Container] 2024/12/21 17:01:46.432645 Assembling file list
[Container] 2024/12/21 17:01:46.432656 Expanding .
[Container] 2024/12/21 17:01:46.434180 Expanding file paths for base directory .
[Container] 2024/12/21 17:01:46.434189 Assembling file list
[Container] 2024/12/21 17:01:46.434192 Expanding **/*
[Container] 2024/12/21 17:01:46.437253 No matching auto-discover report paths found
[Container] 2024/12/21 17:01:46.437274 Report auto-discover file discovery took 0.006150 seconds
[Container] 2024/12/21 17:01:46.437285 Phase complete: UPLOAD_ARTIFACTS State: SUCCEEDED
[Container] 2024/12/21 17:01:46.437293 Phase context status code:  Message:

Updates to website-leaderboard/package.json as part of #80 resolve the issue


text:
Add prettier formatting

Adds prettier formatting configuration, applies it, and verifies it in run-all-tests.sh.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Had to dig in to see the changes.
LGTM

authors: evanwieren schana


text:
problem in ota_demo_core_mqtt.c : prvMqttUnSubscribe cmdCompleteCallback

Describe the bug
in ota_v3_integration branch, demos/ota/ota_demo_core_mqtt/ota_demo_core_mqtt.c, function prvMqttUnSubscribe, commandParams.cmdCompleteCallback is currently set to prvMQTTSubscribeCompleteCallback, but i think it should be set to prvMQTTUnsubscribeCompleteCallback which is currently there, but unused.
@divekarshubham i think you are working on this, so i mentioned you
Thanks!

@maa1370 Seems so. I will open a PR and reference this Issue.
In the future, feel free to open a pull request when you notice any similar issues and we will be happy to review and merge them.

repo: aws/amazon-freertos

license: MIT


text:
log4Net issue with unity 6 and AWS Gamelift version 5

I am about to test my gamelift setup locally with an "Anywhere" setting and just build my scene as a windows player. Everything seems to be okay until it runs the following code:
'''C#
using UnityEngine;
using System.Collections.Generic;
using Aws.GameLift.Server;
using Aws.GameLift.Server.Model;
using System;
using Unity.Netcode;
using System.IO;
using System.Threading.Tasks;
using Amazon.Lambda;
using Amazon.Lambda.Model;
namespace Assets.scripts.Multiplayer
{
///
/// THis is called by the server. The server must know whihc methods to call when the client wants to create aserver...
///
public class GameLiftServerInitializer : MonoBehaviour
{
    public LaunchGameServer launchGameServer;

    void Start()
    {
        //    ConfigureAppSettings();

        if (Application.platform == RuntimePlatform.WindowsEditor)
        {
            UnityEngine.Debug.Log("platform is windows Editor. This code should terminate here.");
            this.enabled = false;
            return;
        }
        else if (Application.platform == RuntimePlatform.WindowsPlayer)
        {
            UnityEngine.Debug.Log("platform is windows and you are running the test server");
            // Define the server parameters
            string webSocketUrl = "wss://eu-central-1.api.amazongamelift.com";
            string processId = "TestProcess1234";
            string fleetId = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx";
            string hostId = "LocalCompute"; // Replace with your registered compute name
            string authToken = "xxxxxxxxxxxxxxxxx"; // Retrieve this dynamically

            ServerParameters serverParameters = new ServerParameters(webSocketUrl, processId, hostId, fleetId, authToken);

            var localOutcome = GameLiftServerAPI.InitSDK(serverParameters);

        }
        else if (Application.platform == RuntimePlatform.LinuxServer || Application.platform == RuntimePlatform.LinuxPlayer  )
        {
            UnityEngine.Debug.Log("Here you should be on the server now");
            GameLiftServerAPI.InitSDK();

        }
        else if (Application.platform == RuntimePlatform.Android)
        {
            UnityEngine.Debug.Log("You are on android. This code is part of the server and thus it will not run here. Start disabling class");
            this.enabled = false;
            return;
        }
        else
        {
            Debug.LogError("Unsupported platform for GameLift server.");
            this.enabled = false;
            Application.Quit();
            return;
        }
        UnityEngine.Debug.Log("Initializing gamelift");
        InitializeGameLift();

    }

}

Here it returns the following error when it invokes InitSDK:

```C#
log4net:ERROR Exception while reading ConfigurationSettings. Check your .config file is well formed XML.
System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize ---> System.MissingMethodException: Default constructor not found for type System.Configuration.ClientConfigurationHost
  at System.RuntimeType.CreateInstanceMono (System.Boolean nonPublic, System.Boolean wrapExceptions) [0x00000] in <00000000000000000000000000000000>:0
  at System.Activator.CreateInstance (System.Type type, System.Boolean nonPublic, System.Boolean wrapExceptions) [0x00000] in <00000000000000000000000000000000>:0
  at System.Configuration.Internal.ConfigSystem.System.Configuration.Internal.IConfigSystem.Init (System.Type typeConfigHost, System.Object[] hostInitParams) [0x00000] in <00000000000000000000000000000000>:0
  at System.Configuration.ClientConfigurationSystem..ctor () [0x00000] in <00000000000000000000000000000000>:0
  at System.Configuration.ConfigurationManager.EnsureConfigurationSystem () [0x00000] in <00000000000000000000000000000000>:0
  at System.Configuration.ConfigurationManager.get_AppSettings () [0x00000] in <00000000000000000000000000000000>:0
  at log4net.Util.SystemInfo.GetAppSetting (System.String key) [0x00000] in <00000000000000000000000000000000>:0
  at log4net.Util.SystemInfo..cctor () [0x00000] in <00000000000000000000000000000000>:0
  at log4net.Core.LoggerManager.GetVersionInfo () [0x00000] in <00000000000000000000000000000000>:0
  at log4net.Core.LoggerManager..cctor () [0x00000] in <00000000000000000000000000000000>:0
  at log4net.LogManager.GetLogger (System.Type type) [0x00000] in <00000000000000000000000000000000>:0
  at Aws.GameLift.Server.GameLiftWebSocket..cctor () [0x00000] in <00000000000000000000000000000000>:0
  at Aws.GameLift.Server.ServerState..ctor () [0x00000] in <00000000000000000000000000000000>:0
  at Aws.GameLift.Server.ServerState..cctor () [0x00000] in <00000000000000000000000000000000>:0
  at Aws.GameLift.Server.GameLiftServerAPI.InitSDK (Aws.GameLift.Server.ServerParameters serverParameters) [0x00000] in <00000000000000000000000000000000>:0
  at Assets.scripts.Multiplayer.GameLiftServerInitializer.Start () [0x00000] in <00000000000000000000000000000000>:0
   --- End of inner exception stack trace ---
  at System.Configuration.ConfigurationManager.get_AppSettings () [0x00000] in <00000000000000000000000000000000>:0
  at log4net.Util.SystemInfo.GetAppSetting (System.String key) [0x00000] in <00000000000000000000000000000000>:0
  at log4net.Util.LogLog..cctor () [0x00000] in <00000000000000000000000000000000>:0
  at log4net.Util.SystemInfo.GetAppSetting (System.String key) [0x00000] in <00000000000000000000000000000000>:0
  at log4net.Util.SystemInfo..cctor () [0x00000] in <00000000000000000000000000000000>:0
  at log4net.Core.LoggerManager.GetVersionInfo () [0x00000] in <00000000000000000000000000000000>:0
  at log4net.Core.LoggerManager..cctor () [0x00000] in <00000000000000000000000000000000>:0
  at log4net.LogManager.GetLogger (System.Type type) [0x00000] in <00000000000000000000000000000000>:0
  at Aws.GameLift.Server.GameLiftWebSocket..cctor () [0x00000] in <00000000000000000000000000000000>:0
  at Aws.GameLift.Server.ServerState..ctor () [0x00000] in <00000000000000000000000000000000>:0
  at Aws.GameLift.Server.ServerState..cctor () [0x00000] in <00000000000000000000000000000000>:0
  at Aws.GameLift.Server.GameLiftServerAPI.InitSDK (Aws.GameLift.Server.ServerParameters serverParameters) [0x00000] in <00000000000000000000000000000000>:0
  at Assets.scripts.Multiplayer.GameLiftServerInitializer.Start () [0x00000] in <00000000000000000000000000000000>:0

I know that this may be because of the configuration. However, when I try to implement the config file with the sample code for the configuration with the Package manager (Log4Net Config) and invoke it manually in my class before I call InitSDK. it tells me that i have two log4net versions. One is the internal log4net version from Unity (I cannot delete it) and I assume the other one is the one which comes with the SDK. I could not figure out how to solve this because I always experience other errors when I try to delete one of them.
The following is my setup:
Unity 6
Manifest:
{
"scopedRegistries": [
{
"name": "Unity NuGet",
"url": "https://unitynuget-registry.azurewebsites.net",
"scopes": [
"org.nuget"
]
}
],
"dependencies": {
"com.amazonaws.gameliftserver.sdk": "file:C:/Users/nilsh/Downloads/GameLift-CSharp-ServerSDK-UnityPlugin-5.2.0/com.amazonaws.gameliftserver.sdk-5.2.0.tgz",
"com.github-glitchenzo.nugetforunity": "https://github.com/GlitchEnzo/NuGetForUnity.git?path=/src/NuGetForUnity",
"com.microsoft.mrtk.graphicstools.unity": "file:MixedReality/com.microsoft.mrtk.graphicstools.unity-0.7.1.tgz",
"com.unity.2d.sprite": "1.0.0",
"com.unity.ads.ios-support": "1.0.0",
"com.unity.collab-proxy": "2.5.2",
"com.unity.feature.development": "1.0.2",
"com.unity.formats.alembic": "2.4.0",
"com.unity.inputsystem": "1.11.2",
"com.unity.learn.iet-framework": "4.0.2",
"com.unity.learn.iet-framework.authoring": "1.2.2",
"com.unity.multiplayer.center": "1.0.0",
"com.unity.multiplayer.playmode": "1.3.1",
"com.unity.netcode.gameobjects": "2.1.1",
"com.unity.postprocessing": "3.4.0",
"com.unity.render-pipelines.universal": "17.0.3",
"com.unity.scriptablebuildpipeline": "2.1.5",
"com.unity.services.lobby": "1.2.2",
"com.unity.services.relay": "1.1.1",
"com.unity.test-framework": "1.4.5",
"com.unity.toolchain.linux-x86_64": "2.0.10",
"com.unity.toolchain.win-arm64-linux-x86_64": "1.0.4",
"com.unity.toolchain.win-x86_64-linux-x86_64": "2.0.10",
"com.unity.xr.arcore": "6.0.3",
"com.unity.xr.arfoundation": "6.0.3",
"com.unity.xr.hands": "1.5.0",
"com.unity.xr.interaction.toolkit": "3.0.7",
"com.unity.xr.management": "4.5.0",
"com.unity.xr.meta-openxr": "2.0.1",
"com.unity.xr.oculus": "4.3.0",
"com.unity.xr.openxr": "1.13.0",
"com.veriorpies.parrelsync": "https://github.com/VeriorPies/ParrelSync.git?path=/ParrelSync",
"org.mixedrealitytoolkit.core": "file:MixedReality/org.mixedrealitytoolkit.core-4.0.0-pre.1.tgz",
"org.mixedrealitytoolkit.diagnostics": "file:MixedReality/org.mixedrealitytoolkit.diagnostics-3.0.2.tgz",
"org.mixedrealitytoolkit.extendedassets": "file:MixedReality/org.mixedrealitytoolkit.extendedassets-3.0.3.tgz",
"org.mixedrealitytoolkit.input": "file:MixedReality/org.mixedrealitytoolkit.input-4.0.0-pre.1.tgz",
"org.mixedrealitytoolkit.spatialmanipulation": "file:MixedReality/org.mixedrealitytoolkit.spatialmanipulation-4.0.0-pre.1.tgz",
"org.mixedrealitytoolkit.standardassets": "file:MixedReality/org.mixedrealitytoolkit.standardassets-3.2.0.tgz",
"org.mixedrealitytoolkit.tools": "file:MixedReality/org.mixedrealitytoolkit.tools-3.0.4.tgz",
"org.mixedrealitytoolkit.uxcomponents": "file:MixedReality/org.mixedrealitytoolkit.uxcomponents-4.0.0-pre.1.tgz",
"org.mixedrealitytoolkit.uxcomponents.noncanvas": "file:MixedReality/org.mixedrealitytoolkit.uxcomponents.noncanvas-4.0.0-pre.1.tgz",
"org.mixedrealitytoolkit.uxcore": "file:MixedReality/org.mixedrealitytoolkit.uxcore-4.0.0-pre.1.tgz",
"org.nuget.awssdk.core": "3.7.400",
"org.nuget.awssdk.s3": "3.7.410",
"org.nuget.awssdk.securitytoken": "3.7.401",
"org.nuget.csvhelper": "33.0.1",
"com.unity.modules.physics2d": "1.0.0"
}
}
I dont know how to solve this and I see it rather as an issue of the SDK. It would be great if there is a way to either remove the log4net package from the SDK or use an alternative logging.

I solved the issue by deleting the Unity package versioncontrol. However, after that I encountered another problem. I keep having this error: log4net:ERROR Exception while reading ConfigurationSettings. Check your .config file is well formed XML.
And I absolutely do not get why. I put the config file for log4net in the streaming assets path. Then referenced it in the script like this:

        private static void ConfigureLog4Net()
        {
            var configPath = System.IO.Path.Combine(Application.streamingAssetsPath, "log4net.xml");
            var fileInfo = new System.IO.FileInfo(configPath);

            if (fileInfo.Exists)
            {
                log4net.Config.XmlConfigurator.Configure(fileInfo);
                Debug.Log("log4net configured successfully.");
            }
            else
            {
                Debug.LogError("log4net.xml not found in StreamingAssets.");
            }
        }

I tried it as .xml file and .conf file. The method was called in the beginning of my start method. Also I tried several versions of the config file where I copied your version from the Samples and tried it or modified it to a very simple version with ChatGPT. Basically it never worked. I also tried to just disable the entire debugging by setting it in the beginning of the code:

            AWSConfigs.LoggingConfig.LogTo = LoggingOptions.None;
            AWSConfigs.LoggingConfig.LogResponses = ResponseLoggingOption.Never;
            AWSConfigs.LoggingConfig.LogMetrics = false;

Still, I had the same error. You can see the full error here:
log4net:ERROR Exception while reading ConfigurationSettings. Check your .config file is well formed XML.
System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize ---> System.MissingMethodException: Default constructor not found for type System.Configuration.ClientConfigurationHost
at System.RuntimeType.CreateInstanceMono (System.Boolean nonPublic, System.Boolean wrapExceptions) [0x00076] in :0
at System.RuntimeType.CreateInstanceSlow (System.Boolean publicOnly, System.Boolean wrapExceptions, System.Boolean skipCheckThis, System.Boolean fillCache) [0x00009] in :0
at System.RuntimeType.CreateInstanceDefaultCtor (System.Boolean publicOnly, System.Boolean skipCheckThis, System.Boolean fillCache, System.Boolean wrapExceptions, System.Threading.StackCrawlMark& stackMark) [0x00027] in :0
at System.Activator.CreateInstance (System.Type type, System.Boolean nonPublic, System.Boolean wrapExceptions) [0x00020] in :0
at System.Activator.CreateInstance (System.Type type, System.Boolean nonPublic) [0x00000] in :0
at System.Configuration.TypeUtil.CreateInstance (System.Type type) [0x00000] in :0
at System.Configuration.Internal.ConfigSystem.System.Configuration.Internal.IConfigSystem.Init (System.Type typeConfigHost, System.Object[] hostInitParams) [0x0000b] in :0
at System.Configuration.ClientConfigurationSystem..ctor () [0x0000c] in :0
at System.Configuration.ConfigurationManager.EnsureConfigurationSystem () [0x00024] in :0
--- End of inner exception stack trace ---
at System.Configuration.ConfigurationManager.PrepareConfigSystem () [0x0001a] in :0
at System.Configuration.ConfigurationManager.GetSection (System.String sectionName) [0x0000a] in :0
at System.Configuration.ConfigurationManager.get_AppSettings () [0x00000] in :0
at log4net.Util.SystemInfo.GetAppSetting (System.String key) [0x00000] in <2599f4b68b884a8e9936e90d695ab43f>:0
log4net:ERROR Exception while reading ConfigurationSettings. Check your .config file is well formed XML.
System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize ---> System.MissingMethodException: Default constructor not found for type System.Configuration.ClientConfigurationHost
at System.RuntimeType.CreateInstanceMono (System.Boolean nonPublic, System.Boolean wrapExceptions) [0x00076] in :0
at System.RuntimeType.CreateInstanceSlow (System.Boolean publicOnly, System.Boolean wrapExceptions, System.Boolean skipCheckThis, System.Boolean fillCache) [0x00009] in :0
at System.RuntimeType.CreateInstanceDefaultCtor (System.Boolean publicOnly, System.Boolean skipCheckThis, System.Boolean fillCache, System.Boolean wrapExceptions, System.Threading.StackCrawlMark& stackMark) [0x00027] in :0
at System.Activator.CreateInstance (System.Type type, System.Boolean nonPublic, System.Boolean wrapExceptions) [0x00020] in :0
at System.Activator.CreateInstance (System.Type type, System.Boolean nonPublic) [0x00000] in :0
at System.Configuration.TypeUtil.CreateInstance (System.Type type) [0x00000] in :0
at System.Configuration.Internal.ConfigSystem.System.Configuration.Internal.IConfigSystem.Init (System.Type typeConfigHost, System.Object[] hostInitParams) [0x0000b] in :0
at System.Configuration.ClientConfigurationSystem..ctor () [0x0000c] in :0
at System.Configuration.ConfigurationManager.EnsureConfigurationSystem () [0x00024] in :0
--- End of inner exception stack trace ---
at System.Configuration.ConfigurationManager.PrepareConfigSystem () [0x0001a] in :0
at System.Configuration.ConfigurationManager.GetSection (System.String sectionName) [0x0000a] in :0
at System.Configuration.ConfigurationManager.get_AppSettings () [0x00000] in :0
at log4net.Util.SystemInfo.GetAppSetting (System.String key) [0x00000] in <2599f4b68b884a8e9936e90d695ab43f>:0
log4net:ERROR Exception while reading ConfigurationSettings. Check your .config file is well formed XML.
System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize ---> System.MissingMethodException: Default constructor not found for type System.Configuration.ClientConfigurationHost
at System.RuntimeType.CreateInstanceMono (System.Boolean nonPublic, System.Boolean wrapExceptions) [0x00076] in :0
at System.RuntimeType.CreateInstanceSlow (System.Boolean publicOnly, System.Boolean wrapExceptions, System.Boolean skipCheckThis, System.Boolean fillCache) [0x00009] in :0
at System.RuntimeType.CreateInstanceDefaultCtor (System.Boolean publicOnly, System.Boolean skipCheckThis, System.Boolean fillCache, System.Boolean wrapExceptions, System.Threading.StackCrawlMark& stackMark) [0x00027] in :0
at System.Activator.CreateInstance (System.Type type, System.Boolean nonPublic, System.Boolean wrapExceptions) [0x00020] in :0
at System.Activator.CreateInstance (System.Type type, System.Boolean nonPublic) [0x00000] in :0
at System.Configuration.TypeUtil.CreateInstance (System.Type type) [0x00000] in :0
at System.Configuration.Internal.ConfigSystem.System.Configuration.Internal.IConfigSystem.Init (System.Type typeConfigHost, System.Object[] hostInitParams) [0x0000b] in :0
at System.Configuration.ClientConfigurationSystem..ctor () [0x0000c] in :0
at System.Configuration.ConfigurationManager.EnsureConfigurationSystem () [0x00024] in :0
--- End of inner exception stack trace ---
at System.Configuration.ConfigurationManager.PrepareConfigSystem () [0x0001a] in :0
at System.Configuration.ConfigurationManager.GetSection (System.String sectionName) [0x0000a] in :0
at System.Configuration.ConfigurationManager.get_AppSettings () [0x00000] in :0
at log4net.Util.SystemInfo.GetAppSetting (System.String key) [0x00000] in <2599f4b68b884a8e9936e90d695ab43f>:0
log4net:ERROR Exception while reading ConfigurationSettings. Check your .config file is well formed XML.
System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize ---> System.MissingMethodException: Default constructor not found for type System.Configuration.ClientConfigurationHost
at System.RuntimeType.CreateInstanceMono (System.Boolean nonPublic, System.Boolean wrapExceptions) [0x00076] in :0
at System.RuntimeType.CreateInstanceSlow (System.Boolean publicOnly, System.Boolean wrapExceptions, System.Boolean skipCheckThis, System.Boolean fillCache) [0x00009] in :0
at System.RuntimeType.CreateInstanceDefaultCtor (System.Boolean publicOnly, System.Boolean skipCheckThis, System.Boolean fillCache, System.Boolean wrapExceptions, System.Threading.StackCrawlMark& stackMark) [0x00027] in :0
at System.Activator.CreateInstance (System.Type type, System.Boolean nonPublic, System.Boolean wrapExceptions) [0x00020] in :0
at System.Activator.CreateInstance (System.Type type, System.Boolean nonPublic) [0x00000] in :0
at System.Configuration.TypeUtil.CreateInstance (System.Type type) [0x00000] in :0
at System.Configuration.Internal.ConfigSystem.System.Configuration.Internal.IConfigSystem.Init (System.Type typeConfigHost, System.Object[] hostInitParams) [0x0000b] in :0
at System.Configuration.ClientConfigurationSystem..ctor () [0x0000c] in :0
at System.Configuration.ConfigurationManager.EnsureConfigurationSystem () [0x00024] in :0
--- End of inner exception stack trace ---
at System.Configuration.ConfigurationManager.PrepareConfigSystem () [0x0001a] in :0
at System.Configuration.ConfigurationManager.GetSection (System.String sectionName) [0x0000a] in :0
at System.Configuration.ConfigurationManager.get_AppSettings () [0x00000] in :0
at log4net.Util.SystemInfo.GetAppSetting (System.String key) [0x00000] in <2599f4b68b884a8e9936e90d695ab43f>:0
log4net:ERROR Exception while reading ConfigurationSettings. Check your .config file is well formed XML.
System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize ---> System.MissingMethodException: Default constructor not found for type System.Configuration.ClientConfigurationHost
at System.RuntimeType.CreateInstanceMono (System.Boolean nonPublic, System.Boolean wrapExceptions) [0x00076] in :0
at System.RuntimeType.CreateInstanceSlow (System.Boolean publicOnly, System.Boolean wrapExceptions, System.Boolean skipCheckThis, System.Boolean fillCache) [0x00009] in :0
at System.RuntimeType.CreateInstanceDefaultCtor (System.Boolean publicOnly, System.Boolean skipCheckThis, System.Boolean fillCache, System.Boolean wrapExceptions, System.Threading.StackCrawlMark& stackMark) [0x00027] in :0
at System.Activator.CreateInstance (System.Type type, System.Boolean nonPublic, System.Boolean wrapExceptions) [0x00020] in :0
at System.Activator.CreateInstance (System.Type type, System.Boolean nonPublic) [0x00000] in :0
at System.Configuration.TypeUtil.CreateInstance (System.Type type) [0x00000] in :0
at System.Configuration.Internal.ConfigSystem.System.Configuration.Internal.IConfigSystem.Init (System.Type typeConfigHost, System.Object[] hostInitParams) [0x0000b] in :0
at System.Configuration.ClientConfigurationSystem..ctor () [0x0000c] in :0
at System.Configuration.ConfigurationManager.EnsureConfigurationSystem () [0x00024] in :0
--- End of inner exception stack trace ---
at System.Configuration.ConfigurationManager.PrepareConfigSystem () [0x0001a] in :0
at System.Configuration.ConfigurationManager.GetSection (System.String sectionName) [0x0000a] in :0
at System.Configuration.ConfigurationManager.get_AppSettings () [0x00000] in :0
at log4net.Util.SystemInfo.GetAppSetting (System.String key) [0x00000] in <2599f4b68b884a8e9936e90d695ab43f>:0
log4net:ERROR Exception while reading ConfigurationSettings. Check your .config file is well formed XML.
System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize ---> System.MissingMethodException: Default constructor not found for type System.Configuration.ClientConfigurationHost
at System.RuntimeType.CreateInstanceMono (System.Boolean nonPublic, System.Boolean wrapExceptions) [0x00076] in :0
at System.RuntimeType.CreateInstanceSlow (System.Boolean publicOnly, System.Boolean wrapExceptions, System.Boolean skipCheckThis, System.Boolean fillCache) [0x00009] in :0
at System.RuntimeType.CreateInstanceDefaultCtor (System.Boolean publicOnly, System.Boolean skipCheckThis, System.Boolean fillCache, System.Boolean wrapExceptions, System.Threading.StackCrawlMark& stackMark) [0x00027] in :0
at System.Activator.CreateInstance (System.Type type, System.Boolean nonPublic, System.Boolean wrapExceptions) [0x00020] in :0
at System.Activator.CreateInstance (System.Type type, System.Boolean nonPublic) [0x00000] in :0
at System.Configuration.TypeUtil.CreateInstance (System.Type type) [0x00000] in :0
at System.Configuration.Internal.ConfigSystem.System.Configuration.Internal.IConfigSystem.Init (System.Type typeConfigHost, System.Object[] hostInitParams) [0x0000b] in :0
at System.Configuration.ClientConfigurationSystem..ctor () [0x0000c] in :0
at System.Configuration.ConfigurationManager.EnsureConfigurationSystem () [0x00024] in :0
--- End of inner exception stack trace ---
at System.Configuration.ConfigurationManager.PrepareConfigSystem () [0x0001a] in :0
at System.Configuration.ConfigurationManager.GetSection (System.String sectionName) [0x0000a] in :0
at System.Configuration.ConfigurationManager.get_AppSettings () [0x00000] in :0
at log4net.Util.SystemInfo.GetAppSetting (System.String key) [0x00000] in <2599f4b68b884a8e9936e90d695ab43f>:0
MissingMethodException: Default constructor not found for type log4net.Repository.Hierarchy.Hierarchy
at System.RuntimeType.CreateInstanceMono (System.Boolean nonPublic, System.Boolean wrapExceptions) [0x00076] in :0
at System.RuntimeType.CreateInstanceSlow (System.Boolean publicOnly, System.Boolean wrapExceptions, System.Boolean skipCheckThis, System.Boolean fillCache) [0x00009] in :0
at System.RuntimeType.CreateInstanceDefaultCtor (System.Boolean publicOnly, System.Boolean skipCheckThis, System.Boolean fillCache, System.Boolean wrapExceptions, System.Threading.StackCrawlMark& stackMark) [0x00027] in :0
at System.Activator.CreateInstance (System.Type type, System.Boolean nonPublic, System.Boolean wrapExceptions) [0x00020] in :0
at System.Activator.CreateInstance (System.Type type, System.Boolean nonPublic) [0x00000] in :0
at System.Activator.CreateInstance (System.Type type) [0x00000] in :0
at log4net.Core.DefaultRepositorySelector.CreateRepository (System.String repositoryName, System.Type repositoryType) [0x0016f] in <2599f4b68b884a8e9936e90d695ab43f>:0
at log4net.Core.DefaultRepositorySelector.CreateRepository (System.Reflection.Assembly repositoryAssembly, System.Type repositoryType, System.String repositoryName, System.Boolean readAssemblyAttributes) [0x000f2] in <2599f4b68b884a8e9936e90d695ab43f>:0
at log4net.Core.DefaultRepositorySelector.CreateRepository (System.Reflection.Assembly repositoryAssembly, System.Type repositoryType) [0x00000] in <2599f4b68b884a8e9936e90d695ab43f>:0
at log4net.Core.DefaultRepositorySelector.GetRepository (System.Reflection.Assembly repositoryAssembly) [0x00014] in <2599f4b68b884a8e9936e90d695ab43f>:0
at log4net.Core.LoggerManager.GetLogger (System.Reflection.Assembly repositoryAssembly, System.String name) [0x00027] in <2599f4b68b884a8e9936e90d695ab43f>:0
at log4net.LogManager.GetLogger (System.Reflection.Assembly repositoryAssembly, System.String name) [0x00000] in <2599f4b68b884a8e9936e90d695ab43f>:0
at log4net.LogManager.GetLogger (System.Type type) [0x0000b] in <2599f4b68b884a8e9936e90d695ab43f>:0
at Aws.GameLift.Server.GameLiftWebSocket..cctor () [0x00000] in .\Library\PackageCache\com.amazonaws.gameliftserver.sdk\Runtime\Core\Server
So, since I cannot disable debugging, cannot disable log4net and also cannot modifty the logging from the sdk itself in anyway what would you suggest me to do? I tried to follow your sample and instructions and it seems to be impossible for me to use it.

For everyone else having this issue, I solved this by doing the following:

Downloading the C# Server SDK from here: https://aws.amazon.com/de/gamelift/getting-started-sdks/
Creating a new folder in your Assets/ folder which I named aws.
Creating an assembly definition there for referencing it later.
Copying the three subfolders under src/GameLiftServerSDK to my folder aws in Assets/
Replacing all Log statements associated with log4net with UnityEngine.Debug.Log / LogError / LogWarning
Removing all log4net references
Installing the missing dependencies (in my case it was only Polly)
using InitSDK , ProcessParameters and ProcessReady and it worked.

Kind of crazy to do that but then the build will just save the unity debug statements in the corresponding output file in AppData from your build and the information will be enough for debugging (Not sure how it is different from log4net though).

repo: aws/amazon-gamelift-plugin-unity


text:
Add EFS access point support (aws-parallelcluster#2337)

Description of changes
Add support to specify EFS access points per issue aws/aws-parallelcluster#2337
Tests
Tested mounting EFS with and without accesspoints from an aws-parallelcluster cluster.
More tests to be done but opening a draft PR for discussion and early feedback
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Hi @thheinen,
thanks a lot for your contribution!
Made a first round of review and unblocked PR checks.

authors: gmarciani thheinen

repo: aws/aws-parallelcluster


text:
Can I query number of operations on S3 Bucket using the SDK/API?

Confirm by changing [ ] to [x] below:

[x ] I've gone though Developer Guide and API reference
[ x] I've searched for previous similar issues and didn't find any solution

Platform/OS/Hardware/Device
What are you running the sdk on?
Linux
Describe the question
I want to know how many operations (REST requests) I've done on a specific bucket in the last month. Is there a way I can get this information with the SDK/API?
Thanks,
Dror
Logs/output
If applicable, add logs or error output.
To enable logging, set the following system properties:
REMEMBER TO SANITIZE YOUR PERSONAL INFO
options.loggingOptions.logLevel = Aws::Utils::Logging::LogLevel::Trace;
Aws::InitAPI(options)

@drorgy ,
Kind of, s3 buckets have what's called an Access Log which has to be manually enabled, either from the console or the sdk, you can read more about what those are here.
Once enabled

Amazon S3 periodically collects access log records, consolidates the records in log files, and then uploads log files to your target bucket as log objects.

Not sure if that is exactly what you're looking for though. I also noticed that there is only a sample on how to do it for .NET but if you need that on C++ let me know and I can write a quick similar one for you too.

@KaibaLopez
Thanks for the information.
You mention that there is a sample of how to do it in .NET (can you please send a link). You wrote that the Access Log is manually enabled (as opposed to programmatically), so what can be done in .NET/C++.
Thanks again,
Dror

Yea, these are the 2 documentation pages on enabling those logs: manually and programatically.

authors: KaibaLopez drorgy

repo: aws/aws-sdk-cpp


text:
The difference between the request time and the current time is too large

I am getting an error the time difference between the request time and the current time is too large while sending large files more than 100 MB with the help of (Multi part Upload Request)
I read out the same issue id #211 there advised to use aws sdk V3. I was using 2.3.26 first but now i am using 2.3.40 but getting the same error.
i was not able to find the solution and stuck here. please help me and give suggestion that what should i do.
Please let me know if any more information you needed.
Thanks:)

Can you provide the code that you are using?

authors: AmitManchanda PavelSafronov

repo: aws/aws-sdk-net


text:
Allow to remove TableNameSuffix on operation level

Fixes #3470
Description
Allow to remove TableNameSuffix in operation-level configs by setting an empty string.
Motivation and Context
In some cases I have most of the tables with suffix, and one or two, which do not correspond to such convention. In this case I would like to be able to use TableNameSuffix globally, but remove it per operation.
Testing
Added unit tests.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project
[ ] My change requires a change to the documentation
[x] I have updated the documentation accordingly
[x] I have read the README document
[x] I have added tests to cover my changes
[x] All new and existing tests passed

License

[x] I confirm that this pull request can be released under the Apache 2 license

Verified that all unit tests and integrations tests pass locally.
@dscpinheiro has initiated a full dry-run that will run this commit through our build system.

@Dreamescaper Shouldn't the PR title and the commit message read_"...remove TableNamePrefix"_ instead of TableNameSuffix?
Unless I am missing something.


text:
Fix changelog and bump version for new release

Fixes changelog and bumps version for new release
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Updated everything to 4.0.2


text:
X-Ray migration on Django: XRayTracedConn subclassing of psycopg's connection throws exception

After an update to my code base (my branch was 2 weeks behind), suddenly my working branch failed to build my core application's Docker container (using containers, all local, including the X-Ray Daemon), the output shows this:

Full output:
ALEXKLEMAS: docker_wrapper_recorder
ALEXKLEMAS: docker_XRAY mode has been enabled
ALEXKLEMAS: VERIFYING SERVICE PASSED ALONG: Project_WRAPPER_MDW
ALEXKLEMAS: docker_wrapper_recorder
ALEXKLEMAS: docker_XRAY mode has been enabled
ALEXKLEMAS: VERIFYING SERVICE PASSED ALONG: Project_WRAPPER_PRICER
ALEXKLEMAS: docker_wrapper_recorder
ALEXKLEMAS: docker_XRAY mode has been enabled
ALEXKLEMAS: VERIFYING SERVICE PASSED ALONG: Project_WRAPPER_COMMON
ALEXKLEMAS: docker_wrapper_recorder
ALEXKLEMAS: docker_XRAY mode has been enabled
ALEXKLEMAS: VERIFYING SERVICE PASSED ALONG: Project_WRAPPER_COLLECTORS
ALEXKLEMAS: docker_wrapper_recorder
ALEXKLEMAS: docker_XRAY mode has been enabled
ALEXKLEMAS: VERIFYING SERVICE PASSED ALONG: Project_WRAPPER_BASIC
ALEXKLEMAS: docker_wrapper_recorder
ALEXKLEMAS: docker_XRAY mode has been enabled
ALEXKLEMAS: VERIFYING SERVICE PASSED ALONG: Project_WRAPPER_ENVIRONMENT

Executing Django Command: /opt/app/work_project/work_company/project/manage.py migrate
Traceback (most recent call last):
File "/usr/local/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/usr/local/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/opt/app/work_project/work_company/project/manage.py", line 39, in <module>
execute_from_command_line(sys.argv)
File "/usr/local/lib/python3.6/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line
utility.execute()
File "/usr/local/lib/python3.6/site-packages/django/core/management/__init__.py", line 395, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/local/lib/python3.6/site-packages/django/core/management/base.py", line 330, in run_from_argv
self.execute(*args, **cmd_options)
File "/usr/local/lib/python3.6/site-packages/django/core/management/base.py", line 371, in execute
output = self.handle(*args, **options)
File "/usr/local/lib/python3.6/site-packages/django/core/management/base.py", line 85, in wrapped
res = handle_func(*args, **kwargs)
File "/usr/local/lib/python3.6/site-packages/django/core/management/commands/migrate.py", line 92, in handle
executor = MigrationExecutor(connection, self.migration_progress_callback)
File "/usr/local/lib/python3.6/site-packages/django/db/migrations/executor.py", line 18, in __init__
self.loader = MigrationLoader(self.connection)
File "/usr/local/lib/python3.6/site-packages/django/db/migrations/loader.py", line 53, in __init__
self.build_graph()
File "/usr/local/lib/python3.6/site-packages/django/db/migrations/loader.py", line 216, in build_graph
self.applied_migrations = recorder.applied_migrations()
File "/usr/local/lib/python3.6/site-packages/django/db/migrations/recorder.py", line 77, in applied_migrations
if self.has_table():
File "/usr/local/lib/python3.6/site-packages/django/db/migrations/recorder.py", line 55, in has_table
with self.connection.cursor() as cursor:
File "/usr/local/lib/python3.6/site-packages/aws_xray_sdk/ext/django/db.py", line 81, in cursor
original_cursor = getattr(self, attr)(*args, **kwargs)
File "/usr/local/lib/python3.6/site-packages/django/utils/asyncio.py", line 26, in inner
return func(*args, **kwargs)
File "/usr/local/lib/python3.6/site-packages/django/db/backends/base/base.py", line 259, in cursor
return self._cursor()
File "/usr/local/lib/python3.6/site-packages/django/db/backends/base/base.py", line 235, in _cursor
self.ensure_connection()
File "/usr/local/lib/python3.6/site-packages/django/utils/asyncio.py", line 26, in inner
return func(*args, **kwargs)
File "/usr/local/lib/python3.6/site-packages/django/db/backends/base/base.py", line 219, in ensure_connection
self.connect()
File "/usr/local/lib/python3.6/site-packages/django/utils/asyncio.py", line 26, in inner
return func(*args, **kwargs)
File "/usr/local/lib/python3.6/site-packages/django/db/backends/base/base.py", line 200, in connect
self.connection = self.get_new_connection(conn_params)
File "/usr/local/lib/python3.6/site-packages/django/utils/asyncio.py", line 26, in inner
return func(*args, **kwargs)
File "/usr/local/lib/python3.6/site-packages/django/db/backends/postgresql/base.py", line 206, in get_new_connection
psycopg2.extras.register_default_jsonb(conn_or_curs=connection, loads=lambda x: x)
File "/usr/local/lib/python3.6/site-packages/psycopg2/_json.py", line 156, in register_default_jsonb
loads=loads, oid=JSONB_OID, array_oid=JSONBARRAY_OID, name='jsonb')
File "/usr/local/lib/python3.6/site-packages/psycopg2/_json.py", line 125, in register_json
register_type(JSON, not globally and conn_or_curs or None)
TypeError: argument 2 must be a connection, cursor or None

And upon finding this (still open) bug #148, tried to see if the subclassing was also False:
Python 3.6.9 (default, Jul 17 2020, 12:50:27)
[GCC 8.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from aws_xray_sdk.ext.dbapi2 import XRayTracedConn
>>> from psycopg2.extensions import connection
>>> issubclass(XRayTracedConn, connection)
False
>>> exit()

I'm not sure, but it sure looks like the same issue, 2 years later, is still ongoing.
I read https://docs.aws.amazon.com/xray-sdk-for-python/latest/reference/frameworks.html#local-development and here's my Django config:
# ##### AWS XRAY Specifics ###############################

XRAY_RECORDER = {
    "AUTO_INSTRUMENT": True,
    "AWS_XRAY_CONTEXT_MISSING": "LOG_ERROR",
    "AWS_XRAY_DAEMON_ADDRESS": "127.0.0.1:2000",
    "AWS_XRAY_TRACING_NAME": "Project_DJANGO",
    "PLUGINS": ("ECSPlugin", "ElasticBeanstalkPlugin"),
    "SAMPLING": False,
}

And my psycopg2 level is 2.8.5 (#148 reported value of 2.7.7)
This is blocking our usage of X-Ray (which was working just fine), has there been any progress on it, or a possible workaround (didn't quite get the workaround mentioned in #148)?

Hi @alexklemas ,
Seems like it's an issue raised by the incompatibility of XRayTracedConn and psycopg2.extensions.connection due to wrapt is not properly subclassing the connection or cursor object.
Have you tried the method mentioned in #148 to mitigate this issue?
We'll need some further investigation on this and will get back to you soon
Thanks for the patience

Hi @alexklemas
I'm closing this one to de-dupe and tracking in the issue #243. Please find any updates there and feel free to add any comments. Thanks!

authors: alexklemas lupengamzn srprash

repo: aws/aws-xray-sdk-python


text:
fix: updated logic to copy sln to another folder

Related issue
Closes: #ISSUE_NUMBER_HERE
Description

Describe the changes in this pull request

Supplemental testing
Describe any testing done in addition to existing unit tests
Additional context
Please provide any additional information related to this PR

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

If the PR doesn't have any tests, please add before merging

Member

This PR will be covered by existing tests, but found an issue on the codelyzer on which Jonathan is working on. Will add the test once Jonathan merges his changes

authors: marknfawaz saikiranakula-amzn

repo: aws/cta


text:
Add release notes to PR description

Adding release notes to the upgrade PRs that the bot opens.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

repo: aws/eks-anywhere-build-tooling


text:
Packages deleted while the controller was down are not reconciled

Install a package
Shut down the controller
Delete the package
Start the controller

Expected: The controller removes the installation part of the deleted package
Actual: The installation remains

Good call here. Labeling installed resources would probably help here.

This probably needs to be done first https://github.com/aws/eks-anywhere-packages/issues/107

authors: TerryHowe lewisdiamond

repo: aws/eks-anywhere-packages


text:
Cluster-autoscaler errors on permissions

What happened:
I follow the docs and the ADC for getting cluster autoscaler to function, but it appears to be missing some permissions, I've checked the curated patches and I don't see how it could be working.
3
I0621 11:28:57.621036       1 clusterapi_provider.go:67] discovered node group: MachineDeployment/eksa-system/w01-md-0 (min: 1, max: 30, replicas: 3)
22
I0621 11:28:57.625886       1 clusterapi_provider.go:67] discovered node group: MachineDeployment/eksa-system/w01-md-0 (min: 1, max: 30, replicas: 3)
21
I0621 11:28:57.625931       1 clusterapi_controller.go:726] waiting for cache sync on infrastructure resource
20
I0621 11:28:57.626039       1 reflector.go:205] Reflector from k8s.io/client-go/dynamic/dynamicinformer/informer.go:91 configured with expectedType of *unstructured.Unstructured with empty GroupVersionKind.
19
I0621 11:28:57.626068       1 reflector.go:221] Starting reflector *unstructured.Unstructured (0s) from k8s.io/client-go/dynamic/dynamicinformer/informer.go:91
18
I0621 11:28:57.626075       1 reflector.go:257] Listing and watching *unstructured.Unstructured from k8s.io/client-go/dynamic/dynamicinformer/informer.go:91
17
W0621 11:28:57.627058       1 reflector.go:424] k8s.io/client-go/dynamic/dynamicinformer/informer.go:91: failed to list *unstructured.Unstructured: vspheremachinetemplates.infrastructure.cluster.x-k8s.io is forbidden: User "system:serviceaccount:kube-system:cluster-autoscaler" cannot list resource "vspheremachinetemplates" in API group "infrastructure.cluster.x-k8s.io" at the cluster scope
16
E0621 11:28:57.627094       1 reflector.go:140] k8s.io/client-go/dynamic/dynamicinformer/informer.go:91: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: vspheremachinetemplates.infrastructure.cluster.x-k8s.io is forbidden: User "system:serviceaccount:kube-system:cluster-autoscaler" cannot list resource "vspheremachinetemplates" in API group "infrastructure.cluster.x-k8s.io" at the cluster scope
15
I0621 11:28:58.984700       1 reflector.go:257] Listing and watching *unstructured.Unstructured from k8s.io/client-go/dynamic/dynamicinformer/informer.go:91

What you expected to happen:
I'd expect the error messages to not exist and scaling to function.
How to reproduce it (as minimally and precisely as possible):
Deploy a cluster with the annotations and install cluster autoscaler.
Anything else we need to know?:
It looks related to https://github.com/kubernetes/autoscaler/issues/5509
Ideally I'd just like you to confirm if this works in your labs/tests.
Environment:

EKS Anywhere Release: 0.16.0
EKS Distro Release: 1.27

@eperdeme are you running EKS Anywhere Curated Packages' Cluster Autoscaler image/helm chart or a community support cluster autoscaler image/helm chart?

Community edition, the official cluster autoscaler helm chart from kube.

@eperdeme Got it. We have not seen the exact issue and we build our Curated Packages Cluster Autoscaler image from commit 299c9637229fb2bf849c1d86243fe2948d14101e.
We did see a similar issue to that with the 1.27 cluster autoscaler image requiring MachinePool permissions. We resolved it in our curated packages helm chart with this patch.
If you modify this section of your helm chart and add vspheremachinetemplates as a resource I think that should solve the issue for you.

repo: aws/eks-anywhere


text:
trigger prod cli 0.16

Issue #, if available:
Description of changes:
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/approve

authors: ddjjia mitalipaygude


text:
Update upgradeable attributes docs to include registryMirrorConfiguration

Issue #, if available:
Description of changes:
Testing (if applicable):
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/meow

/cherry-pick release-0.17


text:
Bump kops to v1.28.0-alpha.1

Issue #, if available:
Description of changes:
Related to https://github.com/aws/eks-distro/pull/2215
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/hold

/lgtm

/approved

/unhold

authors: bhavi-koduru rcrozean

repo: aws/eks-distro-build-tooling


text:
add generate-attribution script for generating ATTRIBUTION.txt files

** Please review by commit **
This adds the generate-attribution script I wrote last year for the eks-d release to generate the ATTRIBUTION.txt files for each of our dependencies projects.  I have broken this up into 3 commits for easier review.

adding generate script
adding generate script + go-licenses to the builder-base
adding test cases for generate script based on projects from eks-d.  These were added to make it easier if we ever need to make changes later and/or want to rewrite this in golang so its easier for others to maintain.

I have another PR coming on eks-distro to get this in use so that our ATTRIBUTION.txt files can be updated automatically when pushing new versions.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/retest


text:
Created and updated docs for 1.28

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/approve

/unhold

repo: aws/eks-distro


text:
node-driver-registrar project updates 1.25-1.29

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

/lgtm