Service Quotas is an Amazon feature that you can use to view and manage your Amazon EMR service quotas, or limits, from a central location using the Amazon Web Services Management Console, the API or the CLI. To learn more about viewing quotas and requesting increases, see Amazon service quotas in the Amazon Web Services General Reference. Show
For some APIs, setting up a CloudWatch event might be a better option than increasing service quotas. You can also save time by using CloudWatch to set alarms and trigger increase requests proactively, before you reach the service quota. For more details, see When to set up EMR events in CloudWatch.
† These instance types provide 96 logical processors on 48 physical cores. They run on single servers with two physical Intel sockets. ‡ This instance type provides 48 logical processors on 24 physical cores. 🚀Solution Landing Page |
🚧Feature request |
🐛Bug Report | 📜Documentation Improvement Note: For any relevant information outside the scope of this readme, please refer to the solution landing page and implementation guide. Quota Monitor for AWS is a reference implementation that provides a foundation for monitoring AWS services' quotas usage. Customers can leverage the solution to monitor
quotas across services supported by Amazon Trusted Advisor and AWS Service Quotas; in multiple regions and multiple AWS accounts. The solution integrates with Amazon SNS and Slack to notify customers for service quotas approaching thresholds. The architecture can be broken down into different components, few which are installed in the monitoring account and others are installed in the monitored accounts. The monitoring account
also known as hub account, collects all usage events from the monitored accounts (spokes) and raises notifications. Additionally, all the usage events are put on DynamoDB table in the hub account, which can be used to view historical trend of resource usage across all accounts. Deployment scenarios:The solution follows hub-spoke model and supports different deployment scenarios
hub: For the first two scenarios use quota-monitor-hub.template. For environments not using Organizations, use quota-monitor-hub-no-ou.template. Note: Hub template should be deployed in the monitoring account. For the first two scenarios, this account should also be your delegated administrator for StackSets in the organization. spoke: Spoke templates are automatically deployed by StackSets for targeted Organizational Units. For hybrid environments and environments not using Organizations, deploy the spoke templates individually in the accounts where monitoring is needed. Note: ta-spoke.template should be deployed in us-east-1 ONLY. sq-spoke.template can be deployed in any region. Installing pre-packaged solution template
Note: hub, hub-no-ou and sq-spoke templates can be deployed in ANY region; prerequisite and ta-spoke template can be deployed in us-east-1 ONLY. Parameters for hub template
Note: Deployment Configuration parameter is not available in hub-no-ou template. Parameters for spoke templates
Note: You may leave rest of the parameters to default. CustomizationThe steps given below can be followed if you are looking to customize the solution or extend the solution with newer capabilities Setup
Clone the repository and run the following commands to install dependencies
(optional) Run the following commands to format and lint the project per the project standards
Note: Following steps have been tested under above pre-requisites Running unit tests for customizationRun unit tests to make sure added customization passes the tests.
✅ Ensure all unit tests pass. Review the generated coverage report. BuildTo build your customized distributable run build from the project root ✅ All assets are now built. DeployRun the following command from the root of the project
Bootstrap your CDK environment
Note:
✅ Solution stack is deployed with your customized code. Independent spoke templatesThere are two spoke templates packaged with the solution
Both spoke templates are independent standalone stacks that can be individually deployed. You can deploy the spoke stack and route usage events and notifications to your preferred destinations. Additionally, in sq-spoke stack you can control which services to monitor, by toggling monitored status of the services in the DynamoDB table ServiceTable. For deploying sq-spoke stack:
Note: BUS_ARN, substitute the arn of the EventBridge bus where you want to send usage events SSM Parameter Store based workflowThe solution provisions /QuotaMonitor/OUs and /QuotaMonitor/Accounts SSM Parameter Store. You can modify the parameters at any point after deployment to update the list of targeted organizational-units and accounts for monitoring.
File StructureThe project consists of several microservices, shared utility lambda layer and CDK resources
LicenseSee license here Collection of operational metricsThis solution collects anonymous operational metrics to help AWS improve the quality and features of the solution. For more information, including how to disable this capability, please see the implementation guide. Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved. Licensed under the Apache License Version 2.0 (the "License"). You may not use this file except in compliance with the License. A copy of the License is located at
or in the "license" file accompanying this file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied. See the License for the specific language governing permissions and limitations under the License. Which AWS service can a company use to monitor service quotas?You can access Service Quotas by visiting directly or by searching for it in the AWS management console.
What tool can be used to monitor AWS service limits?You can use Service Quotas console to view and request increases for most AWS quotas.
Which AWS service or feature allows users to connect with and deploy AWS services programmatically?AWS CodeDeploy is a fully managed deployment service that automates software deployments to various compute services, such as Amazon Elastic Compute Cloud (EC2), Amazon Elastic Container Service (ECS), AWS Lambda, and your on-premises servers.
Which AWS service or resource can the company use with Amazon CloudWatch to meet this requirement?Amazon CloudWatch can monitor AWS resources such as Amazon EC2 instances, Amazon DynamoDB tables, and Amazon RDS DB instances, as well as custom metrics generated by your applications and services, and any log files your applications generate.
|