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
Customer using AWS Instance Scheduler has provided the following feature request to improve the security of the solution:
Addition of a VPC parameter for the Lambda function in the Instance Scheduler CloudFormation template.
This enhancement would allow the Lambda function to be deployed within a specified VPC, enabling secure access to AWS services (such as S3, CloudWatch, and RDS) through VPC endpoints.
Further, this adjustment would provide:
Network isolation for the Lambda function by eliminating the need for public internet access.
Private, VPC-only access to required AWS services through VPC endpoints, enhancing security and compliance.
The text was updated successfully, but these errors were encountered:
Thanks for submitting this request. It will be added to our backlock for prioritization. If anybody else would like to see this feature prioritized, please upvote this thread.
Hello Team,
Customer using AWS Instance Scheduler has provided the following feature request to improve the security of the solution:
Addition of a VPC parameter for the Lambda function in the Instance Scheduler CloudFormation template.
This enhancement would allow the Lambda function to be deployed within a specified VPC, enabling secure access to AWS services (such as S3, CloudWatch, and RDS) through VPC endpoints.
Further, this adjustment would provide:
Network isolation for the Lambda function by eliminating the need for public internet access.
Private, VPC-only access to required AWS services through VPC endpoints, enhancing security and compliance.
The text was updated successfully, but these errors were encountered: