You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You are receiving this notification because we identified you have one or more Amazon CloudWatch rule(s) that monitor AWS Lambda API events logged through AWS CloudTrail. [1]
Previously, AWS Lambda API names were logged with a date suffix in the EventName for your CloudTrail logs. The event names changed as service APIs were enhanced with new features and capabilities. In order to simplify automation of log processing, we are now removing the date suffixes from the EventName. With this change, Lambda will only log documented API names in the EventName field as part of the CloudTrail event. The list of updated and old API events are listed in this message.
This change will roll out to your account on October 20, 2021. Before this date, please evaluate and update any automation workflows that process Lambda API events from CloudTrail logs to use the Event Name without date suffix.
Failing to update the event names in your automation may prevent you from performing the desired actions after calling Lambda APIs. If your automation relies on accessing the Lambda API version, you can use the apiVersion field in CloudTrail.
List of API event names that will be logged going forward:
AddLayerVersionPermission
AddPermission
CreateAlias
CreateEventSourceMapping
CreateFunction
DeleteAlias
DeleteEventSourceMapping
DeleteFunction
DeleteFunctionConcurrency
DeleteLayerVersion
GetAccountSettings
GetAlias
GetEventSourceMapping
GetFunction
GetFunctionConfiguration
GetLayerVersion
GetLayerVersionByArn
GetLayerVersionPolicy
GetPolicy
ListAliases
ListEventSourceMappings
ListFunctions
ListLayers
ListLayerVersions
ListTags
ListVersionsByFunction
PublishLayerVersion
PublishVersion
PutFunctionConcurrency
RemoveLayerVersionPermission
RemovePermission
TagResource
UntagResource
UpdateAlias
UpdateEventSourceMapping
UpdateFunctionCode
UpdateFunctionConfiguration
Events Logged before Update
CreateFunction20150331
UpdateFunctionConfiguration
UpdateFunctionConfiguration20150331
UpdateFunctionConfiguration20150331v2
UpdateFunctionCode
UpdateFunctionCode20150331
UpdateFunctionCode20150331v2
DeleteFunction
DeleteFunction20150331
CreateAlias20150331
UpdateAlias20150331
DeleteAlias20150331
AddPermission20150331
AddPermission20150331v2
RemovePermission20150331
RemovePermission20150331v2
PutFunctionConcurrency20171031
DeleteFunctionConcurrency20171031
CreateEventSourceMapping20150331
DeleteEventSourceMapping20150331
UpdateEventSourceMapping20150331
PublishVersion20150331
TagResource20170331
TagResource20170331v2
UntagResource20170331
UntagResource20170331v2
GetFunction
GetFunctionConfiguration
GetFunction20150331
GetFunction20150331v2
GetFunctionConfiguration20150331
GetFunctionConfiguration20150331v2
ListFunctions20150331
GetPolicy20150331
GetPolicy20150331v2
GetEventSourceMapping20150331
GetAccountSettings20150331
GetAccountSettings20160819
ListEventSourceMappings20150331
ListVersionsByFunction20150331
ListTags20170331
GetAlias20150331
ListAliases20150331
PublishLayerVersion20181031
DeleteLayerVersion20181031
GetLayerVersion20181031
GetLayerVersionByArn20181031
ListLayerVersions20181031
ListLayers20181031
AddLayerVersionPermission20181031
RemoveLayerVersionPermission20181031
GetLayerVersionPolicy20181031
If you require further assistance, please reach out to the AWS Support team [2].
Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amazon.com is a registered trademark of Amazon.com, Inc. This message was produced and distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA 98109-5210
"""
The text was updated successfully, but these errors were encountered:
Email from AWS
"""
Hello,
You are receiving this notification because we identified you have one or more Amazon CloudWatch rule(s) that monitor AWS Lambda API events logged through AWS CloudTrail. [1]
Previously, AWS Lambda API names were logged with a date suffix in the EventName for your CloudTrail logs. The event names changed as service APIs were enhanced with new features and capabilities. In order to simplify automation of log processing, we are now removing the date suffixes from the EventName. With this change, Lambda will only log documented API names in the EventName field as part of the CloudTrail event. The list of updated and old API events are listed in this message.
This change will roll out to your account on October 20, 2021. Before this date, please evaluate and update any automation workflows that process Lambda API events from CloudTrail logs to use the Event Name without date suffix.
Failing to update the event names in your automation may prevent you from performing the desired actions after calling Lambda APIs. If your automation relies on accessing the Lambda API version, you can use the apiVersion field in CloudTrail.
List of API event names that will be logged going forward:
Events Logged before Update
If you require further assistance, please reach out to the AWS Support team [2].
[1] https://docs.aws.amazon.com/lambda/latest/dg/logging-using-cloudtrail.html
[2] https://aws.amazon.com/support
Sincerely,
Amazon Web Services
Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amazon.com is a registered trademark of Amazon.com, Inc. This message was produced and distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA 98109-5210
"""
The text was updated successfully, but these errors were encountered: