text:
use sts GetCallerIdentity to find AWS AccountID

Description of changes:
Breaking changes : Removing --aws-account-id flag from controller binary. This flag can allow users to enter wrong account_id during controller installation which can cause incorrect controller logs and confusion

If aws-region flags are missing, default to 'AWS_REGION' env variable
Add new method Config.SetAccountID() to use sts GetCallerIdentity for detecting aws account-id.

TODO: code-gen update to remove --aws-account-id flag, community repo docs update and test-infra update to drop aws-account-id from test-helm.sh & kind-build-test.sh

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

/lgtm

Dang, I actually liked being able to set the Account_Id explicitly as I use a couple different accounts when developing locally.

This flag can allow users to enter wrong account_id during controller installation which can cause incorrect controller logs and confusion

If the account_id is malformed or missing, then using your env-var-fallback as a default is a good strategy, but is the opportunity to mistype a value a good enough reason to remove a flag? Does this imply mistyping other controller flags will not lead to incorrect controller logs and confusion?

authors: A-Hilaly brycahta vijtrip2


text:
Allow nested statements by overwriting their types with string

Issue #, if available:
Description of changes:

on top of, and to be reviewed after https://github.com/aws-controllers-k8s/wafv2-controller/pull/7
nested statements are allowed in yaml files via strings e.g.

      statement:
        andStatement: |
          statements:
            - labelMatchStatement:
                scope: "RULE_SET"
                key: "aws:UserAgent"
                value: "Mozilla"
            - ipSetReferenceStatement:
                arn: "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"

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

@TiberiuGC can we have a v0.0.3 release please?

source: gharchive/pull-request

authors: TiberiuGC a-hilaly

license_type: permissive

license_source: github-api


text:
(gdk): Hidden files are not included in component's zip artifact

Feature Description
Hidden configuration files should (optionally) be included in the component's zip artifact.
Use Case
I need this feature to include files like .eslintrc.js.
Proposed Solution
Perhaps files could be blacklisted with a file called .greengrassignore, or they could be whitelisted in the gdk-config file.
Other
I'm aware of #109, but hidden configuration files should at least be optionally included using zip build system.
Also, this should be mentioned in https://docs.aws.amazon.com/greengrass/v2/developerguide/greengrass-development-kit-cli-component.html. I couldn't understand why these files were not included in my project until I found #109

If you specify your own excludes list, then the default excludes won't be used.
This is explained in the documentation here: https://docs.aws.amazon.com/greengrass/v2/developerguide/gdk-cli-configuration-file.html#:~:text=The following files are excluded by default. However%2C you can control which of these files are excluded with the excludes option.

I overlooked gdk config file doc, thank you very much

source: gharchive/issue

repo: aws-greengrass/aws-greengrass-gdk-cli


text:
Differing min-layer-size between CLI and Index Builder

Problem
The SOCI CLI sets a 10 MiB default --min-layer-size threshold when building indexes, which means layers under 10 MiB will not get zTOCs created for them. The index builder sets the min-layer-size to 0 - https://github.com/aws-ia/cfn-ecr-aws-soci-index-builder/blob/3c562dc3d0534206546de9e786c61342ac95f5b7/functions/source/soci-index-generator-lambda/handler.go#L273 ideally, the CLI and the index builder should have the same defaults.
Expected Behavior
The SOCI CLI and Index Builder should have the same defaults for creating indexes.
Current Behavior
Different min-layer-size for both the SOCI CLI and index builder.
Possible Solution
If you have a solution or workaround in mind, please describe it here.
Steps to Reproduce (if applicable)
If you're reporting a bug, please provide steps to reproduce the issue.

Screenshots (if applicable)
If you have any relevant screenshots, please attach them here.
Environment
Please provide information about the environment in which you're experiencing the issue, including:

Project version:
Operating system:
Browser version (if applicable):
Any relevant hardware or software information:

Additional Context
Please provide any additional information or context that may be helpful in resolving the issue or implementing the requested feature.

Do we have any insight around the original decision to set this to zero?

Do we have any insight around the original decision to set this to zero?

I believe this was in part due to the fact that certain registries that don't allow pushing image manifests without any layers. Instead of blindly pushing, I think we should check if any zTOCs were created for an index after building and decide to push accordingly. I'll create an issue for this upstream.

The ability to set the min layer size with an environment variable to the lambda would be good as well.

Thanks, we'll be waiting for the upstream bug in go-fuse to be closed before retrying.

authors: bgardner-noggin sparr turan18

repo: aws-ia/cfn-ecr-aws-soci-index-builder


text:
[FEATURE] Allow addon_config variable in aws-for-fluentbit module (similar to fargate-fluentbit module)

Is your feature request related to a problem? Please describe
I need customize aws-for-fluentbit addon with some filters.
Describe the solution you'd like
aws-for-fluentbit
In fluent bit ConfigMap data, add:

fluent-bit.conf
container-log.conf
dataplane-log.conf
host-log.conf
parsers.conf
filters.conf
outputs.conf

https://github.com/aws-ia/terraform-aws-eks-blueprints/blob/7064fbba2fccddbfd3119564204a0f20db479965/modules/kubernetes-addons/fargate-fluentbit/main.tf#L15-L26
Its mandatory create locals named config default_config  and a addon_config variable.
Similar to:
https://github.com/aws-ia/terraform-aws-eks-blueprints/blob/7064fbba2fccddbfd3119564204a0f20db479965/modules/kubernetes-addons/fargate-fluentbit/locals.tf#L6-L41
kubernetes-addons
Create aws_for_fluentbit_addon_config variable.
Describe alternatives you've considered
Install addon without terraform-eks-blueprints module.
Additional context
Add any other context or screenshots about the feature request here.

This is no longer an issue in https://github.com/aws-ia/terraform-aws-eks-blueprints-addons as users can pass any arbitrary configuration through values.yaml.


text:
update the remote target for eks e2e validations

Follow up from the https://github.com/aws-observability/aws-otel-java-instrumentation/pull/757 where EKS E2E test templates were missed out.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 52.62%. Comparing base (09e6487) to head (92c928d).
Report is 243 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@              Coverage Diff              @@
##               main     #758       +/-   ##
=============================================
- Coverage     85.71%   52.62%   -33.09%
- Complexity       19      315      +296
=============================================
  Files             3       40       +37
  Lines            49     1446     +1397
  Branches          5      178      +173
=============================================
+ Hits             42      761      +719
- Misses            3      638      +635
- Partials          4       47       +43

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: codecov-commenter srprash


text:
Bug: Event handler middleware not triggered for not found routes

Expected Behaviour
I think I would expect (global) middleware to be triggered when a not-found route is used.   I have middleware that implements desirable behaviour even when the route is not found.
Current Behaviour
Currently global middleware seems to be bypassed when a not found route is hit.
Code snippet
from aws_lambda_powertools.event_handler import APIGatewayRestResolver, Response
from aws_lambda_powertools.event_handler.middlewares import NextMiddleware

def test_resolve():
    def log_middleware(
        app: APIGatewayRestResolver, next_middleware: NextMiddleware
    ) -> Response:
        print("middleware before")
        return next_middleware(app)

    app = APIGatewayRestResolver()
    app.use(middlewares=[log_middleware])

    @app.get("/listItems")
    def list_items():
        return [{"id": 1}, {"id": 2}]

    @app.not_found
    def not_found(exc):
        return Response(status_code=404)

    # calling this triggers middleware
    app.resolve(
        {
            "path": "/listItems",
            "httpMethod": "GET",
            "requestContext": {},
        },
        {},
    )

    # calling this does not trigger middleware
    app.resolve(
        {
            "path": "/junk",
            "httpMethod": "GET",
            "requestContext": {},
        },
        {},
    )

Possible Solution
The solution I've used currently is to use catch all route handlers to sweep up any unexpected routes, which looks to app like a "valid" route.  This means middleware is triggered.
Another solution would be to trigger global middleware before route resolution.
Steps to Reproduce
I think I've supplied enough context.  The above code snippet should run under pytest -rP Please let me know if more is needed.
Powertools for AWS Lambda (Python) version
latest
AWS Lambda function runtime
3.11
Packaging format used
PyPi
Debugging logs
No response

Hi @tomsimpkins! Thanks for raising this issue and identifying this bug. We should process the global middlewares even when invoking not_found method.
Do you want to submit a PR to fix this? We would love to have your contribution here. Please let us know.
Thanks.

Hi @leandrodamascena thanks for getting back.  I can't dive into this immediately but I've done some reading and think I know how this might be solved.  Please let me know if you agree/disagree.
I'd propose modelling the not found handler itself as middleware.  So in the resolver we would have:
def _not_found(self, method: str):
   def not_found_middleware(app, next_middleware):
       # call handler for not found here and return Response

    middleware_stack = not_found_middleware
    for handler in reversed(self._router_middlewares + [_registered_api_adapter]):
        middleware_stack = MiddlewareFrame(current_middleware=handler, next_middleware=middleware_stack)

    return ResponseBuilder(middleware_stack(self))

The same issue seems to apply with the exception handlers.  I think we could provide the exception handler as a middleware to the Route as the last element of the _route_middlewares:
response=self._to_response(
    route(router_middlewares=self._router_middlewares + [exception_handler_as_middleware], app=self, route_arguments=route_arguments),
),

There's definitely benefit to reusing the logic from Route, so I prefer the answer for the exception handlers to the not found route because of the reuse.  cors for example has to be duplicated in the not found case.  I considered making a NotFoundRoute which implements the overlapping functionality that we'd want so there's symmetry, but I don't know the codebase well enough to make that change.

resurfacing to @leandrodamascena for later this week. I'm gonna tackle as many other issues as possible today.

Assigning to @heitorlessa!

hey @tomsimpkins tks a lot for the patience! I'm gonna start poking at it today - we may not have it ready for this Thursday's release (13th) but we might be able to the next one (27th); we do it bi-weekly now.

