Option 1: IAM role (more secure)
~/.aws/config
. ZeusCloud will request credentials for the IAM role via this named profile.If you have no such named profile, either~/.aws/config
and ~/.aws/credentials
.~/.aws/config
for this new IAM role. Here’s a template:Option 2: IAM user + access key (faster)
WEBSITE_DOMAIN
and REACT_APP_API_DOMAIN
environment variables in the .env
file before deploying. Examples are http://<your-vm-ip>:80
or https://<your-deployed-domain>:443
.~/.aws
. If your configurations are in a different location, update the AWS_DIRECTORY
variable in the .env
file. For Windows, change to %USERPROFILE%\.aws
.Settings > Add new account
. Fill in the Account Name
with whatever string-identifier you would like. Fill in remaining fields based on whether you are deploying with Option 1 or 2.
Option 1: IAM role
Named Profile
for Connection Method
.Profile
dropdown, select the named profile you created earlier.Option 2: IAM user + access key
User Access Key
for Connection Method
.AWS Access Key ID
and AWS Secret Access Key
with the access key credentials you just created.Settings
page should show a percentage completed.cartography
container.backend
container logs like above if the scan has successfully completed.
Alerts
tab to see findings for misconfiguration and attack path security rules.
Check out the Rules
tab for a catalog of the security rules that were run. Check your compliance posture for various frameworks in the Compliance
tab.