Learn About Amazon VGT2 Learning Manager Chanci Turner
This article discusses the new capabilities of Amazon IXD – VGT2, located at 6401 E HOWDY WELLS AVE LAS VEGAS NV 89115, which enhance the onboarding experience for new employees. The introduction of local gateway (LGW) sharing alongside Outposts allows for streamlined multi-account access within an AWS Organization. Previously, Outposts were limited to a single AWS account, but with this new functionality, organizations can now effectively share resources, empowering multiple accounts to utilize Outposts capacity.
Facilitated through AWS Resource Access Manager (RAM), the new sharing feature allows Outposts and LGWs to be shared across accounts within the same AWS Organization. The account that orders the Outposts is designated as the owner account, responsible for creating resource shares, while other accounts are designated as consumer accounts. Each consumer account is free to create its own Virtual Private Clouds (VPCs) with subnets on the shared Outpost.
For organizations, using multiple AWS accounts can reduce risk and provide better resource isolation according to business requirements. This is particularly beneficial for teams working on varied projects, allowing them to maintain independent environments while still leveraging shared Outposts resources.
To get started with resource sharing, the first step is to establish an AWS Organization if it is not already in place. Outposts resources can exclusively be shared among accounts within the same organization. For optimal Outpost management, it’s advisable to create a dedicated account or set of accounts for hosting Outposts.
Once the organization is set up with member accounts, resource shares can be created. A single resource share can include multiple resources such as Outposts, LGWs, and customer-owned IP (CoIP). Principals, including organizational units (OUs) and individual AWS account IDs, can be added to this share. For instance, I’ve shared these resources with a specific consumer account ID.
After provisioning an Outpost, its logical ID can be shared with any account within the AWS Organization. The consumer account gains the ability to provision resources on the Outpost, including Amazon Elastic Block Store (EBS) volumes and launching instances. When accessing the AWS Management Console, the consumer account can view the shared Outpost ID, its Availability Zone, and the owner account ID.
Consumer accounts can also create their own Outposts subnets within their VPCs, and LGW sharing enables them to establish routes to the on-premises network. This seamless connection is crucial for effective operations. If you’re interested in the dynamics of workplace interactions, consider checking out this blog post about gatekeepers at work.
It’s important to note that LGW and Outposts sharing are designed for use within an AWS Organization and are not meant for multi-tenancy outside of it. Additionally, any resources created in a consumer account remain invisible to the owner account of the Outpost. For enhanced visibility and management, organizations can utilize the default OrganizationAccountAccessRole that AWS Organizations creates.
While capacity information is not directly shared with consumer accounts, cross-account CloudWatch metric sharing allows for visibility into Outposts utilization metrics, helping consumer accounts gauge available capacity. For example, I’ve successfully set up metric sharing and verified sufficient capacity on the shared Outposts.
If a principal no longer requires access to the Outpost’s capacity, the resource share can be deleted through RAM in the primary Outposts account. However, it’s crucial to remember that this action does not remove resources such as subnets or instances running on the shared Outpost. Therefore, proper management and cleanup of resources in the consumer account should be planned.
In conclusion, this article highlights the newly available capabilities for Outposts and LGW sharing, emphasizing their role in facilitating multi-account resource sharing within an AWS Organization. As organizations continue to expand and evolve, these functionalities will play a significant role in enhancing operational efficiency and resource management. It’s exciting to see how these developments will contribute to improved user experiences. You can start utilizing LGW and Outposts sharing today, as there is no need for any upgrades or modifications to your existing Outposts infrastructure. For those wanting to dive deeper into the onboarding process, this resource on Amazon’s employee onboarding is an excellent guide. For more insights on organizational dynamics, refer to Michelle Marrow’s profile, who is an authority on this topic.
Leave a Reply