Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Amazon AWS Message
I received this message from Amazon AWS, and not really sure whether it affects me or not.  I do use both the CQC Echo and the Native Echo integration.

Any thoughts?

You are receiving this message because we identified that your account created or updated or invoked Lambda functions on or after July 1, 2021.

AWS Lambda is extending the capability to track the current state of a function through its lifecycle to all functions [1]. With this change, you may need to update your CLI and/or SDK-based automation workflows around creating and updating functions by adding a check that the function became active before performing additional actions that operate on the function.

Previously, states have been used in two primary use-cases. Firstly, to move the blocking setup of VPC resources out of the path of function invocation. Secondly, to allow the Lambda service to optimize new or updated container images for container-image based functions, also before invocation. By moving this additional work out of the path of the invocation, customers see lower latency and better consistency in their function performance.
Infrastructure as code and deployment automation tools such as AWS CloudFormation, AWS Serverless Application Model (SAM), AWS Cloud Development Kit (CDK), Serverless Framework,Hashicorp Terraform, AWS Chalice and Cloud Custodian already support states.

If you are using these tools and are already on the latest Software Development Kit (SDK), you do not need to take any action, and can stop reading now. If you are using an earlier SDK version, please update to the latest one.

We are rolling out this change over multi-phase periods to allow you to update existing tooling for deploying and managing Lambda functions. You can delay this change for your functions until December 5, 2021. Starting December 6, 2021, the delay mechanism expires and all customers see the Lambda states lifecycle applied during function create or update. Read this blog post [2] to learn about this change, timelines for different phases and a reference example on how to check your function state.

If you have any questions, please contact AWS Support [3].
I don't think any of that would be applicable.
Dean Roddey
Explorans limites defectum

Possibly Related Threads…
Thread Author Replies Views Last Post
  Driver for Amazon 4k Stick Darrie 3 822 01-15-2022, 02:21 PM
Last Post: znelbok
  Sonos Log Message karenlee 5 1,269 10-24-2021, 04:18 AM
Last Post: karenlee
  Amazon Echo integration rhosch 8 2,185 05-15-2021, 01:06 PM
Last Post: Bugman
Big Grin A Big Thanks on my 1000th Forum Message kblagron 1 1,656 09-12-2018, 10:35 PM
Last Post: Dean Roddey
  New Amazon Echo Support Dean Roddey 591 259,065 02-21-2018, 12:56 PM
Last Post: Dean Roddey
  Amazon email re Alexa interface? Ron Haley 5 5,094 03-14-2017, 02:40 PM
Last Post: Dean Roddey
  Google Home Integration using Amazon Echo Approach? Jnetto 4 4,912 12-21-2016, 02:04 PM
Last Post: Jnetto
  New Amazon Dot Ron Haley 18 5,832 10-22-2016, 07:21 AM
Last Post: Ron Haley
  unclear error message IVB 7 3,619 09-03-2016, 10:32 PM
Last Post: IVB
  Amazon echo driver Ron Haley 6 2,316 07-01-2016, 05:47 AM
Last Post: wuench

Forum Jump:

Users browsing this thread: 1 Guest(s)