read up the context now. My concern with turning them into a middleware is the potential side effects of short-circuits, where either middleware (404 / exception handler) could be skipped and crash. We wrote about "rules" when authoring middleware but it's hard to contain.
Thank you for providing tests, it's not every day that we have good submissions like yours. I'll keep you posted on how the investigation goes

Got it all working along with edge cases, and all 311+ functional tests pass. I'll create additional tests to be extra sure it doesn't break exotic resolvers like Bedrock Agent - if it passes, we can include it in tomorrow's release 🎉🎉

repo: aws-powertools/powertools-lambda-python


text:
(Addon's): addon's with version Auto not deployed

Describe the bug
i have the following Addon's: CoreDNS, Kube-proxy, EBS CSI Driver, and the VPC CNI
it the version of these addon's is set to Auto, they are not deployed to the cluster. when i set them to a specific version they are deployed.
Expected Behavior
when the version is set to auto, it should deploy the latest version.
Current Behavior
not deploying the addon, no errors, synth and deploy is going without error's but when you check the cluster, there are no addon's.
Reproduction Steps
        new blueprints.addons.CoreDnsAddOn(
           'v1.11.1-eksbuild.8'

        ),
        new blueprints.addons.KubeProxyAddOn(
          'v1.30.0-eksbuild.3'

        ),

Possible Solution
not found yet.
Additional Information/Context
No response
CDK CLI Version
2.161.1
EKS Blueprints Version
1.15.1
Node.js Version
v18.18.2
Environment details (OS name and version, etc.)
mac os, and github action ubuntu.
Other information
No response

Accepted, most likely related to lack of version registered for 1.30 EKS version. When running synth, do you mind making sure that you have AWS credentials configured that allow access to the aws eks describe-addon-versions API/CLI?
To detect the version we make the API call, if fails, then we make a static lookup in the internal dictionary.
I will also look into lack of diagnostics that you mentioned, you should get errors in the stdout/stderr.

You can set the log level like and see if you get any descriptive messages:
import { utils } from "@aws-quickstart/eks-blueprints";
import { HelmAddOn } from '@aws-quickstart/eks-blueprints';

    blueprints.HelmAddOn.validateHelmVersions = true;
    blueprints.HelmAddOn.failOnVersionValidation = false;
    utils.logger.settings.minLevel = 3; // info
    utils.userLog.settings.minLevel = 2; // debug

    builder...

if it works, I can enable these by default

repo: aws-quickstart/cdk-eks-blueprints


text:
Cleanup and new location data

Add missing license headers, remove unused files and add new location data.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/do-e2e-tests

authors: SaschaJanssen tbulding


text:
CE pipeline migration

Tested in my account: https://travis-ci.com/xabxx/kinesisvideo-ros1/builds/101350834

Codecov Report

:exclamation: No coverage uploaded for pull request base (release-v1@3b963a4). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             release-v1      #14   +/-   ##
=============================================
  Coverage              ?   76.81%
=============================================
  Files                 ?        6
  Lines                 ?      522
  Branches              ?        0
=============================================
  Hits                  ?      401
  Misses                ?      121
  Partials              ?        0

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3b963a4...353ab37. Read the comment docs.

authors: codecov-io xabxx


text:
Feature Request: Add tags to alarms

It would be great if there is be a kind of auto tagging for the auto-generated alarms, e..g.

copy the tags of the corresponding EC2 instance to the alarm or
stick tags to the alarms using a lambda hook which can be populated by the user

Hello knizami,
Greetings of the day!
am Looking for this code. Is there any Update on this


text:
Error "Unknown options: AutoImportPolicy=DELETED], AutoImportPolicy=CHANGED" while creating AWS FSx create-data-repository-association

I am getting error while adding auto-import-policy when creating AWS FSx create-data-repository-association
FSX Lustre config is:
Storage type: SSD
Deployment type: Persistent 2
Lustre version: 2.12
Success: The below command is successful
aws --region region_name fsx create-data-repository-association --file-system-id fs-xxxxxxxxxxx --batch-import-meta-data-on-create --file-system-path /ns1/ --data-repository-path s3://s3_bucket_path --s3 AutoImportPolicy={Events=[NEW]},AutoExportPolicy={Events=[NEW]}
Error: throwing error when taking multiple options in the list of the AutoImportPolicy
aws --region region_name fsx create-data-repository-association --file-system-id fs-xxxxxxxxx --batch-import-meta-data-on-create --file-system-path /ns1/ --data-repository-path s3://s3_bucket_path --s3 AutoImportPolicy={Events=[NEW,CHANGED,DELETED]}
usage: aws [options]   [ ...] [parameters]
To see help text, you can run:
aws help
aws  help
aws   help
Unknown options: AutoImportPolicy=DELETED], AutoImportPolicy=CHANGED
I tried the below options but none of them are successful
--s3 AutoImportPolicy={Events=['NEW','CHANGED','DELETED']}
--s3 AutoImportPolicy={Events=["NEW","CHANGED","DELETED"]}
--s3 AutoImportPolicy={Events=[NEW|CHANGED|DELETED]}
--s3 AutoImportPolicy={Events=[NEW_CHANGED_DELETED]}
but none of the above options worked
Expecting: I am expecting to create the data-repository-association whose AutoImportPolicy should be New,Changed & Deleted

Hello Team any update on the above issue ?

The issue is fixed by
aws --region ${AWS_REGION} fsx create-data-repository-association
--batch-import-meta-data-on-create
--file-system-id ${fsx_id}
--file-system-path /ns1/
--data-repository-path ${s3_dra}
--s3 "AutoImportPolicy={Events=[NEW,CHANGED,DELETED]},AutoExportPolicy={Events=[NEW,CHANGED,DELETED]}"

repo: aws-samples/amazon-fsx-tutorial

license: MIT


text:
Remove instructions for public read access to S3 buckets

We should remove public s3 read access instructions for S3 bucket.
--create Amazon S3 bucket with public read access
aws s3api create-bucket --bucket  --acl public-read --region  --create-bucket-configuration LocationConstraint=
--
This should be done using Cloudfront distribution with  policy to restrict access to the CloudFrontOriginAccessIdentity

Noting which project this is related to here:
https://github.com/aws-samples/amazon-neptune-samples/blob/master/gremlin/visjs-neptune/README.md
Will follow up with the author to address.

authors: triggan varunrao

repo: aws-samples/amazon-neptune-samples


text:
project_id is not accepted in get_pipeline

Issue #, if available:
None. Here describes the issue:
As defined in get_pipeline() in pipeline.py, get_pipeline cannot receive argument project_id, but codebuild pass this argument based on this codebuild-buildspec.yml, which causes the following  error:
[Container] 2022/11/08 18:03:30 Running command run-pipeline --module-name pipelines.customer_churn.pipeline \
  --role-arn $SAGEMAKER_PIPELINE_ROLE_ARN \
  --tags "[{\"Key\":\"sagemaker:project-name\", \"Value\":\"${SAGEMAKER_PROJECT_NAME}\"}, {\"Key\":\"sagemaker:project-id\", \"Value\":\"${SAGEMAKER_PROJECT_ID}\"}]" \
  --kwargs "{\"region\":\"${AWS_REGION}\",\"role\":\"${SAGEMAKER_PIPELINE_ROLE_ARN}\",\"default_bucket\":\"${ARTIFACT_BUCKET}\",\"pipeline_name\":\"${SAGEMAKER_PROJECT_NAME_ID}\",\"model_package_group_name\":\"${SAGEMAKER_PROJECT_NAME_ID}\",\"base_job_prefix\":\"${SAGEMAKER_PROJECT_NAME_ID}\",\"project_id\":\"${SAGEMAKER_PROJECT_ID}\"}"

Exception: get_pipeline() got an unexpected keyword argument 'project_id' Traceback (most recent call last):
  File "/root/.pyenv/versions/3.8.13/lib/python3.8/site-packages/pipelines/run_pipeline.py", line 77, in main
    pipeline = get_pipeline_driver(args.module_name, args.kwargs)
  File "/root/.pyenv/versions/3.8.13/lib/python3.8/site-packages/pipelines/_utils.py", line 33, in get_pipeline_driver
    return _imports.get_pipeline(**kwargs)
TypeError: get_pipeline() got an unexpected keyword argument 'project_id'

Description of changes:
Just removing project_id from codebuild-buildspec.yml
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Withdraw my PR as my configuration was not correct.
The MLOps template that I used was MLOps template for image building, model building, and model deployment, which was different from MLOps template for model building, training, and deployment suggested in Lab 6.


text:
In python workshop, there is a problem.

:bug: Bug Report
What is the problem?

In "Writing Constructs" part, there is "Use the hit counter" section.
I typed "from hitcounter import HitCounter" in my cdkworkshop_stack.py, but when I did sdk deploy command. It couldn't find hitcounter module. So I changed from .hitcounter import Hitcounter and It was fixed. I think you need to check if it's okay or not.
Reproduction Steps

Verbose Log

Environment

CDK CLI Version:  1.39.0
Section:  visual code
Browser:  Chrome
Language:  Python

Other information

I ran into this issue today in the Python CDK workshop when adding the hitcounter. Currently on line 8 in the cdk_workshop_stack.py file in the tutorial it states: "from .hitcounter import HitCounter" this should be without the . (dot)
like this "from hitcounter import HitCounter"

repo: aws-samples/aws-cdk-intro-workshop


text:
Testing Construct Broken Link

:bug: Bug Report
What is the problem?
Within the workshop here there is a link to "read the docs" the link is stale.
please read the docs here
Reproduction Steps
Click link in description... no worky.
Verbose Log
We don't need to see these droids
Environment

Section: TESTING CONSTRUCTS
Browser: All
Language: TypeScript

Other information
Not needed

This should be the proper link: https://github.com/aws/aws-cdk/blob/master/packages/%40aws-cdk/assert-internal/README.md
Would you be willing to submit a pr for this @shdobxr? Ping me to let me know

authors: peterwoodworth shdobxr


text:
Use local firewall with passthrough

Are there any examples of using firewalls (nftables) with gwX interfaces?
For example, traffic incoming on gwi-X, does some nft actions and then mirrored to gwo-X
tc qdisc add dev $2 ingress
tc filter add dev $2 parent ffff: protocol all prio 2 u32 match u32 0 0 flowid 1:1 action mirred egress mirror dev $3

I guess that traffic mirrored before firewalling in this case. It will be greate to have some examples.
Thanks.

@sever-sever I was interested in this as well... did you find a solution ?  This has to be possible since Vyos, being linux based, just added support for GWLB.

@sever-sever I was interested in this as well... did you find a solution ? This has to be possible since Vyos, being linux based, just added support for GWLB.

@kxs-jnadeau, I didn't get any examples.
I hope the examples will be extended or someone can point me in the right direction.

authors: kxs-jnadeau sever-sever


text:
[BUG] Token validation in middleware

In dependencies.py we are raising error while token verification fails but in the middlware in no where it is being catched?

Please do not ignore the template and provide details. thank you

@statefb Added more details

authors: cyruxOP statefb

repo: aws-samples/bedrock-claude-chat


text:
feat: Update nri-bundle to version 5.0.66

Update nri-bundle to version 5.0.66

@Pjv93 @mikemcd3912 Please review and merge this

repo: aws-samples/eks-anywhere-addons


text:
Fix for CVE-2024-47554 - update to commons-io 2.14.0

Fix for CVE-2024-47554 - update to commons-io 2.14.0
Issue #, if available:
CVE-2024-47554
Description of changes:
update to commons-io 2.14.0

Fix for https://github.com/advisories/GHSA-78wr-2p64-hpwj - update to commons-io 2.14.0

Fix for CVE-2024-47554 - update to commons-io 2.14.0

repo: aws-samples/pix-proxy-samples


text:
[feat] Tighten Instance Security Group

The InstanceSecurityGroup currently allows egress access to anywhere over HTTPS.
This is required because:

versions less than v1.4.0 nitro-enclaves-acm require accessing https://iam.amazonaws.com:443 to resolve the IAM role. Once version v1.4.0 is available in the yum repositories, we could consider fix this
access to S3 to download yum packages through the S3 VPC Gateway endpoint

To resolve this, we need to wait until v1.4.0 is available in the yum repositories and change the S3 VPC Gateway endpoint to a S3 VPC Interface endpoint.

Amazon Linux 2023 version 2023.6.20241010 includes ACM v1.4.0 - https://docs.aws.amazon.com/linux/al2023/release-notes/relnotes-2023.6.20241010.html#amis-2023.6.20241010.repository


text:
Set S3 ObjectOwnership to ObjectWriter for AccessLoggingBucket

Closes #236
Starting in April 2023, S3 changed the default ownership settings for new S3 buckets:
https://aws.amazon.com/blogs/aws/heads-up-amazon-s3-security-changes-are-coming-in-april-of-2023/
By not specifying ObjectWriter as the desired ownership the bucket defaulted to the new BucketOwnerEnforced. This caused the CF template to fail creating the S3 bucket when it tries to apply ACL rules on the bucket. The template would fail with this error
Bucket cannot have ACLs set with ObjectOwnership's BucketOwnerEnforced setting

By specifying that the bucket should be created with ObjectWriter (ACL enabled) the CF template is then able to apply it's ACL rules and successfully deploy.
As of this commit (April 18, 2023) this cf template fails to deploy in us-east-2. I'm guessing this is the first, or one of the first, regions where these new defaults are being rolled out to.

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

@aijunpeng @WillAWS Sorry to ping folks. I see you two worked in this repo most recently so just want to get this on your radar. Not sure how often y'all check PR's. This will become a problem as the S3 changes roll out to more regions.
I realize it might even be worth looking into if setting ownership to ObjectWritier and writing up an ACL is even necessary. Maybe the BucketOwnerEnforced setting is fine and what should actually happen is the custom ACL rules are removed?

Use patched version:
release/v3.2.5

Niceee, thank you!

authors: WillAWS taylorsilva


text:
feature: add control-sqrt-not gate

Adding this gate makes things like CHSH circuits much more manageable off the bat.
Issue #, if available: - https://github.com/aws/amazon-braket-sdk-python/pull/297
Description of changes:
This edit to the schemas repo based on changes proposed in PR #297 on the sdk repo https://github.com/aws/amazon-braket-sdk-python/pull/297
Testing done:
Added unit test. More information available at: https://github.com/aws/amazon-braket-sdk-python/pull/297
Merge Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.
General

[x] I have read the CONTRIBUTING doc
[x] I used the commit message format described in CONTRIBUTING
[x] I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

[x] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[x] I have checked that my tests are not configured for a specific region or account (if appropriate)

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

Fix: I added a basic test in line with the CY and CZ gates - there's nothing I can think for an extra test right now.

Hello! Apologies, tracked down what I had forgotten to do and pushed a fix. All tests now succeed locally for me with tox (linters, docs, and unit-tests). Many thanks for your patience!

Done :) Would you like me to do the same for thetox.ini file in amazon-braket-sdk-python as well?

repo: aws/amazon-braket-schemas-python


text:
Iframe in the same window

Hello there!
I've embedded ACS into React and I have question how can I insert this url (https://{alias}.awsapps.com/connect/ccp) as an Iframe in the same window?
Because when I do it, I have tons of errors in the console.

You have to white list the URL you are loading the iframe from in the Connect admin panel.  Also, I don't believe you can have ports on the white listed URL so you will have to run your dev server on a standard port or use Fiddler to redirect your URL request.

Everything is okey there and it automatically opens a new window where I can login, but I want to have this window in my iFrame.

Try using HTTPS.

Oh wait, sorry.  I replied from the e mail and didn't see the second half of your comment regarding the login window.  There is no way, right now, to have that login come in am Iframe.  I think there is OAUTH authentication planned for the future, but we are stuck with the current login flow for now.

Okey. Thank you.

repo: aws/amazon-connect-streams


text:
agent.mute silently fails after softphone is refreshed on voice interaction

This behavior is seen both with the Connect CCP softphone and using the amazon connect streams api.
If a voice interaction is active and the window/frame that the softphone or a softphone using the API lives in is refreshed the mute/unmute API calls silently fail for the remainder of the interaction.

Please refer the Issue
Unfortunately I don't have any details about what exactly we will do here (or when it'll happen).

For now this behavior is expected as it's mentioned here https://github.com/aws/amazon-connect-streams/issues/33.

authors: amollerson jagadeeshaby


text:
Update Docker to 20.10.20 for all images al1, al2, al2arm, al2gpu, al2inf

Summary

Updates the version of Docker Engine installed on all image flavors to 20.10.20.
Implementation details

Updated docker_version variable in Packer variable files and generate-release-vars.sh script.
Testing

New tests cover the changes:
no
Description for the changelog

Enhancement - Update Docker to 20.10.20 for all images al1, al2, al2arm, al2gpu, al2inf #87
Licensing
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This change is needed to address multiple CVEs in Go with a high CVSS base score.

hi @dude0001, the docker version installed in our AMIs comes from the Amazon Linux repos, so we're not able to update to whatever version we like that docker has released.
FWIW, the Amazon Linux docker version also is not identical to docker's version. As it is with most operating systems, Amazon Linux builds their own version of docker. AL's docker 20.10.17, for example, was built with Go 1.19.1 in order to address a CVE, see https://alas.aws.amazon.com/AL2/ALASDOCKER-2022-021.html

repo: aws/amazon-ecs-ami


text:
Loading AppConfig feature flags into strong-type options

Describe the issue
So I've defined a feature flag configuration profile in AppConfig with two booleans e.g.

Run = true
Jump = false

For the ASP.NET 6 WebApplicationBuilder.Configuration object, it gets extended with AppConfig.
var builder = WebApplication.CreateBuilder(args);
builder.Configuration.AddAppConfig("appid", "envid", "configprofileid", TimeSpan.FromSeconds(30));

// This will not work.
// builder.Services.Configure<FeatureFlags>(builder.Configuration.GetSection(nameof(FeatureFlags)));

But how to read in all those feature flags into a consolidated options object? There's no real configuration section tied to those, is there?
public class FeatureFlags
{
	public bool Run { get; set; }
	public bool Jump { get; set; }
}

public class AppConfigModel : PageModel
{
	internal FeatureFlags FeatureFlags{ get; private set; }

	public AppConfigModel(IOptionsSnapshot<FeatureFlags> flagOptions)
	{
		this.FeatureFlags= flagOptions.Value;
	}

	public void OnGet()
	{
	}
}

Links
https://github.com/aws/aws-dotnet-extensions-configuration

@icelava Thanks for opening the issue. Could you please share screenshot(s) on what your AppConfig in AWS Console looks like and how you have defined a feature flag configuration profile in AppConfig with two booleans e.g.

Run = true
Jump = false

Thanks,
Ashish

It's just a feature flag config profile with flags defined.

It's just a feature flag config profile with flags defined.

@icelava Just for reference, debugged using the clone of the repository and defining the flags similar to your screenshot. The configuration is returned as a dictionary like below:

So supposed to be configuring for a Dictionary<sting, bool> object instead? But what's the configuration section name?
builder.Services.Configure<Dictionary<string, bool>>(builder.Configuration.GetSection("WHATCONFIGSECTIONNAME"));
If I place in the name of the configuration profile as config section name "FeatureFlags", all the page gets on construction is just an IOptionsSnapshot<Dictionary<string, bool>> of an empty dictionary.

Ok now that have some spare time to revisit this issue, I found that given the nature of the config parameter names returned from AppConfig to ASP.NET, it's not possible to consolidate all feature flags in one configuration profile into the same .NET strong-typed config object.
The class has to be written for each individual feature flag.
public class FeatureFlagRun
{
	public bool Enabled { get; set; }
}

Then the configuration builder draws in the feature flag as the "Run" config section alone.
builder.Services.Configure<FeatureFlagRun>(builder.Configuration.GetSection("Run"));
Given that this has to be done repeatedly for each feature flag, think it's just way more convenient to use free-form JSON.

authors: ashishdhingra icelava

repo: aws/aws-dotnet-extensions-configuration


text:
Importing Numpy and OpenCV in enclave

Is there a compatible issue in enclave instance with python packages such as cv2 and NumPy? When I import those libraries the instance just hangs. No error output or termination, just an OpenBLAS warning about L2 cache.
Just some example code of the import
#amazonlinux still have the import issue
#python:3.7 libs importing crush
FROM amazonlinux

WORKDIR /app
#py 3.7
RUN yum install python3 zip -y

ENV VIRTIAL_ENV=/opt/venv
RUN python3 -m venv $VIRTIAL_ENV
ENV PATH="$VIRTIAL_ENV/bin:$PATH"

#3 libs needed for cv2 import
RUN yum install libSM-1.2.2-2.amzn2.x86_64 -y
RUN yum install libXrender-0.9.10-1.amzn2.x86_64 -y
RUN yum install libXext-1.3.3-3.amzn2.x86_64 -y

COPY requirements.txt ./
RUN pip3 install --no-cache-dir -r /app/requirements.txt

#shell script testing
COPY dockerfile_entrypoint.sh ./

COPY test_cv2.py ./

#ENV for shell testing printf loop
ENV HELLO="Hello from enclave side!"
RUN chmod +X dockerfile_entrypoint.sh

#shell script testing
CMD ["/app/dockerfile_entrypoint.sh"]

The shell and py scripts are just an import to show things are working
#!/bin/bash

#shell printf loop test in enclave
# go to work dir and check files
cd /app||return
ls

#cv2 imp issue
python3 test_cv2.py

#use shell loop to keep enclave live to see error message output
count=1
while true;do
  printf "[%4d] $HELLO\n" $count
  echo "$PWD"
  ls
  count=$((count+1))
  sleep 5
done

import cv2

for i in range(10):
    print('testing OpenCV')

There may be that there is not enough entropy in the enclave so it hangs. There are a couple of options shared in https://github.com/aws/aws-nitro-enclaves-sdk-c/issues/41 to solve this.

authors: Foxium andraprs

repo: aws/aws-nitro-enclaves-cli


text:
Fix code formatting

Fix code formatting for #2137
Signed-off-by: chenwany chenwany@amazon.com
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Closed in favor of: https://github.com/aws/aws-parallelcluster/pull/2140

authors: chenwany rexcsn

repo: aws/aws-parallelcluster


text:
[Bug]: The client type is not transformed by codemod

Self-service

[ ] I'd be willing to implement a fix

Describe the bug
The client type is not transformed by codemod
Steps to reproduce
import { StepFunctions } from "aws-sdk";

let client: StepFunctions;
client = new StepFunctions();

Observed behavior
import { StepFunctions } from "aws-sdk";

import { SFN } from "@aws-sdk/client-sfn";

let client: StepFunctions;
client = new SFN();

Expected behavior
import { SFN } from "@aws-sdk/client-sfn";

let client: SFN;
client = new SFN();

Environment
aws-sdk-js-codemod: 1.2.5
- jscodeshift: 0.15.2
- recast: 0.23.4

Additional context
No response

This applies to only the clients whose names are different in v2 and v3.

repo: aws/aws-sdk-js-codemod


text:
Dependency warning: "NU1603: PCLCrypto 1.0.2.15130 depends on Validation (>= 2.0.6 && < 3.0.0) but Validation 2.0.6 was not found."

When fetching AWSSDK.Core, I have the following warning:
NU1603: PCLCrypto 1.0.2.15130 depends on Validation (>= 2.0.6 && < 3.0.0) but Validation 2.0.6 was not found. An approximate best match of Validation 2.0.6.15003 was resolved.
Expected Behavior
No warning
Current Behavior
A lot of warnings popup with this info but it does not prevent the compilation
Possible Solution
Update the version of PCLCrypto dependency.
Your Environment

AWSSDK.Core version used: 3.3.102.18 (but a lot of versions seem affected by this issue)
Service assembly and version used:
Operating System and version: Windows 10
Visual Studio version: Visual Studio 2017
Targeted .NET platform: UWP

Hi @ErwanJes, if you want to remove the warning, you can try manually depending on Validation 2.0.6.  Otherwise, this should go away as we progress in our move from PCL to .NET Standard.

1 year later, same message still happening

authors: ErwanJes klaytaybai nbsoftware

repo: aws/aws-sdk-net


text:
File "", line 1, in  ModuleNotFoundError: No module named 'awswrangler'

Describe the bug
I'm following this tutorial on awswrangler: (https://aws-sdk-pandas.readthedocs.io/en/stable/tutorials/036 - Distributing Calls with Glue Interactive Sessions on Ray.html)
cell 1
!pip install "awswrangler[modin]"

Defaulting to user installation because normal site-packages is not writeable
Collecting awswrangler[modin]
Using cached awswrangler-3.4.1-py3-none-any.whl (396 kB)
Requirement already satisfied: boto3<2.0.0,>=1.20.32 in /home/jupyter-user/.local/lib/python3.9/site-packages (from awswrangler[modin]) (1.28.2)
Requirement already satisfied: botocore<2.0.0,>=1.23.32 in /home/jupyter-user/.local/lib/python3.9/site-packages (from awswrangler[modin]) (1.31.2)
Requirement already satisfied: numpy<2.0,>=1.18 in /home/jupyter-user/.local/lib/python3.9/site-packages (from awswrangler[modin]) (1.25.1)
Requirement already satisfied: packaging<24.0,>=21.1 in /home/jupyter-user/.local/lib/python3.9/site-packages (from awswrangler[modin]) (23.1)
Requirement already satisfied: pandas<3.0.0,>=1.2.0 in /home/jupyter-user/.local/lib/python3.9/site-packages (from awswrangler[modin]) (2.0.0)
Requirement already satisfied: pyarrow>=7.0.0 in /home/jupyter-user/.local/lib/python3.9/site-packages (from awswrangler[modin]) (13.0.0)
Requirement already satisfied: typing-extensions<5.0.0,>=4.4.0 in /home/jupyter-user/.local/lib/python3.9/site-packages (from awswrangler[modin]) (4.7.1)
Requirement already satisfied: modin<0.24.0,>=0.23.0 in /home/jupyter-user/.local/lib/python3.9/site-packages (from awswrangler[modin]) (0.23.1)
Requirement already satisfied: jmespath<2.0.0,>=0.7.1 in /home/jupyter-user/.local/lib/python3.9/site-packages (from boto3<2.0.0,>=1.20.32->awswrangler[modin]) (1.0.1)
Requirement already satisfied: s3transfer<0.7.0,>=0.6.0 in /home/jupyter-user/.local/lib/python3.9/site-packages (from boto3<2.0.0,>=1.20.32->awswrangler[modin]) (0.6.1)
Requirement already satisfied: python-dateutil<3.0.0,>=2.1 in /home/jupyter-user/.local/lib/python3.9/site-packages (from botocore<2.0.0,>=1.23.32->awswrangler[modin]) (2.8.2)
Requirement already satisfied: urllib3<1.27,>=1.25.4 in /home/jupyter-user/.local/lib/python3.9/site-packages (from botocore<2.0.0,>=1.23.32->awswrangler[modin]) (1.26.16)
Requirement already satisfied: fsspec>=2021.07.0 in /home/jupyter-user/.local/lib/python3.9/site-packages (from modin<0.24.0,>=0.23.0->awswrangler[modin]) (2023.10.0)
Requirement already satisfied: psutil>=5.8.0 in /home/jupyter-user/.local/lib/python3.9/site-packages (from modin<0.24.0,>=0.23.0->awswrangler[modin]) (5.9.5)
Requirement already satisfied: pytz>=2020.1 in /home/jupyter-user/.local/lib/python3.9/site-packages (from pandas<3.0.0,>=1.2.0->awswrangler[modin]) (2023.3)
Requirement already satisfied: tzdata>=2022.1 in /home/jupyter-user/.local/lib/python3.9/site-packages (from pandas<3.0.0,>=1.2.0->awswrangler[modin]) (2023.3)
Requirement already satisfied: six>=1.5 in /home/jupyter-user/.local/lib/python3.9/site-packages (from python-dateutil<3.0.0,>=2.1->botocore<2.0.0,>=1.23.32->awswrangler[modin]) (1.16.0)
Installing collected packages: awswrangler
Successfully installed awswrangler-3.4.1
[notice] A new release of pip is available: 23.1.2 -> 23.3.1
[notice] To update, run: pip install --upgrade pip
cell2
import awswrangler as wr
File "", line 1, in
ModuleNotFoundError: No module named 'awswrangler'
How to Reproduce
Just followed the tutorial at https://aws-sdk-pandas.readthedocs.io/en/stable/tutorials/036 - Distributing Calls with Glue Interactive Sessions on Ray.html
Here is the output of me doing a  !python -m pip list
Package                             Version

