Amazon Web Services - FAQs

Introduction

These FAQs provide an overview of the Âé¶¹AV AWS Cloud Platform (Âé¶¹AV AWS).

Âé¶¹AV Information Technology has embarked on a hybrid cloud strategy that enables Âé¶¹AV to transition to the cloud. The Âé¶¹AV AWS Cloud Platform provides the necessary baseline infrastructure for utilizing AWS cloud services while securely integrating with Âé¶¹AV’s on-premise data centers.

Âé¶¹AV AWS is an extension of Âé¶¹AV’s on-premise network and datacenter. Users have the ability to seamlessly integrate and access resources between the on-premise and Âé¶¹AV AWS environments. Users already familiar with AWS will not notice a difference after logging in to their Âé¶¹AV AWS account. Lastly, users will not have to agree to AWS Terms and Conditions when the account is created.

Requesting a Âé¶¹AV AWS account is easy! Âé¶¹AV AWS is integrated with Âé¶¹AV's standard procurement process using purchasing orders (POs). Users need to have an approved PO from their respective department/college before a new Âé¶¹AV AWS account can be requested. Âé¶¹AV IT will work with the user to estimate cost and provide a quote that will be used to issue a PO. Once the PO is approved, navigate to the accountÌý.

Âé¶¹AV AWS is integrated with Âé¶¹AV's single sign-on (SSO) process. Users can log in to their Âé¶¹AV AWS account by going to accountÌýÌýpage. Users are requested to enter their Âé¶¹AV issued user ID and password to log in.

Users can navigate to theÌýguest access pageÌýand select ‘Guest Access’ to grant others access to their Âé¶¹AV AWS account. Access can only be granted to valid Âé¶¹AV accounts.

The user who requested the account (account owner) has access to the account. Additionally, anyone the account owner shares access with will gain access to the account. Âé¶¹AV IT does not have access to your AWS account unless explicit permission is granted.

Âé¶¹AV AWS is integrated with Âé¶¹AV’s single sign-on platform (SSO) for authentication. Users are not allowed to create or log in through local user account created within Âé¶¹AV AWS account. Âé¶¹AV AWS security audit logs (CloudTrails logs) are sent to central security account for auditing purposes if/when required.

Each Âé¶¹AV AWS Account comes pre-configured with four subnets. These subnets are split across two availability zones (AZ, refers to AWS datacenter). Two subnets are labeled ‘public’ – meaning these subnets have access to the internet (outbound), while two subnets are labeled ‘private’ – meaning these subnets have access to campus datacenter network, but not internet access.

From an end user console experience, Âé¶¹AV AWS is identical to an AWS account. However, several key differences are listed below:

  • By default, users can use services under the Oregon region. If other regions are required, please contact theÌýIT Help Center.
  • Users are not allowed to create local users (IAM user) or to create custom roles or policies. If the default access does not meet the needs, please contact theÌýIT Help Center.
  • Users have limited access to network services under AWS. For example, users are not allowed to modify/delete/create VPCs, subnets, internet gateways (IGWs) etc. If the default network configuration does not meet your needs, please contact theÌýIT Help Center.Ìý
  • Âé¶¹AV AWS allows for ease of payment and cost tracking.
  • Tied to Âé¶¹AV's purchasing department using POs. No P Card or credit card needed.Ìý
  • Âé¶¹AV AWS has pre-established security and technical configurations consistent with CSU guidelines.
  • Âé¶¹AV AWS users can contact Âé¶¹AV IT to estimate costs or help architect the environment.Ìý
  • Connected to Âé¶¹AV's in-campus network.Ìý
  • No need to agree to AWS Terms and Conditions.Ìý

Yes! The account can be used as soon as the Âé¶¹AV AWS account is created. Users receive a notification email with their account details. At that point, The Âé¶¹AV AWS account is ready for use. If there are any questions or issues, please contact theÌýIT Help Center.Ìý

.Ìý

Ìý

Âé¶¹AV AWS is integrated with Âé¶¹AV's standard procurement process using purchasing orders (POs). During the account creation process, the Âé¶¹AV AWS account is linked to a Âé¶¹AV issued PO. Every month, the respective Âé¶¹AV Accounts Payable department will receive a bill. The respective accounts payable team will charge the PO tied to a particular Âé¶¹AV AWS account.

Yes. Users can view and track their Âé¶¹AV AWS charges directly under their Âé¶¹AV account by going to the ‘Billing’ service. Users are able to create budgets, set-up notifications and run reports.

Ìý

Purchase Order questions should be directed to your department or Contact Purchasing & Contracts Administration at (818) 677-2301 or via email atÌýpurch@csun.eduÌýfor assistance with Purchase Order (PO) creation and processing.

Ìý

Ìý