- cost-modeling - lists.anvilproject.org

[Notification] AWS Trusted Advisor will be removing 3 checks on April 25, 2024 [AWS Account: 183998710709] [US-EAST-1]
by Amazon Web Services, Inc. 09 Apr '24

09 Apr '24

Hello, We would like to inform you about upcoming changes to 3 AWS Trusted Advisor checks that will take effect on April 25, 2024. These updates are designed to provide more accurate and relevant recommendations based on the latest best practices and service enhancements. - “IAM Use” (ID: ZXCkfM1nI3) is being phased out due to changes in its underlying best practices. - “Security Groups - Specific Ports Unrestricted” (ID: HCP4007jGY) and “Security Groups - Unrestricted Access” (ID: 1iG5NDGVre) are being replaced as they did not account for customer-managed prefix lists being used to grant access in security groups. If you have AWS Security Hub enabled, we recommend using the updated checks “Security groups should only allow unrestricted incoming traffic for authorized ports” (TA Check ID: Hs4Ma3G178, Security Hub Control ID: EC2.18) and “Security groups should not allow unrestricted access to ports with high risk” (TA Check ID: Hs4Ma3G204, Security Hub Control ID: EC2.19). These checks account for prefix lists and provide comprehensive security group monitoring. To view these AWS Security Hub controls (EC2.18 and EC2.19) in Trusted Advisor, you must have a Business, Enterprise On-Ramp, or Enterprise Support plan. You can find your support plan from the AWS Support Center [1]. For more information, see Compare AWS Support plans [2]. If you have any questions or concerns regarding these changes, please don’t hesitate to contact AWS support [1]. [1] https://aws.amazon.com/support [2] https://aws.amazon.com/premiumsupport/plans 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 --- Reference: https://health.aws.amazon.com/health/home?region=us-east-1#/event-log?event…

1 0

Amazon Web Service Tax Exemption
by Amazon Web Services 07 Mar '24

07 Mar '24

<html xmlns="http://www.w3.org/1999/xhtml"> <body width="100%" bgcolor="#F0F2F3" style="margin: 0;"> <center style="width: 100%; background: #F0F2F3; text-align: left;"> <div style="margin: auto; max-width: 600px; padding-top: 50px;" class="email-container">  <table role="presentation" cellspacing="0" cellpadding="0" border="0" align="center" width="100%" id="logoContainer" style="background: #252F3D; border-radius: 3px 3px 0 0; max-width: 600px;"> <tr> <td style="background: #252F3D; border-radius: 3px 3px 0 0; padding: 20px 0 10px 0; text-align: center;"> <a href="https://aws.amazon.com" target="_blank" title="Amazon Web Services"> <img src="https://m.media-amazon.com/images/G/01/amazonwebservices/AWS_logo_RGB_REV.p…" width="75" height="45" alt="AWS logo" border="0" style="font-family: sans-serif; font-size: 15px; line-height: 140%; color: #555555;"> </a> </td> </tr> </table>   <table role="presentation" cellspacing="0" cellpadding="0" border="0" align="center" width="100%" id="emailBodyContainer" style="border: 0px; border-bottom: 1px solid #D6D6D6; max-width: 600px; table-layout:fixed;"> <tr> <td style="background-color: #FFF; color: #444; font-family: 'Amazon Ember', 'Helvetica Neue', Roboto, Arial, sans-serif; font-size: 14px; line-height: 140%; padding: 25px 35px;"> <div><p> Dear Customer, <br /> <br /> Our records indicate you have a US exemption certificate that you provided through the AWS Console and/or the Amazon Tax Exemption Program (ATEP) portal. <br /> <br /> Starting 15 April 2024, all US exemption certificates for AWS accounts will only be accepted when they are uploaded via the AWS Console. After this date, documents uploaded on Amazon Tax Exemption Program (ATEP) will only be accepted for Amazon retail accounts and will no longer be accepted for enrollment for AWS. To ensure tax exemption for AWS services, please upload an exemption form to AWS via the AWS Console by following instructions <a href="https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/manage-account…"> here </a> . <br /> <br /> Your current active exemption, whether uploaded through ATEP or the AWS Console, will remain active until it expires (if applicable). To retain your AWS tax exempt status, you must submit an updated exemption certificate via the AWS Console before the expiration of the current certificate. Applicable expiration dates are noted in our database. <br /> <br /> Thanks, <br /> Amazon Web Services </p></div> </td> </tr> </table>  </div> </center> </body> </html>

1 0

[Correction] Changes to AWS Managed Policy [AWS Account: 183998710709]
by Amazon Web Services, Inc. 24 Nov '23

24 Nov '23

Hello, We recently notified you that the AWS Managed Policy "CloudWatchFullAccess" [1] would be deprecated on December 7, 2023, in favor of "CloudWatchFullAccessV2" [2]. However, based on customer feedback we have decided to continue supporting both policies and no immediate action is required. If you have questions or concerns, please reach out to AWS Support [3]. [1] https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/auth-and-acc… [2] https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/auth-and-acc… [3] 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 --- Reference: https://phd.aws.amazon.com/phd/home?region=us-east-1#/event-log?eventID=arn…

1 0

[Notification] New charge for public IPv4 addresses starting February 1, 2024 [AWS Account: 183998710709]
by Amazon Web Services, Inc. 16 Nov '23

16 Nov '23

Hello, You are receiving this notification because your AWS account has at least one public IPv4 address used in the last 30 days. On July 28, 2023, we announced [1] a new charge for public IPv4 addresses that will come into effect starting February 1, 2024. For details on your usage, you can look at the AWS Cost and Usage report. To monitor, analyze, and audit your use of public IPv4 addresses, you can look at Public IP Insights [2]. You can also read our blog post, Identify and Optimize Public IPv4 Address Usage on AWS [3], for information on how to optimize your use of public IPv4 addresses. For more details on public IPv4 address pricing, please see the VPC pricing page [4]. For questions, please reach out to AWS support [5]. [1] https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-… [2] https://aws.amazon.com/about-aws/whats-new/2023/07/aws-public-ip-insights-v… [3] https://aws.amazon.com/blogs/networking-and-content-delivery/identify-and-o… [4] https://aws.amazon.com/vpc/pricing/ [5] 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 --- Reference: https://phd.aws.amazon.com/phd/home?region=us-east-1#/event-log?eventID=arn…

1 0

[Notification] AWS CloudShell migrating from Amazon Linux 2 to Amazon Linux 2023 [AWS Account: 183998710709]
by Amazon Web Services, Inc. 07 Nov '23

07 Nov '23

Hello, AWS CloudShell's compute environment, which is currently based on Amazon Linux 2 (AL2), is scheduled to begin migration to Amazon Linux 2023 (AL2023) starting December 4, 2023. The migration will be performed on a Region by Region basis and will be completed by December 14, 2023. There will be no down time as a result of this migration. For more information on how to prepare for the migration, please refer to the AWS CloudShell User Guide [1]. If you have any questions or concerns, contact AWS Support on AWS re:Post [2] or via AWS Premium Support [3]. [1] https://docs.aws.amazon.com/cloudshell/latest/userguide/cloudshell-AL2023-m… [2] https://repost.aws/tags/TA5ZaPf1NkT4uNitnWVitlyQ/aws-cloudshell [3] 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 --- Reference: https://phd.aws.amazon.com/phd/home?region=us-east-1#/event-log?eventID=arn…

1 0

[Action Required] Changes to AWS Managed Policy [AWS Account: 183998710709]
by Amazon Web Services, Inc. 23 Oct '23

23 Oct '23

Hello, We are reaching out to notify you that AWS Managed Policy is making a change that will require your action. AWS Managed Policy is deprecating the managed policy "CloudWatchFullAccess" [1] and replacing it with "CloudWatchFullAccessV2" [2]. After December 7, 2023, "CloudWatchFullAccess" will no longer be supported. We have identified resources in your account with the "CloudWatchFullAccess" managed policy and recommend that you review those resources to replace that managed policy with "CloudWatchFullAccessV2". Please refer to the 'Affected Resources' tab of your AWS Health Dashboard for a list of your resources affected by this change. If you do not take any action, the accounts with the policy attached to a user, group, or role, will continue to see the policy in the account but cannot attach the policy to new users, groups, or roles or view the deprecated policy in the AWS IAM Console. The new policy includes: - Autoscaling:Describe permissions so users with this policy can see the Auto Scaling actions that are associated with CloudWatch alarms - SNS permissions so users with this policy can retrieve or create Amazon SNS topics and associate them with CloudWatch alarms - IAM permissions so users with this policy can view information about service-linked roles associated with CloudWatch - The oam:ListSinks and oam:ListAttachedLinks permissions so users with this policy can use the console to view data shared from source accounts in CloudWatch cross-account observability If you have questions or concerns, please reach out to AWS Support [3]. [1] https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/auth-and-acc… [2] https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/auth-and-acc… [3] 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 --- Reference: https://phd.aws.amazon.com/phd/home?region=us-east-1#/event-log?eventID=arn…

1 0

will Do Verify the factory,Sample Collection, Negotiation, Dropshipping, Shipping, After-Sales Follow-up, Search, Etc.
by polzikov.valerochka 06 Oct '23

06 Oct '23

1 0

[Notification] AWS CloudShell migrating from Amazon Linux 2 to Amazon Linux 2023 starting December 4, 2023 [AWS Account: 183998710709]
by Amazon Web Services, Inc. 24 Sep '23

24 Sep '23

Hello, AWS CloudShell's compute environment, which is currently based on Amazon Linux 2 (AL2), is scheduled to begin migration to Amazon Linux 2023 (AL2023) in all Regions starting December 4, 2023. You will receive another notification with additional information closer to the migration date. For more information on how to prepare for the migration, please refer to the AWS CloudShell User Guide [1]. If you have any questions or concerns, contact AWS Support on AWS re:Post [2] or via AWS Premium Support [3]. [1] https://docs.aws.amazon.com/cloudshell/latest/userguide/cloudshell-AL2023-m… [2] https://repost.aws/tags/TA5ZaPf1NkT4uNitnWVitlyQ/aws-cloudshell [3] 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 --- Reference: https://phd.aws.amazon.com/phd/home?region=us-east-1#/event-log?eventID=arn…

1 0

[Notification] Upcoming maintenance for your Amazon Managed Grafana workspace(s) [AWS Account: 183998710709] [US-EAST-1]
by Amazon Web Services, Inc. 18 Aug '23

18 Aug '23

Hello, Amazon Managed Grafana will perform a planned maintenance for your workspace on the weekend of September 16, 2023 between 8:00 AM and 5:00 PM PDT. During this time the following will take place: 1. Your Amazon Managed Grafana workspace will be in "updating" state. 2. Logged-in users will see a banner in the workspace that says "Grafana is temporarily in read-only mode while it is updating". 3. Workspace users will NOT be able to create, edit, or delete any dashboards, data sources, alerts, or teams for up to 45 minutes. You will continue to receive alerts and view dashboards. Amazon Managed Grafana recently launched support for updating your workspace version to 9.4. You can preempt this maintenance by updating your workspace to version 9.4 anytime before September 16, 2023, and gain access to the feature list in the following section. Amazon Managed Grafana v9.4 new features: * Plugin enhancements to support Amazon CloudWatch cross-account querying. * Amazon OpenSearch Serverless, querying multiple asset properties from AWS IoT Sitewise. * Query result reuse and async queries for Athena. * Prometheus and Loki query builders that make it even easier to create and modify queries for your data sources. * Service accounts to provide a secure and efficient way to automate tasks within your Grafana instance. For instructions on how to update your workspace(s), see Amazon Managed Grafana service documentation [1]. We recommend testing the newer version in a non-production environment before updating a production workspace. You can also migrate your dashboards and data sources from your existing workspace to a new v9.4 workspace for testing, using the Amazon Managed Grafana Migrator tool [2]. Note that any Amazon Managed Grafana workspaces in CREATE_FAILED or DELETE_FAILED state will be deleted as a part of the maintenance. If you wish to resolve these states, or have concerns deleting these workspaces, please reach out to AWS Support [3] by September 11, 2023. To learn more about Amazon Managed Grafana version differences, see the Amazon Managed Grafana service documentation [4]. The following is a list of your affected resource(s): g-565066eb8a If you have questions or concerns, please reach out to AWS Support [3]. [1] https://docs.aws.amazon.com/grafana/latest/userguide/AMG-workspace-version-… [2] https://github.com/aws-observability/amazon-managed-grafana-migrator [3] https://aws.amazon.com/support [4] https://docs.aws.amazon.com/grafana/latest/userguide/version-differences.ht… 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 --- Reference: https://phd.aws.amazon.com/phd/home?region=us-east-1#/event-log?eventID=arn…

1 0

Your AWS CloudShell data is scheduled for deletion on June 9, 2023 [AWS Account: 183998710709]
by Amazon Web Services, Inc. 30 May '23

30 May '23

Hello, Some users of this account haven’t used AWS CloudShell for over 110 days in the us-east-1 Region. On June 9, 2023 we’re scheduled to delete the CloudShell home directory and data of inactive users in the us-east-1 Region. You can see the list of affected users under the Affected Resources tab in your AWS Health Dashboard https://phd.aws.amazon.com/phd/home?region=us-east-1#/account/dashboard/sch…. To stop this deletion, users that are listed in the Affected Resources tab need to launch CloudShell https://us-east-1.console.aws.amazon.com/cloudshell/home?region=us-east-1# in the us-east-1 Region. Important: AWS CloudShell offers a separate home directory per AWS Region, so the deletion of the home directory will occur only in the AWS Region that hasn’t been used for your CloudShell sessions in over 120 days. If you regularly use CloudShell in other AWS Regions, those separate home directories will not be affected. Visit https://docs.aws.amazon.com/cloudshell/latest/userguide/limits.html#persist… if you’d like more information on persistent storage in AWS CloudShell. 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.

1 0