aiofiles                            22.1.0
aiohttp                             3.8.6
aiohttp-cors                        0.7.0
aiosignal                           1.3.1
aiosqlite                           0.19.0
amazon-codewhisperer-jupyterlab-ext 1.0.3
anyio                               3.7.1
argon2-cffi                         21.3.0
argon2-cffi-bindings                21.2.0
arrow                               1.2.3
asn1crypto                          1.5.1
asttokens                           2.2.1
async-timeout                       4.0.3
attrs                               23.1.0
autovizwidget                       0.20.5
aws-glue-sessions                   0.38.1
awscli                              1.29.2
awswrangler                         3.4.1
Babel                               2.12.1
backcall                            0.2.0
beautifulsoup4                      4.12.2
bleach                              6.0.0
blessed                             1.20.0
boto3                               1.28.2
botocore                            1.31.2
cachetools                          5.3.2
certifi                             2023.5.7
cffi                                1.15.1
charset-normalizer                  3.2.0
click                               8.1.4
colorama                            0.4.4
colorful                            0.5.5
comm                                0.1.3
debugpy                             1.6.7
decorator                           5.1.1
defusedxml                          0.7.1
distlib                             0.3.7
docutils                            0.16
exceptiongroup                      1.1.2
executing                           1.2.0
fastjsonschema                      2.17.1
filelock                            3.12.4
fqdn                                1.5.1
frozenlist                          1.4.0
fsspec                              2023.10.0
google-api-core                     2.12.0
google-auth                         2.23.3
googleapis-common-protos            1.61.0
gpustat                             1.1.1
grpcio                              1.59.0
hdijupyterutils                     0.20.5
idna                                3.4
importlib-metadata                  6.8.0
ipykernel                           6.24.0
ipython                             8.14.0
ipython-genutils                    0.2.0
ipywidgets                          8.0.7
isoduration                         20.11.0
jedi                                0.18.2
Jinja2                              3.1.2
jmespath                            1.0.1
json5                               0.9.14
jsonpointer                         2.4
jsonschema                          4.18.2
jsonschema-specifications           2023.6.1
jupyter                             1.0.0
jupyter_client                      8.3.0
jupyter-console                     6.6.3
jupyter_core                        5.3.1
jupyter-events                      0.6.3
jupyter-lsp                         2.2.0
jupyter_server                      2.7.0
jupyter_server_fileid               0.9.0
jupyter_server_terminals            0.4.4
jupyter_server_ydoc                 0.8.0
jupyter-ydoc                        0.2.4
jupyterlab                          3.6.4
jupyterlab-lsp                      4.0.0
jupyterlab-pygments                 0.2.2
jupyterlab_server                   2.23.0
jupyterlab-widgets                  3.0.8
lxml                                4.9.3
markdown-it-py                      3.0.0
MarkupSafe                          2.1.3
matplotlib-inline                   0.1.6
mdurl                               0.1.2
mistune                             3.0.1
modin                               0.23.1
msgpack                             1.0.7
multidict                           6.0.4
nbclassic                           1.0.0
nbclient                            0.8.0
nbconvert                           7.6.0
nbformat                            5.9.1
nest-asyncio                        1.5.6
nose                                1.3.7
notebook                            6.5.4
notebook_shim                       0.2.3
numpy                               1.25.1
nvidia-ml-py                        12.535.108
opencensus                          0.11.3
opencensus-context                  0.1.3
overrides                           7.3.1
packaging                           23.1
pandas                              2.0.0
pandocfilters                       1.5.0
parso                               0.8.3
pexpect                             4.8.0
pickleshare                         0.7.5
pip                                 23.1.2
platformdirs                        3.8.1
plotly                              5.15.0
prometheus-client                   0.17.1
prompt-toolkit                      3.0.39
protobuf                            4.24.4
psutil                              5.9.5
ptyprocess                          0.7.0
pure-eval                           0.2.2
py-spy                              0.3.14
pyarrow                             13.0.0
pyasn1                              0.5.0
pyasn1-modules                      0.3.0
pycparser                           2.21
pydantic                            1.10.13
Pygments                            2.15.1
pykerberos                          1.2.4
python-dateutil                     2.8.2
python-json-logger                  2.0.7
pytz                                2023.3
PyYAML                              5.4.1
pyzmq                               25.1.0
qtconsole                           5.4.3
QtPy                                2.3.1
ray                                 2.6.3
redshift-connector                  2.0.915
referencing                         0.29.1
requests                            2.31.0
rfc3339-validator                   0.1.4
rfc3986-validator                   0.1.1
rich                                13.4.2
rpds-py                             0.8.10
rsa                                 4.7.2
s3transfer                          0.6.1
scramp                              1.4.4
Send2Trash                          1.8.2
setuptools                          58.1.0
six                                 1.16.0
smart-open                          6.4.0
sniffio                             1.3.0
soupsieve                           2.4.1
stack-data                          0.6.2
tenacity                            8.2.2
terminado                           0.17.1
tinycss2                            1.2.1
tomli                               2.0.1
tornado                             6.3.2
traitlets                           5.9.0
typing_extensions                   4.7.1
tzdata                              2023.3
uri-template                        1.3.0
urllib3                             1.26.16
virtualenv                          20.21.0
wcwidth                             0.2.6
webcolors                           1.13
webencodings                        0.5.1
websocket-client                    1.6.1
widgetsnbextension                  4.0.8
y-py                                0.5.9
yarl                                1.9.2
ypy-websocket                       0.8.2
zipp                                3.16.1
[notice] A new release of pip is available: 23.1.2 -> 23.3.1
[notice] To update, run: pip install --upgrade pip
Expected behavior
I expected to be able to import the awswrangler library
Your project
No response
Screenshots

OS
Windows 11
Python version
3.9.9
AWS SDK for pandas version
3.4.1
Additional context
Running on Windows 11 Home version 22H2

