After my investigation, I noticed that Cloud9 does not provide the functionality to move an environment from one AWS account to another. However I found a workaround by sharing the snapshot of Cloud9 instance from one account and creating a new Cloud9 environment with this snapshot in another account. You can find detailed steps below. 1. In AWS account A,…
Read More »I am using API Gateway REST API, however I noticed that there is 30 seconds timeout when using Lambda as backend. How can I execute lambda longer than 30 seconds? One option would be to have a Lambda function behind the API to handle requests asynchronously. This would allow Lambda to immediately respond with a success response 202 (Accepted) to…
Read More »It is kind of possible but this can lead to some unexpected behavior. https://docs.aws.amazon.com/connect/latest/adminguide/configure-saml.html#saml-important-notes Amazon Connect instance allow only a 1:1 mapping of user roles to SAML authentication. This means although you can create two IAM Identity Providers in your AWS account connecting to your Azure AD apps, those two providers have to share the same IAM role. Also, users…
Read More »As you may know, the default Elastic network interfaces (ENI) is 250 per VPC per region. In most cases, if it exceeds the default limit 250, this could be the cause of the error you are experiencing. To fix this issue, do one or both of the following: Delete unused elastic network interfaces, you can find more information from https://aws.amazon.com/premiumsupport/knowledge-center/lambda-eni-find-delete/…
Read More »When you invoke a function directly, you determine the strategy for handling errors. You can retry, send the event to a queue for debugging, or ignore the error. Your function’s code might have run completely, partially, or not at all. If you retry, ensure that your function’s code can handle the same event multiple times without causing duplicate transactions or…
Read More »After my investigation, I noticed that this feature is currently not supported because the environment owner is determined during creation. However there is a workaround to get the ownership of existing Cloud environment by creating an EBS snapshot of the current instance and attaching it to a new Cloud9 environment. Detailed steps are as below. Context: I have an environment…
Read More »