You could use the AWS CLI to check the current limit for IAM Server certificates by running the AWS CLI command -
$ aws service-quotas get-service-quota --service-code iam --quota-code L-BF35879D --region us-east-1
==============
{
"Quota": {
"ServiceCode": "iam",
"ServiceName": "AWS Identity and Access Management (IAM)",
"QuotaArn": "arn:aws:servicequotas::895006963947:iam/L-BF35879D",
"QuotaCode": "L-BF35879D",
"QuotaName": "Server certificates per account",
"Value": "55",
"Unit": "None",
"Adjustable": "true",
"GlobalQuota": "true",
"UsageMetric": null,
"Period": null,
"ErrorReason": null
}
}
==================
Here, you could see the Value as 55.
b. You could use the AWS Console to see this details.
Please make sure to select the region as 'us-east-1' regions.
Then please navigate to AWS services > AWS Identity and Access Management (IAM) > Server certificates per account.
Here, you could see the list.
Query 2 - Where you could see how many certificates are being used.
Answer - You could run the following CLI command to list the IAM certificates in your account -
$ aws iam list-server-certificates
I hope the above information is helpful. In case of any other query or concern, please feel free to update the case and I will be glad to assist you further.
References:
https://docs.aws.amazon.com/cli/latest/reference/service-quotas/get-service-quota.html#examples
[2] https://docs.aws.amazon.com/cli/latest/reference/iam/list-server-certificates.html#examples
To receive the SQS Queue messages from exst-prod-integration-hub-outbound-eit.fifo Queue,
Expand more on the SQS Queue (exst-prod-integration-hub-outbound-eit.fifo) and check the available messages,
Go to Lambda function (PROD_SQS_Receive_Message)and click Add Trigger, Refer below code
Select SQS as source,
Select exst-prod-integration-hub-outbound-eit.fifo as Queue name,
Select 1 as Batch Size then only we’ll get 1 record on CSV file in JSON format,
Maximum Concurrency is 2
Click Add on the trigger page
We can confirm the Lambda on SQS Page under “Lambda Triggers”
Once we are done with Lambda Execution, select the Trigger and Delete from SQS Page or else it’ll keep on receive the message and post to Cloud watch event,
Under Cloudwatch LogGroup, on top right click “View in Logs Insight”. Click custom timeline and click the date twice so we get log for full day and paste the below code and Run Query.
Once the Query is displayed then verify the number of message on the Metrics and click “Export results” and then select “Download table (JSON)”
Rename the file with Date and messages and upload to S3 bucket under json folder
Alternatively you can follow the manual step.
Click the Log Stream and click ACTIONS and select “Download search results (CSV)” then we can export it to csv format
The PEM-encoded certificate is stored in a file named Certificate.pem.
The PEM-encoded certificate chain is stored in a file named CertificateChain.pem.
The PEM-encoded, unencrypted private key is stored in a file named PrivateKey.pem.
To use the following example, replace the file names with your own and type the command on one continuous line. The following example includes line breaks and extra spaces to make it easier to read.