I also tried using the additional_python_modules ['awswrangler'] magic, then import awswrangler produced this output
uthenticating with environment variables and user-defined glue_role_arn: arn:aws:iam::696353118745:role/awsglueservicerole
Trying to create a Glue session for the kernel.
Worker Type: Z.2X
Number of Workers: 5
Session ID: fa980785-a2c9-4b43-b704-bbaf2c485e4a
Job Type: glueray
Applying the following default arguments:
--glue_kernel_version 0.38.1
--enable-glue-datacatalog true
--auto-scaling-ray-min-workers 1
--additional-python-modules 'awswrangler'
Waiting for session fa980785-a2c9-4b43-b704-bbaf2c485e4a to get into ready status...
Session fa980785-a2c9-4b43-b704-bbaf2c485e4a has been created.
File "", line 19, in
File "", line 12, in
File "/opt/amazon/workload-runtime/Ray2.4/python3.9/lib/python3.9/site-packages/ray/_private/client_mode_hook.py", line 105, in wrapper
return func(*args, **kwargs)
File "/opt/amazon/workload-runtime/Ray2.4/python3.9/lib/python3.9/site-packages/ray/_private/worker.py", line 2523, in get
raise value
ray.exceptions.RuntimeEnvSetupError: Failed to set up runtime environment.
Traceback (most recent call last):
File "/opt/amazon/workload-runtime/Ray2.4/python3.9/lib/python3.9/site-packages/ray/dashboard/modules/runtime_env/runtime_env_agent.py", line 357, in _create_runtime_env_with_retry
runtime_env_context = await asyncio.wait_for(
File "/opt/amazon/workload-runtime/Ray2.4/python3.9/lib/python3.9/asyncio/tasks.py", line 479, in wait_for
return fut.result()
File "/opt/amazon/workload-runtime/Ray2.4/python3.9/lib/python3.9/site-packages/ray/dashboard/modules/runtime_env/runtime_env_agent.py", line 312, in _setup_runtime_env
await create_for_plugin_if_needed(
File "/opt/amazon/workload-runtime/Ray2.4/python3.9/lib/python3.9/site-packages/ray/_private/runtime_env/plugin.py", line 252, in create_for_plugin_if_needed
size_bytes = await plugin.create(uri, runtime_env, context, logger=logger)
File "/opt/amazon/workload-runtime/Ray2.4/python3.9/lib/python3.9/site-packages/ray/_private/runtime_env/pip.py", line 473, in create
return await task
File "/opt/amazon/workload-runtime/Ray2.4/python3.9/lib/python3.9/site-packages/ray/_private/runtime_env/pip.py", line 455, in _create_for_hash
await PipProcessor(
File "/opt/amazon/workload-runtime/Ray2.4/python3.9/lib/python3.9/site-packages/ray/_private/runtime_env/pip.py", line 361, in _run
await self._install_pip_packages(
File "/opt/amazon/workload-runtime/Ray2.4/python3.9/lib/python3.9/site-packages/ray/_private/runtime_env/pip.py", line 337, in _install_pip_packages
await check_output_cmd(pip_install_cmd, logger=logger, cwd=cwd, env=pip_env)
File "/opt/amazon/workload-runtime/Ray2.4/python3.9/lib/python3.9/site-packages/ray/_private/runtime_env/utils.py", line 101, in check_output_cmd
raise SubprocessCalledProcessError(
ray._private.runtime_env.utils.SubprocessCalledProcessError: Run cmd[9] failed with the following details.
Command '['/tmp/ray/session_2023-10-27_07-49-57_590470_1678/runtime_resources/pip/3df5f0bf1a8ea11d08aea8f90e4c748f7e1ae468/virtualenv/bin/python', '-m', 'pip', 'install', '--disable-pip-version-check', '--no-cache-dir', '-r', '/tmp/ray/session_2023-10-27_07-49-57_590470_1678/runtime_resources/pip/3df5f0bf1a8ea11d08aea8f90e4c748f7e1ae468/requirements.txt']' returned non-zero exit status 1.
Last 50 lines of stdout:
ERROR: Invalid requirement: "'awswrangler'" (from line 1 of /tmp/ray/session_2023-10-27_07-49-57_590470_1678/runtime_resources/pip/3df5f0bf1a8ea11d08aea8f90e4c748f7e1ae468/requirements.txt)
2023-10-27 07:50:03,187	INFO worker.py:1432 -- Connecting to existing Ray cluster at address: 2600:1f10:4f79:8b20:31f8:648:54b9:cfc5:6379...
2023-10-27 07:50:03,196	INFO worker.py:1616 -- Connected to Ray cluster. View the dashboard at 127.0.0.1:8265

Thanks for raising this @taupirho. It looks like the installation of additional modules in AWS Glue interactive sessions has somehow changed and requires using %additional_python_modules. I have updated the tutorial to reflect that.

authors: jaidisido taupirho

repo: aws/aws-sdk-pandas


text:
tests: Replace load tests bucket with SSM parameter

Feature or Bugfix

Enhancement

Detail

Replace load tests bucket with SSM parameter

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

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 46422448588e5bd250b11f03bdc33f55053833ca
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubStandardCodeBuild8C06-llutOAimTATs
Commit ID: 46422448588e5bd250b11f03bdc33f55053833ca
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-ATYtnXPE7MOa
Commit ID: 46422448588e5bd250b11f03bdc33f55053833ca
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

authors: jaidisido malachi-constant


text:
Bump log4j to v2.15.0

Although this is a test dependency, we should still bump up the version to be free from the identified security vulnerability.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #112 (d7fb78e) into main (abbdc32) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main     #112   +/-   ##
=========================================
  Coverage     65.10%   65.10%
  Complexity      193      193
=========================================
  Files            17       17
  Lines           854      854
  Branches        132      132
=========================================
  Hits            556      556
  Misses          229      229
  Partials         69       69

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update abbdc32...d7fb78e. Read the comment docs.

repo: aws/aws-xray-java-agent


text:
Artifacts on docs show v0.12.1 to use 1-23-eks-22 but should be 1-23-eks-7

What happened:
Using eksa v0.12.1
According to the docs the EKS-D Release for 1.23 is “eksdRelease:kubernetes-1-23-eks-22” but fails because the tag should have actually been “eksdRelease:kubernetes-1-23-eks-7” instead
https://anywhere.eks.amazonaws.com/docs/reference/artifacts/
Validation failed     {"validation": "vsphere Provider setup is valid", "error": "template /********/Templates/bottlerocket-v1.23.22-eks-d-1-23-22 is missing tag eksdRelease:kubernetes-1-23-eks-7", "remediation": ""}

Environment:

EKS Anywhere Release: v0.12.1
EKS Distro Release: 0.118.0

hi Ron, thank you for bringing this up to our attention, we will update the docs.

Once this PR merges, the docs will be updated.

Hey @ronpichardo , this is resolved from our side. Please let me know if you are good to go and I can close this issue out.

Doc update is merged and public docs reflect this

authors: danbudris mitalipaygude ronpichardo

repo: aws/eks-anywhere


text:
Remove provider factory

The provider factory created a level of indirection that forced
dependencies of all providers to be constructed irrespective of what
provider was being used.

/cc @g-gaston @panktishah26 @abhinavmpandey08 @pokearu @jacobweinstock @gwesterfieldjr

/approve

/lgtm

/approve


text:
AWS IAM Auth lifecycle controller support

Description of changes:
Adding support for reconciling awsiamconfig identity provider. The changes adds steps in the cluster controller reconcile flow

We create a CA secret on the management cluster before the controlplane comes up for the workload cluster.
Once the new workload cluster is ready we apply the aws-iam-authenticator manifest.
If changes are made to mutable fields on the awsiamconfig object, the controller reconciles and does necessary updates.

Testing:
kubectl apply -f cluster-with-iam.yaml

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
/woof

authors: g-gaston pokearu


text:
Bumped production release number for 1.23-24

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

/lgtm

authors: kschumy rcrozean

repo: aws/eks-distro


text:
chore: Reason in scheduling in terms of nodes

Fixes #
Description
How was this change tested?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build 3644451305

51 of 55 (92.73%)  changed or added relevant lines in 12 files are covered.
9 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.1%) to 75.978%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/controllers/deprovisioning/controller.go
2
3
66.67%

pkg/controllers/deprovisioning/consolidation.go
1
4
25.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/controllers/deprovisioning/controller.go
2
70.39%

pkg/controllers/provisioning/scheduling/preferences.go
7
86.67%

Totals

Change from base Build 3636710075:
-0.1%

Covered Lines:
5494

Relevant Lines:
7231

💛  - Coveralls

authors: coveralls jonathan-innis

repo: aws/karpenter-core


text:
chore: Bump karpenter for v0.31.4

Fixes #N/A
Description

Bump Karpenter for v0.31.4

How was this change tested?

N/A

Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

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

Pull Request Test Coverage Report for Build 7847656016

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.05%) to 84.167%

Totals

Change from base Build 7838153023:
-0.05%

Covered Lines:
6868

Relevant Lines:
8160

💛  - Coveralls

authors: coveralls engedaam

repo: aws/karpenter-provider-aws


text:
[WIP] fix regex for version string

1. Issue, if available:
version warning shows entire path for old verions
2. Description of changes:
revise regex
3. How was this change tested?
4. Does this change impact docs?

[x] Yes, PR includes docs updates
[ ] Yes, issue opened: link to issue
[ ] No

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

ok, now it has been tested and works! 🎉

repo: aws/karpenter


text:
Peer Connection ID Management

From https://tools.ietf.org/id/draft-ietf-quic-transport-32.html#name-consuming-and-retiring-conn:
Receiving Connection IDs from the peer:

[x] Create a peer connection ID manager #342
[x] Track the number of RETIRE_CONNECTION_ID frames sent but not acknowledged #342

Sending RETIRE_CONNECTION_ID frames:

[x] Send a RETIRE_CONNECTION_ID frame immediately after the handshake. Since we cannot actually retire a connection ID until we've received a new connection ID, this should be implemented as transitioning to a state of wanting to retire a connection ID  #342
[x] Only retire connection IDs if there is an unused active connection ID available to use #342
[x] Send RETIRE_CONNECTION_ID when a NEW_CONNECTION_ID is received with an increased Retire Prior To field #342
[ ] Endpoints SHOULD retire connection IDs when they are no longer actively using either the local or destination
address for which the connection ID was used.

Receiving NEW_CONNECTION_ID frames:

[x] Close the connection if the peer sent too many connection IDS (more than active_connection_id_limit) #342
[x] When the retire_prior_to value increases, stop using any retired connection IDs and then add the connection ID to the pool of connection IDs (or just start using it immediately) #342

Wiring:

[x] Wire the PathManager into the necessary places so that on_packet_ack, on_packet_loss, on_transmit, and transmission_interest are called

All issues are solved except https://github.com/aws/s2n-quic/issues/2043, closing in favor of that issue


text:
2024-10-02_01-35-16_master-next_python3-boto3

Automatically created.

Backport failed for kirkstone-next, because it was unable to cherry-pick the commit(s).
Please cherry-pick the changes locally.
git fetch origin kirkstone-next
git worktree add -d .worktree/backport-9792-to-kirkstone-next origin/kirkstone-next
cd .worktree/backport-9792-to-kirkstone-next
git checkout -b backport-9792-to-kirkstone-next
ancref=$(git merge-base bdbb598b4af0c56f4d7ddf52a7a77cfc7a2989a0 6aa1db90f4c1ac73654eebc4bc892d97606aaed0)
git cherry-pick -x $ancref..6aa1db90f4c1ac73654eebc4bc892d97606aaed0

Backport failed for scarthgap-next, because it was unable to cherry-pick the commit(s).
Please cherry-pick the changes locally.
git fetch origin scarthgap-next
git worktree add -d .worktree/backport-9792-to-scarthgap-next origin/scarthgap-next
cd .worktree/backport-9792-to-scarthgap-next
git checkout -b backport-9792-to-scarthgap-next
ancref=$(git merge-base bdbb598b4af0c56f4d7ddf52a7a77cfc7a2989a0 6aa1db90f4c1ac73654eebc4bc892d97606aaed0)
git cherry-pick -x $ancref..6aa1db90f4c1ac73654eebc4bc892d97606aaed0

Successfully created backport PR for styhead-next:

#9796


text:
Amplify Framework next.js typescript와 함께 코딩하기

참고문서
~next.js examples: with-aws-amplify-typescript~
TypeScript Next.js example

같은 코드 보니 code와 html이 막 섞여 있네요. 아무 재미있습니다.

authors: geoseong hunkim

repo: awskrug/kendra-button


text:
docs build needs environment installation (graphviz error)

I tried building the docs, but was met with a graphviz error. Typically this means I can spend a few hours pecking away at the dependencies until I get stable build... or someone that has it working can export their environment, and publish an environment.yml that we can use with the build instructions.
I was going off of the d2l book since that's a dep here, but their environment.yml seems incompatible since I must work with Python 3.7 due to the MXNet pip wheel for Mac, and the environment doesn't mention graphviz. Which, by the way, I recommend not using at all because of issues I ran up against trying to get some tutorials working on Windows. Graphviz seems to have dropped caring about Windows. Separate issues, but if we can maybe keep things to matplotlib, we might have an easier time making things cross-platform and keeping the dependencies manageable.

https://github.com/awslabs/autogluon/blob/master/docs/build.yml

repo: awslabs/autogluon


text:
Remove ConfigSpace

Issue #, if available:
Related PRs: #1397, #1411, #1414, #1431
Description of changes:

Remove ConfigSpace
Remove remaining outdated HPO code
Add LocalGridSearcher
Cleanup/streamline HPO logic in Tabular/Text

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

Job PR-1443-5 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1443/5/index.html

authors: Innixma szha


text:
Tabular: Removed deprecated arguments and methods.

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

Job PR-732-1 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-732/1/index.html


text:
Authorization error

1) Error in custom provider, com.amazonaws.AmazonServiceException: User: arn:aws:iam::<ID NUMBER>:user/<USER NAME> is not authorized to perform: apigateway:GET on resource: arn:aws:apigateway:us-east-1::/ (Service: null; Status Code: 403; Error Code: null; Request ID: )

With the following swagger:
{
    "swagger": "2.0",
    "info": {
        "version": "0.0.1",
        "title": "Tested Planet"
    },
    "paths": {
        "/test": {
            "get": {
                "description": "Test.\n",
                "parameters": [
                    {
                        "name": "phrase",
                        "in": "query",
                        "description": "phrase",
                        "required": true,
                        "type": "string"
                    }
                ],
                "responses": {
                    "200": {
                        "description": "Successful response",
                        "schema": {
                            "title": "Test",
                            "type": "object",
                            "properties": {
                                "phrase": {
                                    "type": "string"
                                }
                            }
                        }
                    },
                    "default": {
                        "description": "Unexpected error",
                        "schema": {
                            "$ref": "#/definitions/Error"
                        }
                    }
                },
                "x-amazon-apigateway-auth": {
                    "type": "none"
                },
                "x-amazon-apigateway-integration": {
                    "type": "aws",
                    "uri": "arn:aws:apigateway:us-east-1:lambda:path/2015-03-31/functions/arn:aws:lambda:us-east-1:<ACCOUNT ID>:function:getTest/invocations",
                    "credentials": "arn:aws:iam::<ACCOUNT ID>:role/lambda_basic_execution",
                    "httpMethod": "POST",
                    "requestTemplates": {
                        "application/json": "json request template 2",
                        "application/xml": "xml request template 2"
                    },
                    "requestParameters": {
                        "integration.request.path.integrationPathParam": "method.request.path.phrase"
                    },
                    "responses": {
                        "2\\d{2}": {
                            "statusCode": "200",
                            "responseTemplates": {
                                "application/json": "json 200 response template"
                            }
                        },
                        "default": {
                            "statusCode": "400",
                            "responseTemplates": {
                                "application/json": "json 400 response template"
                            }
                        }
                    }
                }
            }
        }
    },
    "definitions": {
        "Error": {
            "type": "object",
            "properties": {
                "code": {
                    "type": "integer",
                    "format": "int32"
                },
                "message": {
                    "type": "string"
                },
                "fields": {
                    "type": "string"
                }
            }
        }
    }
}

Did this previously work? It appears that the credentials used in your AWS SDK do not have valid permissions on the API Gateway API.
You will need to define a policy for the user/role similar to below. See http://docs.aws.amazon.com/apigateway/latest/developerguide/permissions.html
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"apigateway:GET"
],
"Resource": [
"arn:aws:apigateway:us-east-1::/restapis/[APID_ID]/*"
]
}
]
}

