AWS connection instruction

What you'll need: access to AWS Console and AWS CloudShell with administrator permissions.

Step 1. Download the script archive Download the AWS archive from the public repository — the link is here. Unzip the archive. Keep all files in the same folder — the script references the policy files by relative path.

Step 2. Accept required Marketplace licences emma uses a set of AWS Marketplace images that require licence acceptance before they can be used. Open each link below and click Accept terms:

If a licence page shows Active subscription, it is already accepted — no action needed.

Step 3. Enable required AWS regions emma operates across multiple regions. By default, AWS only activates a limited set. You need to enable the following regions manually: Go to AWS Console → top-right account menu → Account → scroll to AWS Regions and enable all the regions.

AWS limits activation to 5 regions at a time. Enable them in batches and wait approximately 5 minutes between batches before the regions become fully active.

Step 4. Run the script Open AWS CloudShell in your account (the terminal icon in the top navigation bar). Upload the configure.sh file using the Actions → Upload file button in the CloudShell toolbar, then run the following commands:

chmod +x configure.sh
./configure.sh

The script will create a dedicated service user with the required permissions and write the credentials to temp_access_keys.txt in the current directory.

When complete, the terminal will display:

Script execution completed successfully.
Credentials saved to temp_access_keys.txt

Step 5. Find your Account ID In the AWS Console, click your account name in the top-right corner. Your Account ID is displayed at the top of the dropdown (12-digit number).

Step 6. Enter credentials in emma Open the file to retrieve your credentials:

cat temp_access_keys.txt

The file contains:

access_key_id
secret_access_key

Copy these credentials immediately. The secret_access_key is shown only once — it cannot be retrieved later. If lost, you will need to delete the key and re-run the script to generate a new one.

In the selected provider's input table, fill in the following fields:

emma field	Value	Source
Login (Access Key ID)	access_key_id	temp_access_keys.txt
Password (Secret Access Key)	secret_access_key	temp_access_keys.txt
Account ID	12-digit account number	AWS Console top-right corner

Click Connect account. emma will validate the connection — this takes a few seconds. On success, the provider status will change to CONNECTED and the discovery button will become available.

Troubleshooting If the connection fails, the status will remain NOT CONNECTED and an error message will appear.

Symptom	Likely cause	Fix
Script prints its own code instead of running	Missing execute permission	Run `chmod +x configure.sh` before `./configure.sh`
Permission denied errors during script	Insufficient AWS user permissions	Make sure your AWS user has administrator access
temp_access_keys.txt not found after script	Script exited with an error mid-run	Check terminal output for errors, re-run the script
InvalidClientTokenId error in emma	access_key_id copied incorrectly	Open temp_access_keys.txt again and re-copy the value
SignatureDoesNotMatch error in emma	secret_access_key copied incorrectly or truncated	Re-copy the full value — it is case-sensitive
AuthFailure or account not found	Wrong Account ID	Recheck the 12-digit ID from the top-right corner of the AWS Console
Marketplace image errors after connect	Required licences not accepted	Return to Step 2 and accept any remaining licences
Resources missing in certain regions	Region not enabled	Return to Step 3 and enable the missing region, then wait 5 minutes

Previous entries are not saved — you can re-enter new credentials at any time without restrictions.

How is this guide?

Last updated on 14 Jul 2026