Page History

...

Can I coordinate VPC Availability Zones between AWS accounts?

In practiceshort, noyes.  To ensure distribution of load across their infrastructure, AWS creates an independent mapping of Availability Zone designations (ie: "us-east-1a", "us-east-1d") for each account.  Within the same Region, there is no way if you need to guarantee the Availability Zone that you see as "zone A" lives in the same back-end environment as "zone A" seen from a different AWS account you will need to utilize the Availability Zone ID.  For more information about zones and regions, see the AWS documentation on Regions and Availability Zones.

...

1. Install the aws login tool (Access Keys for AWS CLI Using Cornell Two-Step Login (- Shibboleth)
2. Docker with the aws login tool with other helpful cloud utilities (https://github.com/CU-CommunityApps/ct-cloud-utils-dockerized)
3. Install the aws cli (https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-install.html) using 'aws sts get-session-token' with a new or existing IAM user (https://docs.aws.amazon.com/cli/latest/reference/sts/get-session-token.html)

1. 1. Create a new or use default profile
   2. "aws configure --profile {name}"

• AWS CLI
  1. Access Keys for AWS CLI Using Cornell Two-Step Login (- Shibboleth)
• rclone
  1. rclone config
     1. set id, secret and session token (under advanced config)
• Cyberduck 
  1. Copy ID, Secret and Token from ~/.aws/credentials {name}
     1. aws_access_key_id = [ paste ID ]
     2. aws_secret_access_key = [ paste key ]
     3. aws_session_token = [ paste token ]
  2. Download Cyberduck STS token profile
  3. Open Connection - S3 (Credentials from AWS Security Token Service)
     1. Specify profile from #1
        
• Mountain Duck now available with similar process as outlined above with CyberDuck.

...