My policy looks like:
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "apigateway:*"
            ],
            "Resource": "arn:aws:apigateway:*::/*",
            "Condition": {
                "Null": {
                    "aws:MultiFactorAuthAge": "false"
                }
            }
        }
    ]
}

I believe there may be some trouble with my MFA tokens, which work for other aws services...

@edubkendo did you end up solving this issue? I am now seeing this w/ an IAM user who has the same group policy you posted but without the MFA condition. Other IAM users with the same group policy had no issue in the past... looking into it currently

Swagger/OpenAPI import is now generally available in the API Gateway REST API, the AWS CLI and all AWS SDKs. You can also import and export Swagger definitions using the API Gateway console. This release addresses many of the open issues and feedback in this repository.
I would encourage you to migrate your workflow to the standard AWS tools. aws-apigateway-importer will receive minimal support from the API Gateway team going forward.
Any feedback or issues with the new importer should be directed to the official API Gateway forums.
Thanks,
Ryan

authors: akotranza edubkendo rpgreen

repo: awslabs/aws-apigateway-importer

license_source: bigquery


text:
Lambda dlq check

I confirm these files are made available under CC0 1.0 Universal (https://creativecommons.org/publicdomain/zero/1.0/legalcode)
Issue: https://github.com/awslabs/aws-config-rules/issues/165
Description of changes:

Code looks good to me.
@jongogogo, kindly review this pull request

Closing the PR.

repo: awslabs/aws-config-rules


text:
HIVE_METASTORE_ERROR: com.facebook.presto.spi.PrestoException: Error: type expected at the position 0 of 'integer' but 'integer' is found

Hi guys, im getting the following error while trying to query using aws.athena.read_sql_query:

Traceback (most recent call last):
File "/Users/chriscollins/Documents/GitHub/FinishTimePredict/venv/lib/python3.7/site-packages/IPython/core/interactiveshell.py", line 3331, in run_code
exec(code_obj, self.user_global_ns, self.user_ns)
File "", line 3, in
database=AWS_DB_NAME).drop_duplicates()
File "/Users/chriscollins/Documents/GitHub/FinishTimePredict/venv/lib/python3.7/site-packages/awswrangler/athena.py", line 515, in read_sql_query
query_response: Dict[str, Any] = wait_query(query_execution_id=query_id, boto3_session=session)
File "/Users/chriscollins/Documents/GitHub/FinishTimePredict/venv/lib/python3.7/site-packages/awswrangler/athena.py", line 228, in wait_query
raise exceptions.QueryFailed(response["QueryExecution"]["Status"].get("StateChangeReason"))
awswrangler.exceptions.QueryFailed: HIVE_METASTORE_ERROR: com.facebook.presto.spi.PrestoException: Error: type expected at the position 0 of 'integer' but 'integer' is found. (Service: null; Status Code: 0; Error Code: null; Request ID: null). You may need to manually clean the data at location 's3://aws--results-249959970268-eu-west-1/tables/805b23***e-311b3e1b537e' before retrying. Athena will not delete data in your account.

It doesn't seem to be directly related to awswrangler but I did create the database and tables with awswrangler too. From what I've been able to read online it could be due to some kind of schema mismatch. When I created the table I specified the schema with the following dict:
SCHEMA_COLUMNS = {
     'date': 'timestamp',
     'course': 'string',
     'off': 'string',
     'name': 'string',
     'type': 'string',
     'class': 'string',
     'pattern': 'string',
     'rating_band': 'string',
     'age_band': 'string',
     'sex_rest': 'string',
     'dist': 'string',
     'dist_y': 'integer',
     'dist_m': 'integer',
     'dist_f': 'string',
     'going': 'string',
     'num': 'integer',
     'pos': 'string',
     'ran': 'integer',
     'draw': 'integer',
     'btn': 'double',
     'ovr_btn': 'double',
     'horse': 'string',
     'sp': 'string',
     'dec': 'double',
     'age': 'integer',
     'sex': 'string',
     'wgt': 'string',
     'lbs': 'integer',
     'hg': 'string',
     'time': 'double',
     'jockey': 'string',
     'trainer': 'string',
     'or': 'double',
     'rpr': 'double',
     'ts': 'double',
     'prize': 'string',
     'sire': 'string',
     'dam': 'string',
     'damsire': 'string',
     'owner': 'string',
     'comment': 'string',
     'country': 'string',
     'id': 'integer',
     'horse_cleaned': 'string',
     'jockey_clened': 'string',
     'trainer_cleaned': 'string',
     'year': 'integer'
 }

This solution was working before. The only difference I have made is partitioning by year, where previously there was no partition. I notice in the schema list in AWS Glue, year is now the first column, instead of the last as defined here. Do you think that could be the issue?

Ah, fixed it! integer is not a valid data type, it has to be int. I will leave this here in case anyone has a similar issue

Thanks @qemtek, this thread could help others in the future.
In addition, the data types supported are here in the service documentation.
In this "integer family" the options are:

TINYINT (8 bits)
SMALLINT (16 bits)
INT (32 bits)
BIGINT (64 bits)

authors: igorborgest qemtek

repo: awslabs/aws-data-wrangler


text:
Refactoring pagination config in list objects

Issue #, if available:
#955
Description of changes:
Refactored pagination config logic to accept being overridden by the user
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-pDO66x4b9gEu
Commit ID: f37b8d4cb9c6f38c32eff176ae5c049c9b485450
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-pDO66x4b9gEu
Commit ID: 450dd4d585808403aee91a7c4eead7fb91f4bd78
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-pDO66x4b9gEu
Commit ID: ff7b3a90a5aa93fdf220eec9a54c0b6fd8f394bb
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-pDO66x4b9gEu
Commit ID: f3201fef831c2a8d889934f887edaf32c4eee97a
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


text:
AWSSchemaRegistryClient can't be reused for different schemas

Hi,
just a minor thing, that is not blocking us, but might be useful to implement:
AWSSchemaRegistryClient takes the compatibility setting and description from private field glueSchemaRegistryConfiguration:
private CreateSchemaRequest getCreateSchemaRequestObject(String schemaName, String dataFormat, String schemaDefinition) {
        return CreateSchemaRequest
                .builder()
                .dataFormat(DataFormat.valueOf(dataFormat))
                .description(glueSchemaRegistryConfiguration.getDescription())
                .registryId(RegistryId.builder().registryName(glueSchemaRegistryConfiguration.getRegistryName()).build())
                .schemaName(schemaName)
                .schemaDefinition(schemaDefinition)
                .compatibility(glueSchemaRegistryConfiguration.getCompatibilitySetting())
                .tags(glueSchemaRegistryConfiguration.getTags())
                .build();
    }

This means that we can't use the same client instance for different schemas, cause every schema has other description or eventually also other compatibility level.
Might make sense that description and compatibility are also method parameters?
All in all, I am wondering if it makes sense to have compatibility and description as part of GlueSchemaRegistryConfiguration because they really depend on the schema. All other fields are more "global" settings that have same value for every schema. What do you think?
Just as background: We do not register our schemas via the serializer, but have an own pipeline that loops through all of our schemas and registers them with a client instance. With the current implementation, I need own instance per schema with new config to pass individual description.

Thanks for reaching out to us. If you are just using the client, would it make sense if we provide you with an overridden method that takes compatibility and description as parameters that you can use ?
We can also provide the description and compatibility as a part of schema naming strategy.
Let us know what do you think.

As an alternate, you could also use Glue SDK to create glue client and that way you can work without serializer/deserializer library. If you are using auto registration, then you may have to wrap some logic in your client.

Thanks for reaching out to us. If you are just using the client, would it make sense if we provide you with an overridden method that takes compatibility and description as parameters that you can use ?
We can also provide the description and compatibility as a part of schema naming strategy.
Let us know what do you think.

Yes, that is the same way we did it now in our temporary custom solution.
Would make sense to pass description and compatibility as parameter to getORRegisterSchemaVersionId.

Great to hear that you have a custom solution working. Does that unblock you or would you like to have this incorporated from Schema Registry ?

Assuming this is fixed. Please feel free to re-open if you are still facing this.

authors: FabianF92 blacktooth mohitpali

repo: awslabs/aws-glue-schema-registry


text:
Period not parsed correctly "...is an unknown value" "schedule name is unknown"

Hi - I am having an issue where the period config doesn't be seem to be read properly.  The schedule and period is as below
      {
         "RetainRunning": false,
         "Enforced": true,
         "Hibernate": false,
         "Description": "Day to day office hours of eem including holidays",
         "ConfiguredInStack": "arn:aws:cloudformation:...stack/....",
         "StopNewInstances": true,
         "Periods": [
            "eem-office-hours-incl-holidays-21-period-0011",
            "eem-office-hours-incl-holidays-21-period-0001",
            "eem-office-hours-incl-holidays-21-period-0003",
            "eem-office-hours-incl-holidays-21-period-0002",
            "eem-office-hours-incl-holidays-21-period-0009",
            "eem-office-hours-incl-holidays-21-period-0012",
            "eem-office-hours-incl-holidays-21-period-0004",
            "eem-office-hours-incl-holidays-21-period-0008",
            "eem-office-hours-incl-holidays-21-period-0005",
            "eem-office-hours-incl-holidays-21-period-0010",
            "eem-office-hours-incl-holidays-21-period-0006",
            "eem-office-hours-incl-holidays-21-period-0007"
         ],
         "Timezone": "Europe/Berlin",
         "Type": "schedule",
         "Name": "eem-office-hours-incl-holidays-21"
      }

{
         "Description": "July, Schedule eem-office-hours-incl-holidays-21 period 7, do not delete or update manually",
         "Monthdays": [
            "1-31"
         ],
         "Months": [
            "7"
         ],
         "Weekdays": [
            "mon-fri"
         ],
         "Begintime": "07:15",
         "Endtime": "18:30",
         "Type": "period",
         "Name": "eem-office-hours-incl-holidays-21-period-0007"
      }

And in CloudWatchEventHandler cloudwatch logs I see this
ERROR : "1-31" is an unknown value
In my rds cloudwatch log I also see
WARNING : Skipping instance RDS:.... in region eu-central-1 for account ....., schedule name "eem-office-hours-incl-holidays-21" is unknown
Do you know what might be wrong here?

Please try to specify Monthdays, Weekdays and Months as strings instead of Arrays of strings.

How so? It is passed in via cloudformation like so
  eemOfficeHoursInclHolidays21:
    Type: Custom::ServiceInstanceSchedule
    Properties:
      Name: eem-office-hours-incl-holidays-21
      NoStackPrefix: 'True'
      Description: Day to day office hours of eem including holidays
      ServiceToken: !GetAtt InstanceSchedulerLambda.Arn
      Enforced: 'True'
      Timezone: Europe/Berlin
      Periods:
        - Description: January
          Months: 1
          WeekDays: 'mon-fri'
          MonthDays: '2-5,7-31'
          BeginTime: '07:15'
          EndTime: '18:30'

@e-power : Hi,
we are facing some kind of a similar issue. When defining MonthDays which exceeds 27, you are not able to define it as a range.
For example the following does not work:
---
AWSTemplateFormatVersion: '2010-09-09'
Parameters:
  ServiceTokenSchedule:
    Description: Token
    Type: String
Resources:
  FeoAUUTC:
    Type: Custom::ServiceInstanceSchedule
    Properties:
      Description: FeoAUUTC
      ServiceToken: !Ref ServiceTokenSchedule
      Enforced: 'True'
      Timezone: Europe/Berlin
      Periods:
      - Description: Feo AU Up April
        Months: apr
        MonthDays: 6-30

This does work:
---
AWSTemplateFormatVersion: '2010-09-09'
Parameters:
  ServiceTokenSchedule:
    Description: Token
    Type: String
Resources:
  FeoAUUTC:
    Type: Custom::ServiceInstanceSchedule
    Properties:
      Description: FeoAUUTC
      ServiceToken: !Ref ServiceTokenSchedule
      Enforced: 'True'
      Timezone: Europe/Berlin
      Periods:
      - Description: Feo AU Up April
        Months: apr
        MonthDays: 6-27,28,29,30

I know that this is a bug since a long time. What´s new for me is that in the passed the Cloudformation-Stack failed to create and told me that 30 is an unknown value. Which it does not anymore.
Is it possible to either fix this issue or hand over the error back to cloudformation again?

Hi,
Currently, the range greater than 1-28 doesn't works because of date 28 is available in all months and dates greater than that are not. Also, We understand that this is not the best design approach. we will take this issue into our backlog and we will try to improve the design in upcoming releases.
Meanwhile to use range greater that 28, you can try this 'MonthDays: 1-28,29,30,31'
Thanks,
Praveen

Thanks for the info, especially @Nico-DB
@praveenis is this documented somewhere? and if not, could it be?

Did you try to use "L" as wildcard for the lastday of the calendar month?
It's mentioned at https://docs.aws.amazon.com/solutions/latest/instance-scheduler/components.html#period-rules in The "Period definitions table"
monthdays
Enter a comma-delimited list of days of the month, or a hyphenated range of days, during which the instance will run. For example, enter 1, 2, 3 or 1-3 to run an instance during the first three days of the month. You can also enter multiple ranges. For example, enter 1-3, 7-9 to run an instance from the 1st to the 3rd and the 7th through the 9th.You can also schedule an instance to run every nth day of the month or every nth day of the month in a range. For example, enter 1/7 to run an instance every seventh day starting on the 1st. Enter 1-15/2 to run an instance every other day from the 1st to the 15th.
Enter L to run an instance on the last day of the month. Enter a date and W to run an instance on the nearest weekday to the specified date. For example, enter 15W to run an instance on the nearest weekday to the 15th.

L could work in some cases yes, but it doesn't actually solve the problem

@e-power Thank you for considering. Would it be possible to extend the custom resource in the meantime, so cloudformation get an error while creating the schedules? In my opinion this was the care in the past.

Hi @e-power ,
we will update the documentation in the upcoming release.
Thanks,
Praveen

authors: Nico-DB arieleeuw e-power praveenis

repo: awslabs/aws-instance-scheduler


text:
Assess Current State of Plugin Docs

Look thru the existing plugin docs and assess which ones are not complete

Docs updated to latest state.  Ray needs updates, but unsure what the parameters are.

repo: awslabs/aws-orbit-workbench


text:
Build autocomplete index in the background

Especially with the addition of documentation, the index build can take a really long time.  It would be better to build this in the background.

Closing out issue.  The doc indexer runs in the background, which was the main issue.  I think there's room to parallelize the initial autocomplete index, but I don't think this is necessary right now.

repo: awslabs/aws-shell


text:
Unable to connect to CSRs via SSH

I had the following error in the CSR system log after initial boot:
Oct 26 00:04:12.580: %CVAC-3-XML_ERROR: Error while parsing XML from file varied:/ovf-env.xml: error 'XML_ERROR_FRAMING', element '', attribute '', explanation 'Invalid Escape Sequence '5 pass AHk%xp&E**rH''

It appears to be unhappy with the special characters in the randomly generated password. I've worked around this by hard coding a password in the template, but you might consider eliminating some special characters from the password generation script.

Thanks for the feedback. We updated the solution to only generate a password with letters and numbers to avoid this happening in the future.

authors: bwhaley stevemorad

repo: awslabs/aws-transit-vpc


text:
Enhance pull speed for Large ML container Images with Bottlerocket

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

What is the outcome that you are trying to reach?
Currently the inference container images run into multiple GBs in size. This negatively impacts the start up time for Ray Pods. We should look for ways to reduce the startup time of the Ray head and worker pods.

Describe the solution you would like

Validate if pre-fetching of images can be used leveraging EKS bottle rocket data volume in the inference blueprints to achieve this.
Describe alternatives you have considered

Additional context

https://aws.amazon.com/blogs/containers/reduce-container-startup-time-on-amazon-eks-with-bottlerocket-data-volume/

I would like to work on this

@lindarr915 Please let us know if you need any guidance on the repo. This will be a great addition. You can also write a blog doc under the resources section to discuss the performance improvements with Bottlerocket.

Hi @vara-bonthu Darren works with me in a same team. One thing we have discussed, do you want to make this solution as a parallel pattern as others? or make it kind of a "shared pattern" (eg. a TF module), as some of the existing patterns may all need it.
What do you think?

PR merged. Close the issue.

authors: hustshawn lindarr915 ratnopamc vara-bonthu

repo: awslabs/data-on-eks


text:
create virtual environment for running python script for RDStoRedshiftSqoop sample

This may be worthwhile so that we have more control over the environment we are running in.

This was added in the master readme.md file and is applicable to all samples.

authors: mbeitchman stmcpherson

repo: awslabs/data-pipeline-samples


text:
Larger batch size

Is there a recommended way to train with larger batch sizes using FastDP and a smaller physical memory GPU?
I am searching for a technique similar to the BatchMemoryManager from Opacus or standard non-private techniques such as here.

You can use gradient accumulation just like non-DP training, e.g. Line 96-99 in CIFAR_TIMM.py. This has nothing to do with DP engine so I am closing this issue. Feel free to reopen if you have further questions.

repo: awslabs/fast-differential-privacy


text:
[bug] Have to enter the password twice for each file

Version: 0.2.4
OS: Mac Mojave 10.14.2
I notice that when I reveal the secrets with the password of the email that match my github account, I only need to type in the password once for all files. But when using another password from another email, I have to enter it twice for each file; which means if I have n files, I have to enter the password 2n times.

Hi, it sounds like you might be talking about git-secret, not this project, which is git-secrets

authors: catriuspham steadmon

repo: awslabs/git-secrets


text:
Fix aggregate_valid function to ignore non-numeric columns

metric_per_ts.apply(np.ma.masked_invalid) fails when item_id column of the dataframe has strings in it.
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.
Please tag this pr with at least one of these labels to make our release process faster: BREAKING, new feature, bug fix, other change, dev setup

@lostella can we revert this... I believe it removes rows but then the evaluator doesn't remove the ground truth rows... causing issues... masking might be the way to go.... sorry!

@kashif thanks for letting me know; I should have asked you for tests ;-)

so sorry 😢 I will do that

authors: kashif lostella

repo: awslabs/gluon-ts